Back to the MCP Gateway catalog

MCP Gateway · Catalog

Context7 icon

Context7 MCP server

Official

Context7 MCP is the official Model Context Protocol server for Context7, with tools that let agents look up a library and query up-to-date documentation for it. Connect it through the Speakeasy MCP Gateway and agents such as Claude, Cursor, and ChatGPT get one governed URL for it, with SSO, RBAC, and a full audit trail.

Developer tools2 toolsAuth: open

Behind the MCP Gateway

Run Context7 MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Context7 call inspected and logged.

Deploy on MCP Gateway

Tools · 2

Each tool below can be allowed or denied per team and role at the MCP Gateway, and every call is inspected and logged.

resolve-library-id

Resolves a package/product name to a Context7-compatible library ID and returns matching libraries. You MUST call this function before 'Query Documentation' tool to obtain a valid Context7-compatible library ID UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. Each result includes: - Library ID: Context7-compatible identifier (format: /org/project) - Name: Library or package name - Description: Short summary - Code Snippets: Number of available code examples - Source Reputation: Authority indicator (High, Medium, Low, or Unknown) - Benchmark Score: Quality indicator (100 is the highest score) - Versions: List of versions if available. Use one of those versions if the user provides a version in their query. The format of the version is /org/project/version. For best results, select libraries based on name match, source reputation, snippet coverage, benchmark score, and relevance to your use case. Selection Process: 1. Analyze the query to understand what library/package the user is looking for 2. Return the most relevant match based on: - Name similarity to the query (exact matches prioritized) - Description relevance to the query's intent - Documentation coverage (prioritize libraries with higher Code Snippet counts) - Source reputation (consider libraries with High or Medium reputation more authoritative) - Benchmark Score: Quality indicator (100 is the highest score) Response Format: - Return the selected library ID in a clearly marked section - Provide a brief explanation for why this library was chosen - If multiple good matches exist, acknowledge this but proceed with the most relevant one - If no good matches exist, clearly state this and suggest query refinements For ambiguous queries, request clarification before proceeding with a best-guess match. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best result you have.

query-docs

Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. You must call 'Resolve Context7 Library ID' tool first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best information you have.

Questions

What is a Context7 MCP server?
A Context7 MCP server exposes Context7 to AI agents as Model Context Protocol tools. Instead of a custom integration per agent, any MCP client can connect to the server and call tools such as resolve-library-id or query-docs to work with Context7. The server in this catalog is the official Context7 MCP server.
What can you do with Context7 MCP?
Agents can look up a library and query up-to-date documentation for it. The catalog lists 2 tools for this server, including resolve-library-id and query-docs. The full list with descriptions is on this page.
Why put Context7 MCP behind an MCP gateway?
Connecting the Context7 MCP server directly to each client means a separate credential per developer, no inventory of who can reach Context7 through an agent, and no record of what agents did with it. An MCP gateway sits between every agent and the Context7 server, so sign-in runs through your identity provider, role-based access decides which teams can call which Context7 tools, and every call is inspected and logged in one place. The Speakeasy MCP Gateway applies those controls to Context7 and to every other server in your catalog.
How do you connect Context7 MCP through a gateway?
Add the Context7 server from the Speakeasy MCP catalog and every agent reaches it through one gateway URL, next to the rest of your approved servers. Authentication uses OAuth 2.1 with PKCE and dynamic client registration, sign-in runs through your identity provider, and role-based access controls decide which teams can use which Context7 tools. Every prompt, response, and tool call is inspected and logged at the gateway.
How is this different from an unofficial Context7 MCP?
Community-built Context7 MCP servers wrap the same Context7 surface but are not vendor-maintained. This catalog lists the official Context7 MCP server. Running it behind the Speakeasy MCP Gateway adds SSO, role-based access controls, and an audit trail of every call, whichever credential the server itself uses.

AI everywhere.

Control here.

Talk to usLearn more