Context7
Up-to-date docs for AI agents
作者提供的说明(英文原文)
Explore the Claude Code CLI source — browse tools, commands, search code, and more.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"codemaster": {
"command": "npx",
"args": [
"-y",
"@divyesh2000/codemaster"
]
}
}
}在终端中运行这条命令
claude mcp add codemaster -- npx -y @divyesh2000/codemaster粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"codemaster": {
"command": "npx",
"args": [
"-y",
"@divyesh2000/codemaster"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"codemaster": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@divyesh2000/codemaster"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
发布者(divu2025)不是仓库所有者(codeaashu);可能是其他人代为上架的
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.1.0)于7个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Context7, Codebase Memory, Exa
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
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.
| Transport | Endpoint | Best For |
|---|---|---|
| STDIO | node dist/index.js | Claude Desktop, local Claude Code, VS Code |
| Streamable HTTP | POST/GET /mcp | Modern MCP clients, remote hosting |
| Legacy SSE | GET /sse + POST /messages | Older MCP clients |
| Tool | Description |
|---|---|
list_tools | List all 40+ agent tools (BashTool, FileEditTool, etc.) |
list_commands | List all 50+ slash commands (/commit, /review, etc.) |
get_tool_source | Read a specific tool's implementation |
get_command_source | Read a specific command's implementation |
read_source_file | Read any file from src/ by relative path |
search_source | Regex search across the entire source tree |
list_directory | List contents of any directory under src/ |
get_architecture | Get a full architecture overview |
| URI | Description |
|---|---|
claude-code://architecture | README / architecture overview |
claude-code://tools | Tool registry (JSON) |
claude-code://commands | Command registry (JSON) |
claude-code://source/{path} | Any source file (template) |
| Prompt | Description |
|---|---|
explain_tool | Deep-dive explanation of a specific tool's purpose, schema, permissions, and flow |
explain_command | Explanation of a specific slash command's behavior and implementation |
architecture_overview | Guided tour of the full Claude Code architecture |
how_does_it_work | Explain a feature/subsystem (permissions, MCP, bridge, etc.) |
compare_tools | Side-by-side comparison of two tools |
cd mcp-server
npm install npm run build
npm start
CLAUDE_CODE_SRC_ROOT=/path/to/src npm start
npm run start:http
MCP_API_KEY=your-secret-token npm run start:http
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"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" } } } }
Add to .vscode/mcp.json in your workspace:
{
"servers": { "claude-code-explorer": { "type": "stdio", "command": "node", "args": ["${workspaceFolder}/mcp-server/dist/index.js"], "env": { "CLAUDE_CODE_SRC_ROOT": "${workspaceFolder}/src" } } } }
Add to ~/.cursor/mcp.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" } } } }
| Variable | Default | Description |
|---|---|---|
CLAUDE_CODE_SRC_ROOT | ../src (relative to dist/) | Path to the Claude Code src/ directory |
PORT | 3000 | HTTP server port (HTTP mode only) |
MCP_API_KEY | _(none)_ | Bearer token for HTTP auth (optional) |
For Claude Desktop connecting to a remote server:
{
"mcpServers": { "claude-code-explorer": { "url": "https://your-deployment.railway.app/mcp", "headers": { "Authorization": "Bearer your-secret-key" } } } }
mcp-server/DockerfileMCP_API_KEY — a secret bearer tokenPORT is set automatically by Railwayyour-app.railway.appOr via CLI:
railway init
railway up
npx vercel
Set environment variables in the Vercel dashboard:
CLAUDE_CODE_SRC_ROOT — path where src/ files are bundledMCP_API_KEY — bearer tokenNote: 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.
# From repo root
docker 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.
The server also exposes prompt templates for guided exploration:
| Prompt | Description |
|---|---|
explain_tool | Deep-dive explanation of a specific tool (input schema, permissions, execution flow) |
explain_command | Explain how a slash command works |
architecture_overview | Guided tour of the entire Claude Code architecture |
how_does_it_work | Explain a feature or subsystem (e.g. "permission system", "MCP client", "query engine") |
compare_tools | Side-by-side comparison of two tools |
Once connected, you can ask your AI assistant things like:
explain_tool prompt with "FileEditTool" to get a full breakdownhow_does_it_work with "bridge" to understand IDE integrationThis server is published to the MCP Registry via GitHub Actions. On a tagged release (v*), the workflow:
server.json metadata to the registryTo publish manually:
# Install the MCP Publisher CLI
curl -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
./mcp-publisher login github
cd mcp-server ../mcp-publisher publish
Registry name: warrioraashuu-codemaster
npm install
npm run dev # Watch mode TypeScript compilation npm run build # Compile TypeScript to dist/ npm start # Run STDIO server npm run start:http # Run HTTP server
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