Context7 MCP — Remote MCP Server

Context7's trick is fetching the documentation for the exact version of a library you are using — 'use context7' in a prompt is now a common incantation in Cursor and Claude Code workflows. The hosted endpoint at mcp.context7.com is free and unauthenticated, with a two-step flow: resolve the library id, then pull the docs.

Endpoint & Transport

• Endpoint URL: https://mcp.context7.com/mcp
• Transport: Streamable HTTP

Authentication

Context7 MCP is public and unauthenticated — no OAuth, no API key, no headers. Any MCP client can connect and call its tools directly, which also makes it a great endpoint for smoke-testing your own MCP client or proxy.

Available Tools (2)

Connect in 30 Seconds

Claude Code — one command:

claude mcp add --transport http context7 https://mcp.context7.com/mcp

Cursor — add to ~/.cursor/mcp.json:

{ "mcpServers": { "context7": { "url": "https://mcp.context7.com/mcp" } } }

VS Code — add to .vscode/mcp.json:

{ "servers": { "context7": { "type": "http", "url": "https://mcp.context7.com/mcp" } } }

Claude Desktop & stdio clients — bridge with mcp-remote:

{ "mcpServers": { "context7": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.context7.com/mcp"] } } }

Troubleshooting

• "Session expired" / stale Mcp-Session-Id — just re-send initialize; stateless clients can ignore session headers entirely.
• No authentication — rate limits apply per IP.
• Two-tool flow: call resolve-library-id first, then get-library-docs with the returned id.