Docfork MCP not working in Cursor? Fixes
Failed It failed in our test on Oct 15, 2026. Below is the exact setup we used in Cursor (2026.10.14-941492e), every error we saw, and what to check, all from our own run log.
Date tested: · From our harness, not the maker’s claims · How we test
1. Use the install config we tested in Cursor
{
"mcpServers": {
"docfork": {
"command": "npx",
"args": [
"-y",
"docfork"
]
}
}
}Replace any <YOUR_…> placeholder and local test paths with your own. Every client’s tested snippet is on the Docfork page.
2. Check that Cursor connects to it
In our run the connect check was OK (connect time not recorded). Our check output:
docfork: ready3. Confirm the tools are visible
Cursor listed 2 tools from this server in our run (the protocol check found 2). Fewer or none usually means the server did not start; check the config above.
Errors we observed
- agent task: docs fact: no successful call to this server's tools; no tool result containing ['5173']
Quoted from our run log. Secrets redacted. We list only what we saw.
More help
Docfork: all results and setup · Full Cursor run · General Cursor MCP troubleshooting
