Skip to main content
Glama
deenesjakoruzh
regenrek

Deepwiki MCP Server

by regenrek
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Deepwiki MCP サーバー

これは非公式のDeepwiki MCPサーバーです

MCP 経由で Deepwiki URL を受け取り、関連するすべてのページをクロールし、それらを Markdown に変換して、1 つのドキュメントまたはページごとのリストを返します。

特徴

  • 🔒ドメインの安全性: deepwiki.com からの URL のみを処理します

  • 🧹 HTMLサニタイズ：ヘッダー、フッター、ナビゲーション、スクリプト、広告を削除します

  • 🔗リンク書き換え：Markdownで動作するようにリンクを調整します

  • 📄複数の出力形式：1つのドキュメントまたは構造化されたページを取得

  • 🚀パフォーマンス: 同時実行性と深度を調整できる高速クロール

  • NLP : 図書館名だけを検索する

Related MCP server: Markdown-To-Notion

使用法

使用できるプロンプト:

deepwiki fetch how can i use gpt-image-1 with "vercel ai" sdk
deepwiki fetch how can i create new blocks in shadcn?
deepwiki fetch i want to understand how X works

完全なドキュメントを取得する（デフォルト）

use deepwiki https://deepwiki.com/shadcn-ui/ui
use deepwiki multiple pages https://deepwiki.com/shadcn-ui/ui

シングルページ

use deepwiki fetch single page https://deepwiki.com/tailwindlabs/tailwindcss/2.2-theme-system

ショートフォームで取得

use deepwiki fetch tailwindlabs/tailwindcss
deepwiki fetch library

deepwiki fetch url
deepwiki fetch <name>/<repo>

deepwiki multiple pages ...
deepwiki single page url ...

カーソル

これを.cursor/mcp.jsonファイルに追加します。

{
  "mcpServers": {
    "mcp-deepwiki": {
      "command": "npx",
      "args": ["-y", "mcp-deepwiki@latest"]
    }
  }
}

ディープウィキロゴ

MCPツール統合

このパッケージは、MCP 互換クライアントで使用できるdeepwiki_fetchというツールを登録します。

{
  "action": "deepwiki_fetch",
  "params": {
    "url": "https://deepwiki.com/user/repo",
    "mode": "aggregate",
    "maxDepth": "1"
  }
}

パラメータ

  • url (必須): Deepwikiリポジトリの開始URL

  • mode (オプション): 出力モード。単一の Markdown ドキュメントの場合は「aggregate」(デフォルト)、構造化されたページデータの場合は「pages」のいずれか。

  • maxDepth （オプション）：クロールするページの最大深度（デフォルト：10）

応答フォーマット

成功応答（集約モード）

{
  "status": "ok",
  "data": "# Page Title\n\nPage content...\n\n---\n\n# Another Page\n\nMore content...",
  "totalPages": 5,
  "totalBytes": 25000,
  "elapsedMs": 1200
}

成功応答（ページモード）

{
  "status": "ok",
  "data": [
    {
      "path": "index",
      "markdown": "# Home Page\n\nWelcome to the repository."
    },
    {
      "path": "section/page1",
      "markdown": "# First Page\n\nThis is the first page content."
    }
  ],
  "totalPages": 2,
  "totalBytes": 12000,
  "elapsedMs": 800
}

エラー応答

{
  "status": "error",
  "code": "DOMAIN_NOT_ALLOWED",
  "message": "Only deepwiki.com domains are allowed"
}

部分的な成功応答

{
  "status": "partial",
  "data": "# Page Title\n\nPage content...",
  "errors": [
    {
      "url": "https://deepwiki.com/user/repo/page2",
      "reason": "HTTP error: 404"
    }
  ],
  "totalPages": 1,
  "totalBytes": 5000,
  "elapsedMs": 950
}

進捗イベント

ツールを使用すると、クロール中に進行状況イベントを受け取ります。

Fetched https://deepwiki.com/user/repo: 12500 bytes in 450ms (status: 200)
Fetched https://deepwiki.com/user/repo/page1: 8750 bytes in 320ms (status: 200)
Fetched https://deepwiki.com/user/repo/page2: 6200 bytes in 280ms (status: 200)

ローカル開発 - インストール

ローカル使用

{
  "mcpServers": {
    "mcp-deepwiki": {
      "command": "node",
      "args": ["./bin/cli.mjs"]
    }
  }
}

ソースから

# Clone the repository
git clone https://github.com/regenrek/deepwiki-mcp.git
cd deepwiki-mcp

# Install dependencies
npm install

# Build the package
npm run build

直接API呼び出し

HTTP トランスポートの場合、直接 API 呼び出しを行うことができます。

curl -X POST http://localhost:3000/mcp \
  -H "Content-Type: application/json" \
  -d '{
    "id": "req-1",
    "action": "deepwiki_fetch",
    "params": {
      "url": "https://deepwiki.com/user/repo",
      "mode": "aggregate"
    }
  }'

構成

