MCP Gateway · Claude Cowork
Connect Context7 to Claude Cowork
Cowork is useful for documentation jobs that take many lookups, such as checking every code sample in a guide or preparing a training module. Context7 supplies current library documentation for each step. Plugins reach Cowork from the organization's synced marketplace, and agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
- Category
- Developer tools
- Tools
- 2
- Authentication
- None
- Claude Cowork
- Cowork tab in Claude Desktop
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 Cowork 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. Claude Cowork connects to the Context7 server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect Claude Cowork
Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.
New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.
Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.
In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.
Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.
In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.
- 04
Sign in and use Context7 from Claude Cowork
The first time Claude Cowork 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 Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Use cases
What Claude Cowork users do with Context7
Audit the code samples in your docs
Cowork goes through each code sample in your product docs, looks up the libraries they use, and lists the samples that no longer match current documentation.
Assemble a training module
Give Cowork a topic, such as data fetching in a web framework, and it builds a multi-section training outline with examples taken from current docs.
Write a library decision memo
Cowork looks up several candidate libraries, reads how each handles the feature you need, and writes a memo setting out the options for the team.
Tools
2 tools
Each Context7 tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork 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 Cowork
The gateway covers every client the same way. The rest depends on what Claude Cowork 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 Cowork. MCP-scoped policies are enabled per organization.
Prompt blocking
Claude Cowork
Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
Session telemetry
Claude Cowork
Cowork's OTLP export ties sessions to people and feeds observability.
Anthropic inference hooks
Claude Cowork
On Claude Enterprise, prompts can be checked before inference (beta).
- Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
- Personal Claude accounts can't be governed in Cowork.
Questions
Frequently asked questions
Can personal Claude accounts use governed Context7 in Cowork?
How does Cowork pick up an updated Context7 plugin?
How do Claude Cowork users get Context7?
Are Context7 calls from Claude Cowork logged?
Connect more