MCP Gateway · Claude
Connect Context7 to Claude
Not everyone who needs accurate library documentation writes code all day. Support engineers, technical writers and reviewers can ask Claude about a programming library and get answers from Context7's current documentation. Context7 connects as a custom connector through the Speakeasy MCP Gateway, and on Claude Enterprise each prompt can be checked before inference (beta).
- Category
- Developer tools
- Tools
- 2
- Authentication
- None
- Claude
- Web, desktop and mobile
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.
Set up
Add Context7 to Claude in 4 steps
- 01
Add Context7 from the catalog
An admin finds Context7 in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Context7
Give teams the
mcp:connectscope on the Context7 server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Context7 to their gateway on the next call, and removing it takes it away. - 03
Connect Claude
Add the gateway URL as a custom connector, then connect it from Customize > Connectors.
On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.
Each person opens Customize > Connectors and clicks Connect to sign in.
On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.
- 04
Sign in and use Context7 from Claude
The first time Claude connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
From then on, Context7's tools appear in Claude, limited to what the person's access allows, and every call lands in the gateway's tool logs.
No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.
Use cases
What Claude users do with Context7
Answer a customer's integration question
Support and solutions staff can ask Claude how a common library handles a task, and reply to the customer with an answer drawn from current documentation.
Understand a library before approving it
Reviewers can ask Claude what a library a team wants to adopt is for and how it's used, based on its documentation rather than a sales page.
Check code samples in a tutorial
Technical writers and developer advocates can draft a tutorial with Claude and compare each code sample against the library's current examples.
Tools
2 tools
Each Context7 tool can be allowed or denied per team and role at the MCP Gateway before Claude sees it.
resolve-library-id
Resolves a package/product name to a Context7-compatible library ID and returns matching libraries.
query-docs
Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework.
Control
What Speakeasy can see and stop in Claude
The gateway covers every client the same way. The rest depends on what Claude exposes to Speakeasy.
Tool logs
Gateway
Every Context7 call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Context7 tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Context7 can reject a tool request before it reaches the server, or withhold a result from Claude. MCP-scoped policies are enabled per organization.
Anthropic inference hooks
Claude
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Conversation import
Claude
Claude conversations can be imported through Anthropic's Compliance API for review after the fact.
- Custom connectors need a Claude plan that supports them.
- Budgets don't cover Claude web and desktop usage.
Questions
Frequently asked questions
Does Context7 in Claude need its own client ID?
Can I give Context7 only to technical teams?
How do Claude users get Context7?
Are Context7 calls from Claude logged?
Connect more