Skip to main content
Back to the DeepWiki MCP server

MCP Gateway · Claude Code

DeepWiki icon

Connect DeepWiki to Claude Code

Most projects depend on open source code that nobody on the team wrote. DeepWiki offers AI-generated wiki docs for public GitHub repositories and answers questions about them, and through the Speakeasy MCP Gateway Claude Code can read those docs in the middle of a task. Speakeasy checks every prompt and DeepWiki call before it runs and ties each session to a named person.

Category
Developer tools
Tools
3
Authentication
None
Claude Code
CLI

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.

Deploy on MCP Gateway

Set up

Add DeepWiki to Claude Code in 4 steps

  1. 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.

  2. 02

    Choose who can use DeepWiki

    Give teams the mcp:connect scope on the DeepWiki server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds DeepWiki to their gateway on the next call, and removing it takes it away.

  3. 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 /mcp in Claude Code and choose Authenticate to sign in.

    claude mcp add --transport http --scope user \
      'speakeasy' \
      'https://<organization host>/mcp/gateway/<organization slug>'
  4. 04

    Sign in and use DeepWiki 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, DeepWiki'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 DeepWiki

Learn an open source dependency

Before patching around a bug in a dependency, Claude Code reads DeepWiki's topic list for its public repository and the pages that cover the module involved.

read_wiki_structureread_wiki_contents

Ask how a project solves a problem

Ask how a public repository handles retries or plugin loading, and Claude Code gets a context-grounded answer to draw on while writing your own version.

ask_question

Plan an upstream contribution

When you plan a pull request to an open source project, Claude Code reads its architecture pages and asks where the change belongs.

read_wiki_contentsask_question

Tools

3 tools

Each DeepWiki tool can be allowed or denied per team and role at the MCP Gateway before Claude Code 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 Code

The gateway covers every client the same way. The rest depends on what Claude Code 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 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

Does DeepWiki work with our private repositories?
DeepWiki's tools cover public GitHub repositories. Its wiki docs and answers are about those repositories.
Can I limit which teams use DeepWiki in Claude Code?
Yes. Each of the 3 DeepWiki tools can be allowed or denied per team and role at the MCP Gateway.
How do Claude Code users get DeepWiki?
An admin adds DeepWiki from the Speakeasy MCP Catalog and grants access by team or role. Add the organization gateway as an HTTP MCP server, then authenticate from /mcp. Each person then sees only the DeepWiki tools their access allows.
Are DeepWiki calls from Claude Code logged?
Yes. DeepWiki calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

DeepWiki in other clients

AI everywhere.

Control here.