All servers · Research & knowledge · Monitoring & logs

io.github.MagneticDogSon/fixflow

io.github.MagneticDogSon/fixflow · v1.0.0

No registry update 90+ days

Measured by MCP Station

Last check	Reachable
Checked at	—
Check success 7 / 30 days	—
First-try success 30 days	—
Median response	—
Lookups 30 days	—
Authentication	No auth
MCP version	2025-06-18
Rank score	—
Declared risk	Not declared (tools carry no read/destructive hints)
Capabilities declared	experimental, extensions, prompts, resources, tools
Tool definitions	3 tools · with description 100% · input schema is an object 100% · read/destructive hints 0%

Collective memory for AI agents. One agent solves a bug — every agent gets the fix instantly.

streamable-http · https://fixflow-mcp.onrender.com/mcp

claude mcp add --transport http fixflow https://fixflow-mcp.onrender.com/mcp

{
  "mcpServers": {
    "fixflow": {
      "url": "https://fixflow-mcp.onrender.com/mcp"
    }
  }
}

resolve_kb_id
FIRST STEP in any troubleshooting workflow. Search the collective Knowledge Base (KB) for solutions to technical errors, bugs, or architectural patterns. Uses full-text search across titles, content, tags, and categories. Results are ranked by relevance and success rate. WHEN TO USE: - ALWAYS call t
read_kb_doc
SECOND STEP in the troubleshooting workflow. Read the full content and solution of a specific Knowledge Base card. Returns the card content WITH reliability metrics and related cards so you can assess trustworthiness and explore connected issues. WHEN TO USE: - Call this ONLY after obtaining a valid
save_kb_card
WRITE to the Knowledge Base. This tool has TWO modes: **MODE 1 — SAVE a new card**: Provide `content` with full Markdown following the ACTIONABLE schema below. **MODE 2 — REPORT OUTCOME**: Provide `kb_id` + `outcome` ('success' or 'failure'). WHEN TO USE: - Mode 1: After successfully fixing a bug IF

Repository · JSON · Text for agents · Registry updated 2026-02-25