環境変数

  • DEEPWIKI_MAX_CONCURRENCY : 最大同時リクエスト数（デフォルト: 5）

  • DEEPWIKI_REQUEST_TIMEOUT : リクエストタイムアウト（ミリ秒）（デフォルト: 30000）

  • DEEPWIKI_MAX_RETRIES : 失敗したリクエストの最大再試行回数（デフォルト: 3）

  • DEEPWIKI_RETRY_DELAY : 再試行バックオフの基本遅延（ミリ秒）（デフォルト: 250）

これらを設定するには、プロジェクト ルートに.envファイルを作成します。

DEEPWIKI_MAX_CONCURRENCY=10
DEEPWIKI_REQUEST_TIMEOUT=60000
DEEPWIKI_MAX_RETRIES=5
DEEPWIKI_RETRY_DELAY=500

Docker デプロイメント (未テスト)

Docker イメージをビルドして実行します。

# Build the image
docker build -t mcp-deepwiki .

# Run with stdio transport (for development)
docker run -it --rm mcp-deepwiki

# Run with HTTP transport (for production)
docker run -d -p 3000:3000 mcp-deepwiki --http --port 3000

# Run with environment variables
docker run -d -p 3000:3000 \
  -e DEEPWIKI_MAX_CONCURRENCY=10 \
  -e DEEPWIKI_REQUEST_TIMEOUT=60000 \
  mcp-deepwiki --http --port 3000

発達

# Install dependencies
pnpm install

# Run in development mode with stdio
pnpm run dev-stdio

# Run tests
pnpm test

# Run linter
pnpm run lint

# Build the package
pnpm run build

トラブルシューティング

よくある問題

  1. 権限が拒否されました: CLI の実行時に EACCES エラーが発生する場合は、バイナリを実行可能にしてください。

    chmod +x ./node_modules/.bin/mcp-deepwiki

  2. 接続が拒否されました: ポートが使用可能であり、ファイアウォールによってブロックされていないことを確認してください。

    # Check if port is in use
lsof -i :3000

  3. タイムアウト エラー: 大規模なリポジトリの場合は、タイムアウトと同時実行性を増やすことを検討してください。

    DEEPWIKI_REQUEST_TIMEOUT=60000 DEEPWIKI_MAX_CONCURRENCY=10 npx mcp-deepwiki

貢献

貢献を歓迎します！詳細はCONTRIBUTING.mdをご覧ください。

ライセンス

マサチューセッツ工科大学

リンク

コース

他のプロジェクトもご覧ください:

  • AIプロンプト- Cursor AI、Cline、Windsurf、Github Copilot向けに厳選されたAIプロンプト

  • codefetch - 簡単なターミナルコマンドでコードを LLM 用の Markdown に変換します

  • aidex AI言語モデルに関する詳細な情報を提供し、開発者がニーズに合った適切なモデルを選択できるように支援するCLIツール。# tool-starter

Available Tools

1 tool
deepwiki_fetchC

Fetch a deepwiki.com repo and return Markdown

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesshould be a URL, owner/repo name (e.g. "vercel/ai"), a two-word "owner repo" form (e.g. "vercel ai"), or a single library keyword
maxDepthNoCan fetch a single site => maxDepth 0 or multiple/all sites => maxDepth 1
modeNoaggregate
verboseNo

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions fetching and returning Markdown but omits critical details like authentication requirements, rate limits, error handling, or whether this is a read-only operation. For a tool with no annotation coverage, this is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise—a single sentence that directly states the tool's purpose. Every word earns its place, with no unnecessary elaboration. It's front-loaded and efficiently communicates the core functionality.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (4 parameters, 50% schema coverage, no output schema, no annotations), the description is inadequate. It doesn't explain what 'fetching' entails, how the Markdown is structured, error conditions, or usage constraints. For a tool with significant undocumented aspects, more context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%, with only the 'url' parameter well-documented in the schema. The description adds no parameter-specific information beyond what the schema provides. It doesn't explain the meaning of 'maxDepth', 'mode', or 'verbose' parameters, leaving gaps in understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('fetch') and resource ('deepwiki.com repo'), and specifies the output format ('return Markdown'). It distinguishes the tool by mentioning the specific domain (deepwiki.com) and output type. However, without sibling tools, there's no explicit differentiation from alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus other methods or tools. It lacks context about prerequisites, typical use cases, or limitations. With no sibling tools mentioned, it doesn't address alternatives within the server.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as fetching a Deepwiki repo and returning Markdown, making it impossible to confuse with any other tool.

Naming Consistency5/5

The single tool name follows a consistent verb_noun pattern (deepwiki_fetch), and with only one tool, there is no inconsistency to evaluate. The naming is clear and adheres to a predictable structure.

Tool Count2/5

A single tool is generally too few for a server's purpose, as it limits functionality and may indicate an incomplete surface. For a Deepwiki server, one tool feels thin and under-scoped, lacking operations like search, update, or list repos that might be expected.

Completeness2/5

The server is severely incomplete for interacting with Deepwiki repos. It only provides a fetch operation, missing essential CRUD/lifecycle coverage such as creating, updating, deleting, or searching repos, which are likely needed for full agent workflows in this domain.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/regenrek/deepwiki-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server