DeepWiki MCP — Remote MCP Server

DeepWiki indexes public GitHub repositories into conversational wikis, and its MCP server exposes that as three simple tools: read a repo's wiki structure, read wiki contents, or ask a question about the repo. It is free, requires no authentication, and speaks both Streamable HTTP and legacy SSE — which makes it the de-facto 'hello world' endpoint for remote MCP development.

Endpoint & Transport

• Endpoint URL: https://mcp.deepwiki.com/mcp
• Legacy SSE endpoint: https://mcp.deepwiki.com/sse
• Transport: Streamable HTTP + legacy SSE

Authentication

DeepWiki MCP is public and unauthenticated — no OAuth, no API key, no headers. Any MCP client can connect and call its tools directly, which also makes it a great endpoint for smoke-testing your own MCP client or proxy.

Available Tools (3)

Connect in 30 Seconds

Claude Code — one command:

claude mcp add --transport http deepwiki https://mcp.deepwiki.com/mcp

Cursor — add to ~/.cursor/mcp.json:

{ "mcpServers": { "deepwiki": { "url": "https://mcp.deepwiki.com/mcp" } } }

VS Code — add to .vscode/mcp.json:

{ "servers": { "deepwiki": { "type": "http", "url": "https://mcp.deepwiki.com/mcp" } } }

Claude Desktop & stdio clients — bridge with mcp-remote:

{ "mcpServers": { "deepwiki": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.deepwiki.com/mcp"] } } }

Troubleshooting

• Which URL should I use? Prefer https://mcp.deepwiki.com/mcp (Streamable HTTP). The SSE URL is only for older clients pinned to the pre-2025-03-26 spec.
• "Session expired" / stale Mcp-Session-Id — just re-send initialize; stateless clients can ignore session headers entirely.
• No auth and free — a great endpoint for validating client implementations.
• Works for public repos indexed on deepwiki.com; private repos need Devin.