Claude Code Explorer MCP

io.github.divu2025由 GitHub 账号 divu2025 发布v1.1.0更新于 Oct 24, 2026

Explore the Claude Code CLI source — browse tools, commands, search code, and more.

发布方自己的服务:Claude Platform Docs

已验证STDIO仅桌面知识与记忆开发者工具

概览

AI 生成的概览

一个本地 MCP 服务器,让助手浏览、搜索并阅读 Claude Code CLI 源码树、其中的工具、斜杠命令与整体架构。

可以做什么
列出 Claude Code 源码中定义的代理工具与斜杠命令,并以资源形式提供注册表,附有引导式讲解与工具对比提示。读取某个工具或命令的实现,或按相对路径读取源码目录下的任意文件,包括指定行范围。对整个源码树做正则搜索并列出目录内容,以定位代码。获取代码库架构总览,并讲解权限、MCP 客户端、bridge 等子系统。
适用场景
适合让助手回答 Claude Code 如何实现的问题、定位某个工具或命令的代码位置,或研究其权限与 MCP 子系统,而无需手动在大型代码库中检索。
运行要求
需要 Node.js 以 stdio 方式在本地运行该 npm 包,并需要一份本地 Claude Code 源码副本;源码路径通过环境变量 CLAUDE_CODE_SRC_ROOT 指定。HTTP 与 SSE 模式使用 PORT,可选 MCP_API_KEY。
安装前请注意
HTTP 模式仅在设置了 MCP_API_KEY 时才有保护,未设置时端点无鉴权,而 README 建议将其公开部署。服务器会读取所配置目录中的源码文件,请将 CLAUDE_CODE_SRC_ROOT 指向你愿意让助手访问的代码树。README 中的品牌与包名与注册表条目不一致,安装前请确认是预期的包。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Claude Code Explorer MCP,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

warrioraashuu Codemaster — MCP Server

A standalone Model Context Protocol (MCP) server that lets any MCP-compatible client explore the Claude Code source code. Rebranded and published by warrioraashuu. Supports STDIO, Streamable HTTP, and SSE transports.

What It Does

Exposes 8 tools, 3 resources, and 5 prompts for navigating the ~1,900-file, 512K+ line Claude Code codebase. This is the official npm package: warrioraashuu-codemaster.

Transports

TransportEndpointBest For
STDIOnode dist/index.jsClaude Desktop, local Claude Code, VS Code
Streamable HTTPPOST/GET /mcpModern MCP clients, remote hosting
Legacy SSEGET /sse + POST /messagesOlder MCP clients

Tools

ToolDescription
list_toolsList all 40+ agent tools (BashTool, FileEditTool, etc.)
list_commandsList all 50+ slash commands (/commit, /review, etc.)
get_tool_sourceRead a specific tool's implementation
get_command_sourceRead a specific command's implementation
read_source_fileRead any file from src/ by relative path
search_sourceRegex search across the entire source tree
list_directoryList contents of any directory under src/
get_architectureGet a full architecture overview

Resources

URIDescription
claude-code://architectureREADME / architecture overview
claude-code://toolsTool registry (JSON)
claude-code://commandsCommand registry (JSON)
claude-code://source/{path}Any source file (template)

Prompts

PromptDescription
explain_toolDeep-dive explanation of a specific tool's purpose, schema, permissions, and flow
explain_commandExplanation of a specific slash command's behavior and implementation
architecture_overviewGuided tour of the full Claude Code architecture
how_does_it_workExplain a feature/subsystem (permissions, MCP, bridge, etc.)
compare_toolsSide-by-side comparison of two tools

Setup

bash
cd mcp-servernpm installnpm run build

Run Locally (STDIO)

bash
npm start# or with custom source path:CLAUDE_CODE_SRC_ROOT=/path/to/src npm start

Run Locally (HTTP)

bash
npm run start:http# Streamable HTTP at http://localhost:3000/mcp# Legacy SSE at http://localhost:3000/sse# Health check at http://localhost:3000/health

With Authentication

bash
MCP_API_KEY=your-secret-token npm run start:http# Clients must include: Authorization: Bearer your-secret-token

Configuration

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json
{  "mcpServers": {    "warrioraashuu-codemaster": {      "command": "node",      "args": ["/absolute/path/to/claude-code/mcp-server/dist/index.js"],      "env": {        "CLAUDE_CODE_SRC_ROOT": "/absolute/path/to/claude-code/src"      }    }  }}

VS Code (GitHub Copilot)

Add to .vscode/mcp.json in your workspace:

