MCP Gateway · Claude Code
Connect Context7 to Claude Code
A model's knowledge of a library lags behind its releases. With Context7 behind the Speakeasy MCP Gateway, Claude Code can look up current documentation and code examples for the libraries in your project before it writes code against them. Each prompt and tool call goes to Speakeasy first, and the OpenTelemetry exporter ties sessions to named people.
- Category
- Developer tools
- Tools
- 2
- Authentication
- None
- Claude Code
- CLI
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 Code 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 Code
Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.
Run the command below with your organization gateway URL.
Open
/mcpin Claude Code and choose Authenticate to sign in.claude mcp add --transport http --scope user \ 'speakeasy' \ 'https://<organization host>/mcp/gateway/<organization slug>' - 04
Sign in and use Context7 from Claude Code
The first time Claude Code 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 Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.
To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.
Use cases
What Claude Code users do with Context7
Upgrade a dependency with current docs
Before bumping a major version, Claude Code resolves the library and queries its current documentation for migration steps, instead of relying on what the model remembers.
Edit a config file correctly
When a tool's config format changes between releases, Claude Code looks up the current options and examples before it touches the file.
Pick the right package name
Ask Claude Code which libraries match a name. It returns the matching entries, so you choose the right package before installing anything.
Tools
2 tools
Each Context7 tool can be allowed or denied per team and role at the MCP Gateway before Claude Code 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 Code
The gateway covers every client the same way. The rest depends on what Claude Code 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 Code. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Claude Code
Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.
User attribution
Claude Code
Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.
Budgets
Claude Code
Spend limits can block Claude Code traffic once a budget is reached.
Device agent and MDM
Claude Code
The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.
Anthropic inference hooks
Claude Code
On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).
- Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
- Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.
Questions
Frequently asked questions
Do developers store a Context7 credential in Claude Code?
Can documentation lookups be limited to some teams?
How do Claude Code users get Context7?
Are Context7 calls from Claude Code logged?
Connect more