DeepWiki MCP server for AI agents and assistants

Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with DeepWiki MCP or direct API to analyze public GitHub repos, summarize architecture, answer codebase questions, and inspect documentation through natural language.

DeepWiki MCP logoDeepWiki MCP
No Auth

DeepWiki MCP is a free AI-powered service for exploring public GitHub repository documentation and codebases. Use it to understand unfamiliar repos fast without setting up credentials or cloning code locally.

3 Tools

Try DeepWiki MCP now

Type what you want done — sign in and watch it run live in the Tool Router playground.

TOOL ROUTER PLAYGROUND
DeepWiki MCP
Try asking
TOOLS

Supported Tools

Every DeepWiki MCP action and event your agent gets out of the box.

Ask question

Ask any question about a GitHub repository and get an AI-powered, context-grounded response.

Read wiki contents

View documentation about a GitHub repository.

Read wiki structure

Get a list of documentation topics for a GitHub repository.

SETUP GUIDE

Connect DeepWiki MCP Tool with your Agent

1

Install Composio

typescript
npm install @composio/core ai @ai-sdk/mcp @ai-sdk/openai
Install the Composio SDK and your agent framework
2

Create a session with MCP enabled

typescript
import { Composio } from "@composio/core";

const composio = new Composio();
const { mcp } = await composio.create("your-user-id", {
  toolkits: ["deepwiki_mcp"],
  mcp: true,
});
Create a session scoped to DeepWiki MCP and read its MCP URL and headers
3

Connect your agent to the MCP server

typescript
import { createMCPClient } from "@ai-sdk/mcp";
import { openai } from "@ai-sdk/openai";
import { generateText, stepCountIs } from "ai";

const client = await createMCPClient({
  transport: { type: "http", url: mcp.url, headers: mcp.headers },
});

const { text } = await generateText({
  model: openai("gpt-5.6-sol"),
  tools: await client.tools(),
  prompt: "Summarize the architecture of the public GitHub repository vercel/next.js using DeepWiki",
  stopWhen: stepCountIs(10),
});

console.log(text);
await client.close();
Pass the session's MCP URL and headers to your agent and run a DeepWiki MCP request
SETUP GUIDE

Connect DeepWiki MCP API Tool with your Agent

1

Install Composio

typescript
npm install @composio/core @composio/openai openai
Install the Composio SDK, the OpenAI provider, and the OpenAI SDK
2

Create a Composio session

typescript
import OpenAI from "openai";
import { Composio } from "@composio/core";
import { OpenAIResponsesProvider } from "@composio/openai";

const composio = new Composio({ provider: new OpenAIResponsesProvider() });
const client = new OpenAI();

const session = await composio.create("your-user-id", { toolkits: ["deepwiki_mcp"] });
const tools = await session.tools();
Initialize Composio with the OpenAI Responses provider and create a session scoped to DeepWiki MCP
3

Run DeepWiki MCP tools with your agent

typescript
let response = await client.responses.create({
  model: "gpt-5.6-sol",
  tools,
  input: [{ role: "user", content: "Summarize the architecture of the public GitHub repository vercel/next.js using DeepWiki" }],
});

while (response.output.some((o) => o.type === "function_call")) {
  const outputs = await composio.provider.handleToolCalls(session, response.output);
  response = await client.responses.create({
    model: "gpt-5.6-sol",
    tools,
    previous_response_id: response.id,
    input: outputs,
  });
}

console.log(response.output_text);
Send a request, execute the DeepWiki MCP tool calls through the session, and print the final answer

Why Use Composio?

AI Native DeepWiki MCP Integration

  • Supports both DeepWiki MCP server and direct API based integrations
  • Structured, LLM-friendly schemas help agents ask precise questions about public GitHub repositories
  • Great for codebase exploration, architecture summaries, documentation lookup, and repository research

Managed Auth

  • No OAuth setup, API keys, or developer credentials needed because DeepWiki MCP uses NO_AUTH
  • No auth_configs.create() or connected_accounts.link() flow required for this toolkit
  • Use Composio Tool Router sessions, or mcp.create() in custom MCP flows, to expose DeepWiki MCP tools to your agents

Agent Optimized Design

  • Tools are shaped for AI agents, so they can query repositories without brittle custom integration code
  • Execution logs show which DeepWiki MCP action ran, when it ran, and what repository your agent inspected
  • Here’s the thing: agents get useful codebase context without you building a repo-analysis pipeline from scratch

Enterprise Grade Security

  • Fine-grained RBAC controls which agents and users can access DeepWiki MCP tools
  • Safe access pattern for public GitHub repository analysis with no stored third-party credentials
  • Full audit trail of agent actions to support review, debugging, and compliance

Rolling this out across your team?

Give your team centralized access control across every framework with Composio’s MCP Gateway.

EXPLORE MCP GATEWAY
FAQ

Frequently asked questions

No. DeepWiki MCP requires no authentication, so you don't need OAuth credentials, API keys, or a custom developer app. Composio gives your agent a managed Tool Router or MCP connection to DeepWiki MCP tools, so it can analyze public GitHub repositories right away.

Yes! Composio's Tool Router enables agents to use multiple toolkits. Learn more.

Yes. Composio is SOC 2 Type II compliant and is built to keep your DeepWiki connection and credentials secure. OAuth tokens and API keys are encrypted, and sensitive customer data is protected at rest and in transit.

Composio also undergoes independent security testing and continuously monitors its systems for security threats. You can review the latest reports and policies in the Composio Trust Center.

Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.

When you connect a DeepWiki account through Composio, every action runs under that account, so anything the agent creates, sends, or changes shows up in DeepWiki as done by you. Keep an approval step in your prompt for actions with side effects, such as sending or deleting, and have the agent draft first.

Whatever the credentials you connect allow inside DeepWiki. If DeepWiki lets you scope a key to specific permissions, create a scoped one so the agent can only do what you intend. You can revoke the key inside DeepWiki at any time.

Yes. Composio supports multiple connected accounts for the same app, and that works in Claude, ChatGPT, or any other assistant you connect through Composio. Give each DeepWiki connection a name such as work or personal, and the assistant uses the one you mention in the request. Each account keeps its own credentials and nothing is merged.

Composio's free plan includes 100,000 tool calls per month with no credit card, which covers most personal DeepWiki use. Paid plans add higher limits and team features. Your DeepWiki plan and its API limits still apply as usual.

Built-in connectors usually give one AI access to a limited set of apps. Many people use Composio because it lets their AI connect to more apps than it normally supports, or connect to multiple accounts for the same app (e.g. connect Claude to multiple DeepWiki accounts).

With Composio, you connect DeepWiki once and then use it across different AI assistants without setting it up separately in each one. Connect your apps to Composio once, then connect Composio to whichever AI you use, whether that's Claude, ChatGPT, Hermes, or your own custom assistant.

Start with DeepWiki MCP.It takes 30 seconds.

Managed auth, hosted MCP servers, and every DeepWiki MCP tool your agent needs.Free to start.

Start building