Context7 MCP server for Claude, Codex and Cursor

What your AI apps can do with Context7

• Resolve libraries
• Query up-to-date documentation

Context7 MCP tools

2 tools, listed by Toolstile from the server itself on 29 October 2026. The server decides what it offers and can add or rename tools at any time; after you connect, Toolstile shows the current list.

Suggested starting access

Toolstile read each Context7 tool's description and wrote these starting selections by hand. They are a suggestion reviewed by Toolstile, not a guarantee: Upstash decides what each tool does and can change it, so check that a selection fits each app before you save it.

Look up library documentation

Find a library and read its current documentation and code examples.

• Allow: resolve-library-id, query-docs

In the access editor, choosing a suggestion adds the listed tools this server offers to your draft. Existing access stays as it is, blocks and approval requirements stay in force, and the suggestion doesn't grant tool names the server adds later. Nothing is saved until you choose Save changes.

Suggested access for each AI app

• 2 tools marked read-only (resolve-library-id, query-docs). These are usually safe to allow.

These are hints the server reports about its own tools, not guarantees.

Coding agent in Claude Code or Cursor. Allow the read tools so the agent can look things up without stopping, and require approval for tools that change shared data.

Chat or research app in Claude Desktop. Allow reading and searching. Allow writes only where you want the app to act for you.

Unattended agent, such as a scheduled Codex job. No one is watching the session, so keep it narrow: allow what the job needs, require approval for changes and block the rest.

Blocked tools are removed from the tool list an app sees, so it won't try them. Because rules apply per app, the same Context7 connection can be broad in one app and read-only in another, and the credential stays in Toolstile instead of each app's config file.

How it works with Toolstile

1. Connect once. Add Context7 to a workspace (no sign-in). Toolstile keeps the credential, so no agent config holds it.
2. Choose access per app. Give Claude Code every Context7 tool, give Cursor only the read tools, or keep Context7 away from an app entirely.
3. Share approved accounts. Teammates use the connection without copying tokens, and you can remove access in one place.
4. Review activity. See which app called which tool and when, so you can tighten access with evidence.

Add the Context7 MCP server to an AI app

Through Toolstile, every AI app uses one gateway entry, whichever servers you connect. In Claude Code:

claude mcp add --transport http toolstile 'https://mcp.toolstile.com/mcp'

Then connect Context7 in your workspace and choose which of its tools that app may use. Client setup covers Codex, Cursor and Claude Desktop.

To connect directly instead, add the Upstash endpoint to each app separately. In Claude Code:

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

In Cursor's mcp.json:

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

Some servers accept only clients they have approved, or need a token header. Check the Upstash MCP documentation for what your client needs.

Before you connect

No account needed. Anonymous use is rate limited by Context7.

Server details

Upstash MCP documentation