json
{  "servers": {    "claude-code-explorer": {      "type": "stdio",      "command": "node",      "args": ["${workspaceFolder}/mcp-server/dist/index.js"],      "env": {        "CLAUDE_CODE_SRC_ROOT": "${workspaceFolder}/src"      }    }  }}

Cursor

Add to ~/.cursor/mcp.json:

json
{  "mcpServers": {    "claude-code-explorer": {      "command": "node",      "args": ["/absolute/path/to/claude-code/mcp-server/dist/index.js"],      "env": {        "CLAUDE_CODE_SRC_ROOT": "/absolute/path/to/claude-code/src"      }    }  }}

Environment Variables

VariableDefaultDescription
CLAUDE_CODE_SRC_ROOT../src (relative to dist/)Path to the Claude Code src/ directory
PORT3000HTTP server port (HTTP mode only)
MCP_API_KEY(none)Bearer token for HTTP auth (optional)

Remote HTTP Client Configuration

For Claude Desktop connecting to a remote server:

json
{  "mcpServers": {    "claude-code-explorer": {      "url": "https://your-deployment.railway.app/mcp",      "headers": {        "Authorization": "Bearer your-secret-key"      }    }  }}

Deployment

Railway

  1. Connect your GitHub repo to Railway
  2. Railway automatically detects the mcp-server/Dockerfile
  3. Set environment variables in the Railway dashboard:
    • MCP_API_KEY — a secret bearer token
    • PORT is set automatically by Railway
  4. Deploy — available at your-app.railway.app

Or via CLI:

bash
railway initrailway up

Vercel

bash
npx vercel

Set environment variables in the Vercel dashboard:

  • CLAUDE_CODE_SRC_ROOT — path where src/ files are bundled
  • MCP_API_KEY — bearer token

Note: Vercel functions are stateless with execution time limits (10s hobby / 60s pro). Best for simple tool calls. For persistent SSE streams, use Railway or Docker.

Docker

bash
# From repo rootdocker build -f mcp-server/Dockerfile -t claude-code-mcp .docker run -p 3000:3000 -e MCP_API_KEY=your-secret claude-code-mcp

Works on any Docker host: Fly.io, Render, AWS ECS, Google Cloud Run, etc.

Prompts

The server also exposes prompt templates for guided exploration:

PromptDescription
explain_toolDeep-dive explanation of a specific tool (input schema, permissions, execution flow)
explain_commandExplain how a slash command works
architecture_overviewGuided tour of the entire Claude Code architecture
how_does_it_workExplain a feature or subsystem (e.g. "permission system", "MCP client", "query engine")
compare_toolsSide-by-side comparison of two tools

Example Usage

Once connected, you can ask your AI assistant things like:

  • "List all Claude Code tools"
  • "Show me the BashTool implementation"
  • "Search for how permissions are checked"
  • "What files are in the bridge directory?"
  • "Read the QueryEngine.ts file, lines 1-100"
  • "How does the MCP client connection work?"
  • Use the explain_tool prompt with "FileEditTool" to get a full breakdown
  • Use how_does_it_work with "bridge" to understand IDE integration

Publishing to MCP Registry

This server is published to the MCP Registry via GitHub Actions. On a tagged release (v*), the workflow:

  1. Publishes the npm package to npmjs.org
  2. Authenticates with the MCP Registry using GitHub OIDC
  3. Publishes the server.json metadata to the registry

To publish manually:

bash
# Install the MCP Publisher CLIcurl -L "https://github.com/modelcontextprotocol/registry/releases/latest/download/mcp-publisher_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher
# Authenticate (GitHub OAuth)./mcp-publisher login github
# Publishcd mcp-server../mcp-publisher publish

Registry name: warrioraashuu-codemaster

Development

bash
npm installnpm run dev    # Watch mode TypeScript compilationnpm run build  # Compile TypeScript to dist/npm start      # Run STDIO servernpm run start:http  # Run HTTP server

Architecture

mcp-server/├── src/│   ├── server.ts    — Shared MCP server (tools, resources, prompts) — transport-agnostic│   ├── index.ts     — STDIO entrypoint (local)│   └── http.ts      — HTTP + SSE entrypoint (remote)├── api/│   ├── index.ts     — Vercel serverless function│   └── vercelApp.ts — Express app for Vercel├── Dockerfile       — Docker build (Railway, Fly.io, etc.)├── railway.json     — Railway deployment config├── package.json└── tsconfig.json

来源:mcp-server/README.md,提交 eec3692

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v1.1.0最新Sep 16, 2026

评分

已满足适用检查项的 40%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。

其他 Claude 集成