Best up-to-date docs for coding MCP server for Cursor, tested

Dated results

• Context7 passed in Cursor on 2026-10-20 (Cursor CLI 2026.10.19-6bbf2c4, @upstash/context7-mcp 4.4.4, connected in 1.6s). Full result
• Microsoft Learn MCP passed in Cursor on 2026-10-22 (Cursor CLI 2026.10.22-27dcf5f, mcp-remote 0.15.2, connected in 2.9s). Full result
• Svelte MCP passed in Cursor on 2026-10-23 (Cursor CLI 2026.10.22-27dcf5f, @sveltejs/mcp 0.1.27, connected in 2.2s). Full result
• MDN MCP (experimental) passed in Cursor on 2026-10-23 (Cursor CLI 2026.10.22-27dcf5f, mcp-remote 0.15.2, connected in 2.5s). Full result
• mcpdoc (LangChain) failed in Cursor on 2026-10-15 (Cursor CLI 2026.10.14-941492e, package version not recorded, connect time not recorded). Full result
• Docfork failed in Cursor on 2026-10-15 (Cursor CLI 2026.10.14-941492e, server reported v2.2.5, connect time not recorded). Full result

Why Context7 is the candidate

Context7 passed every step in Cursor. It is the group’s site-wide candidate (judged 2026-10-20): Found React's library ID and looked up Vite's default dev-server port (5173) in its docs, in both Claude Code and Cursor (6 calls in total), and it passed its library-ID task in ChatGPT (Codex) on Oct 15 (the Vite task hasn't run there yet). No runner-up: Docfork's search failed on every call ('fetch failed': its docs API didn't respond on Oct 15; the repo is archived), and mcpdoc failed to start in both clients. Confirmed Oct 20, 2026: a second run in Claude Code and Cursor passed both tasks again (Context7 4.4.4).

Provisional: based on one dated run per app (no repeat runs yet), so treat it as a candidate, not a final pick. How we test.

What failed or is partial in Cursor

• mcpdoc (LangChain): failed on 2026-10-15. Recorded reason: no successful call to this server's tools; answer missing ['5173']; no tool result containing ['5173']
• Docfork: failed on 2026-10-15. Recorded reason: no successful call to this server's tools; no tool result containing ['5173']

Install in Cursor

The exact snippet we tested is on the Context7 page (pick the Cursor tab). Not connecting? Cursor MCP troubleshooting.

Not tested in Cursor yet

Ref (docs search MCP), Laravel Boost, pg-aiguide (Timescale), Next.js DevTools MCP, 21st.dev Magic MCP, Grounded Docs MCP Server, xmcp. Listed from their source; no result in Cursor yet.

Questions

What is the best up-to-date docs for coding MCP server for Cursor?

In ToolPassed's hands-on tests in Cursor, Context7 is our provisional candidate for up-to-date docs for coding: it passed install, connect, tools and an agent task on 2026-10-20. We ran 6 up-to-date docs for coding MCP servers in Cursor; 4 passed every step; not a pass: mcpdoc (LangChain) (failed), Docfork (failed).

Does Context7 work with Cursor?

Context7 passed in Cursor on 2026-10-20 (Cursor CLI 2026.10.19-6bbf2c4, @upstash/context7-mcp 4.4.4, connected in 1.6s).

Does mcpdoc (LangChain) work with Cursor?

No, not in our test: mcpdoc (LangChain) failed in Cursor on 2026-10-15 (Cursor CLI 2026.10.14-941492e, package version not recorded, connect time not recorded). Recorded reason: no successful call to this server's tools; answer missing ['5173']; no tool result containing ['5173']

Does Docfork work with Cursor?

No, not in our test: Docfork failed in Cursor on 2026-10-15 (Cursor CLI 2026.10.14-941492e, server reported v2.2.5, connect time not recorded). Recorded reason: no successful call to this server's tools; no tool result containing ['5173']