MCP Gateway · Claude Cowork
Connect DeepWiki to Claude Cowork
Researching several open source projects means reading many repositories and asking each one the same questions. Cowork can carry out that research as one long task, with DeepWiki supplying wiki docs and answers for public GitHub repositories. Cowork picks up the DeepWiki plugin from the organization's synced marketplace, and Speakeasy reviews each prompt before its step proceeds.
- Category
- Developer tools
- Tools
- 3
- Authentication
- None
- Claude Cowork
- Cowork tab in Claude Desktop
Behind the MCP Gateway
Run DeepWiki MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every DeepWiki call inspected and logged.
Set up
Add DeepWiki to Claude Cowork in 4 steps
- 01
Add DeepWiki from the catalog
An admin finds DeepWiki 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 DeepWiki
Give teams the
mcp:connectscope on the DeepWiki server through team access or a role. Claude Cowork connects to the DeepWiki 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 DeepWiki 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, DeepWiki'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 DeepWiki
Research a shortlist of projects
Cowork works through a list of public repositories, reads each wiki, asks every project the same questions, and writes a report on what it found.
Build an onboarding reading pack
Cowork collects the DeepWiki pages for the open source projects your team depends on and assembles them into an onboarding guide for new hires.
Answer a due diligence checklist
For a technical due diligence task, Cowork asks a set of questions about a public repository and records each answer in a document for review.
Tools
3 tools
Each DeepWiki tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork sees it.
read_wiki_structure
Get a list of documentation topics for a GitHub repository.
read_wiki_contents
View documentation about a GitHub repository.
ask_question
Ask any question about a GitHub repository and get an AI-powered, context-grounded response.
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 DeepWiki call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the DeepWiki tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to DeepWiki 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
Is Cowork research with DeepWiki attributed to a person?
Do personal Claude accounts get the same DeepWiki controls in Cowork?
How do Claude Cowork users get DeepWiki?
Are DeepWiki calls from Claude Cowork logged?
Connect more