fixgraph_get_fixes
Get all verified fixes for a specific FixGraph issue by its ID or slug.
LABSCO SUMMARY
The submit tool asks for root cause and validation, not just steps — which is what separates a fix record from a forum answer.
root_cause, steps, validation and risk_level are all fields on fixgraph_submit_fix, so what goes in is a structured account rather than a paste. The read side matches: search results carry a trust score alongside a fix count, so an issue with many fixes and a low score reads very differently from one with a single verified fix. Writing is the only thing gated — the API key is needed on submit, and neither search nor read requires one.
What it is
A FixGraph client with three tools — search issues with their trust scores and fix counts, read the verified fixes for one issue, and submit a new fix.
What you get
- fixgraph_search returns matching issues with trust scores and fix counts, filterable by category with a limit.
- fixgraph_get_fixes returns all verified fixes for an issue by its id or slug.
- fixgraph_submit_fix submits a fix with a title, root_cause, steps, validation and a risk_level.
Requirements
Nothing for fixgraph_search or fixgraph_get_fixes. fixgraph_submit_fix requires a FIXGRAPH_API_KEY environment variable.
Setup effort
One command — npx -y fixgraph-mcp
USE CASES
01
Finding out whether the error you are hitting is a known one
The trust score and the fix count together say how settled an issue is, which is more useful than a match on its own.
02
Reading how other people actually fixed it
The verified fixes come with their steps and validation, which is the difference between a suggestion and something that has been checked.
03
Writing up a fix so the next person finds it
Root cause, steps, validation and risk level are all required, which forces the write-up to be usable rather than approximate.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
fixgraph_search
Search FixGraph for engineering fixes. Returns matching issues with trust scores and fix counts.
fixgraph_submit_fix
Submit a new fix to FixGraph. Requires FIXGRAPH_API_KEY env var.
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected; the project documents 5. The two missing, fixgraph_submit_issue and fixgraph_verify_fix, are write tools; the submit tools require an API key (FIXGRAPH_API_KEY).
Requires
npx on PATH
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y fixgraph-mcpMCP Clients
Claude Desktop, Cursor, Windsurf
JSON
{
"mcpServers": {
"fixgraph": {
"command": "npx",
"args": [
"-y",
"fixgraph-mcp"
]
}
}
}
