Skip to main content
Back to the DeepWiki MCP server

MCP Gateway · Claude

DeepWiki icon

Connect DeepWiki to Claude

Product, partnership and procurement staff sometimes need to understand an open source project without reading its code. DeepWiki provides AI-generated wiki docs for public GitHub repositories, and Claude can read them or ask DeepWiki questions on someone's behalf. It's added as a custom connector pointing at the Speakeasy MCP Gateway, and no client ID or secret is needed.

Category
Developer tools
Tools
3
Authentication
None
Claude
Web, desktop and mobile

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

    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.

  4. 04

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

Understand a project a vendor builds on

Ask Claude for an overview of an open source project behind a product you're evaluating, drawn from the repository's DeepWiki topics and pages.

read_wiki_structureread_wiki_contents

Draft a security questionnaire answer

When a questionnaire asks how an open source component handles data, Claude asks DeepWiki about its public repository and drafts an answer for an engineer to confirm.

ask_question

Brief yourself before a partner call

Ahead of a call with an open source maintainer or partner, ask Claude to read the project's architecture pages and summarize them in a few paragraphs.

read_wiki_contents

Tools

3 tools

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

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

Which Claude plans can use DeepWiki through Speakeasy?
Custom connectors need a Claude plan that supports them. The gateway's sign-in handles client registration.
Can Claude prompts that mention a repository be blocked?
On Claude Enterprise, each prompt goes to Speakeasy before inference, and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
How do Claude users get DeepWiki?
An admin adds DeepWiki from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway URL as a custom connector, then connect it from Customize > Connectors. Each person then sees only the DeepWiki tools their access allows.
Are DeepWiki calls from Claude 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.