MarkItDown MCP (Microsoft) not working in Cursor? Fixes
Failed It failed in our test on Oct 21, 2026. Below is the exact setup we used in Cursor (2026.10.19-6bbf2c4), 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": {
"markitdown": {
"command": "uvx",
"args": [
"markitdown-mcp"
]
}
}
}Replace any <YOUR_…> placeholder and local test paths with your own. Every client’s tested snippet is on the MarkItDown MCP (Microsoft) page.
2. Check that Cursor connects to it
In our run the connect check was OK (connected in 2.0s). Our check output:
markitdown: ready3. Confirm the tools are visible
Cursor listed 1 tools from this server in our run (the protocol check found 1). Fewer or none usually means the server did not start; check the config above.
Errors we observed
- agent task: page read: no tool result containing ['Example Domain']
- agent task: page read (tool error during the run):
no tool result containing ['Example Domain']
Quoted from our run log. Secrets redacted. We list only what we saw.
More help
MarkItDown MCP (Microsoft): all results and setup · Full Cursor run · General Cursor MCP troubleshooting
