Back to the MCP Gateway catalog

MCP Gateway · Catalog

DeepWiki icon

DeepWiki MCP server

Official

DeepWiki MCP is the official Model Context Protocol server for DeepWiki, with tools that let agents read AI-generated wiki docs for public GitHub repositories and ask questions about them. Connect it through the Speakeasy MCP Gateway and agents such as Claude, Cursor, and ChatGPT get one governed URL for it, with SSO, RBAC, and a full audit trail.

Developer tools3 toolsAuth: open

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

Tools · 3

Each tool below can be allowed or denied per team and role at the MCP Gateway, and every call is inspected and logged.

read_wiki_structure

Get a list of documentation topics for a GitHub repository. Args: repoName: GitHub repository in owner/repo format (e.g. "facebook/react")

read_wiki_contents

View documentation about a GitHub repository. Args: repoName: GitHub repository in owner/repo format (e.g. "facebook/react")

ask_question

Ask any question about a GitHub repository and get an AI-powered, context-grounded response. Args: repoName: GitHub repository or list of repositories (max 10) in owner/repo format question: The question to ask about the repository

Questions

What is a DeepWiki MCP server?
A DeepWiki MCP server exposes DeepWiki to AI agents as Model Context Protocol tools. Instead of a custom integration per agent, any MCP client can connect to the server and call tools such as read_wiki_structure or read_wiki_contents to work with DeepWiki. The server in this catalog is the official DeepWiki MCP server.
What can you do with DeepWiki MCP?
Agents can read AI-generated wiki docs for public GitHub repositories and ask questions about them. The catalog lists 3 tools for this server, including read_wiki_structure, read_wiki_contents, and ask_question. The full list with descriptions is on this page.
Why put DeepWiki MCP behind an MCP gateway?
Connecting the DeepWiki MCP server directly to each client means a separate credential per developer, no inventory of who can reach DeepWiki through an agent, and no record of what agents did with it. An MCP gateway sits between every agent and the DeepWiki server, so sign-in runs through your identity provider, role-based access decides which teams can call which DeepWiki tools, and every call is inspected and logged in one place. The Speakeasy MCP Gateway applies those controls to DeepWiki and to every other server in your catalog.
How do you connect DeepWiki MCP through a gateway?
Add the DeepWiki server from the Speakeasy MCP catalog and every agent reaches it through one gateway URL, next to the rest of your approved servers. Authentication uses OAuth 2.1 with PKCE and dynamic client registration, sign-in runs through your identity provider, and role-based access controls decide which teams can use which DeepWiki tools. Every prompt, response, and tool call is inspected and logged at the gateway.
How is this different from an unofficial DeepWiki MCP?
Community-built DeepWiki MCP servers wrap the same DeepWiki surface but are not vendor-maintained. This catalog lists the official DeepWiki MCP server. Running it behind the Speakeasy MCP Gateway adds SSO, role-based access controls, and an audit trail of every call, whichever credential the server itself uses.

AI everywhere.

Control here.

Talk to usLearn more