Context7 MCP Server

Add to your client

Copy the config for your MCP client and paste it into its config file.

{
  "mcpServers": {
    "context7-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@upstash/context7-mcp"
      ],
      "env": {
        "CONTEXT7_API_KEY": "<optional-your-context7-api-key>"
      }
    }
  }
}

Before you start

• Node.js 18 or newer (for the local stdio server via npx)
• An MCP-capable client (Cursor, Claude Code, Claude Desktop, VS Code, Windsurf, OpenCode, and 30+ others)
• A free Context7 API key from https://context7.com/dashboard for higher rate limits (optional but recommended; passed via the CONTEXT7_API_KEY header or --api-key)

About Context7 MCP Server

Tools & capabilities (2)

When to use it

• Use it when your agent writes code against an outdated version of a framework and you need version-pinned docs.
• Use it when a library released breaking changes after the model's training cutoff.
• Use it when you want real, copy-pasteable code examples pulled from current docs instead of invented snippets.
• Use it when you can name the exact library/version (e.g. /vercel/next.js/v15) and want docs injected with no guesswork.
• Use it across many editors — it documents 30+ clients and a hosted remote endpoint for setups where you can't run Node locally.

Quick setup

1. 1Run `npx ctx7 setup` for guided OAuth + client wiring, or configure manually.
2. 2For local stdio: add a server running `npx -y @upstash/context7-mcp` to your client's MCP config.
3. 3For remote: point the client at `https://mcp.context7.com/mcp` and pass your key via the CONTEXT7_API_KEY header.
4. 4Optionally create a free API key at context7.com/dashboard and supply it (CONTEXT7_API_KEY env/header or --api-key) to lift rate limits.
5. 5Restart/reload the client so the resolve-library-id and docs tools register.
6. 6Ask about a specific library and confirm version-specific docs are returned.

Context7 MCP Server FAQ