Does Context7 work with Claude Desktop?
Yes. Context7 passed every step of our test in Claude Desktop on Oct 18, 2026: it installed, connected, its tools were visible, and an agent used it to finish a real task.
Result
Steps
- install OK
- connect OK
- tools visible OK
- agent task: library lookup OK
- agent task: docs fact OKfetch current library docs and answer a fact from them (any docs server, not only library-ID based ones)
Test note: server wrapped in harness/scripts/mcp_tee.py to record JSON-RPC; prompts typed via xdotool; tool Allow pop-ups approved by the operator for test servers only; model = app default
From our own harness run, not the maker’s claims. How we test.
Versions tested
Claude Desktop 2.37337.1 (Linux beta) · package version not recorded · connected in 10s · tested Oct 18, 2026
Server package and resolved dependency versions: not recorded for these runs (our harness records them from Oct 19, 2026 on).
What happened in this run
Install config we used
{
"command": "npx",
"args": [
"-y",
"@upstash/context7-mcp"
]
}Connection check
initialize seen in tee log after app restartTools check
tools/list answered (tee log)
Agent task: library lookup
- 1 calls reached the server
- Agent’s answer (excerpt):
The Context7 library ID for React is /reactjs/react.dev, which is the official react.dev documentation. Context7 also lists /react/react and /websites/react_dev…
Agent task: docs fact
- 2 calls reached the server
- Agent’s answer (excerpt):
The Vite dev server's default port is 5173. If that port is already in use, Vite automatically tries the next available one. Sources: Server Options - Vite
Raw details from our harness log for this run. Secrets redacted.
Set it up in Claude Desktop
Copy-paste config for every app is on the Context7 page. Not connecting? Claude Desktop MCP troubleshooting.
Other apps we tested it in: Claude Code (passed) · Cursor (passed) · ChatGPT (Codex) (passed).