Data as of

Context7 for Cursor: Setup & Config

Context7 retrieves current library documentation and code examples for Cursor.

Context7 Cursor configuration

  1. Choose Cursor configuration scope

    For Context7, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add Context7 to Cursor

    Use the context7-mcp entry below in mcpServers. Keep Context7's documented http connection fields and your other Cursor entries.

  3. Check Context7 in Cursor

    Context7: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

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

Context7 in Cursor: http checks

  • Enable Context7 in Cursor's MCP settings and inspect its tools. For mcp.context7.com, check reachability, transport, and credential expiry if authentication fails.
  • Context7: check http connectivity to mcp.context7.com from Cursor; a stdio command is not a replacement for this endpoint.
Catalog transports
stdio
Tools
resolve-library-id, query-docs

Context7 — details. Cursor guide

Frequently asked questions

Cursor's Context7 entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

Cursor's context7-mcp example uses http. The Context7 catalog lists stdio; these instructions follow the stored configuration instead.

Cursor connects Context7 to mcp.context7.com using url.

Context7's stored list contains 2 tools, including resolve-library-id, query-docs. Compare those names with Cursor's connected tool list; the stored list is not a live check.