Claude Code Explorer MCP

io.github.divu2025Published by GitHub account divu2025v1.1.0Updated Oct 24, 2026

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

The publisher's own server: Claude Platform Docs

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A local MCP server that lets an assistant browse, search and read the Claude Code CLI source tree, its tools, slash commands and architecture.

What you can do
List the agent tools and slash commands defined in the Claude Code source, with registries as resources and prompts for guided explanations and comparisons of tools and commands. Read a specific tool's or command's implementation, or any file under the source directory by relative path, including line ranges. Regex-search the whole source tree and list directory contents to locate code. Get an architecture overview of the codebase and explain subsystems such as permissions, MCP client or bridge.
When to use it
Useful when you want an assistant to answer questions about how Claude Code is built, find where a tool or command is implemented, or study its permission and MCP subsystems, without manually grepping a large codebase.
Requirements
Node.js to run the npm package locally over stdio, plus a local copy of the Claude Code source; the source path is set with the CLAUDE_CODE_SRC_ROOT environment variable. HTTP and SSE modes use PORT and optionally MCP_API_KEY.
Before you install
The HTTP mode is protected only if MCP_API_KEY is set; without it the endpoint is unauthenticated, and the README suggests deploying it publicly. The server reads source files from the configured directory, so point CLAUDE_CODE_SRC_ROOT at a tree you are willing to expose to the assistant. The README's branding and package names differ from the registry entry, so verify you are installing the intended package.

Installation

In SourceWeft

  1. Open Claude Code Explorer MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

Source: mcp-server/README.md at commit eec3692

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Claude integrations