Claude Code Explorer MCP

Community

Claude Code Explorer MCP - Explore the leaked source of Claude Code CLI

How to install ↓ Compare GitHub source repository ↗

Category: Dev Tools #435 of 438
Stars: ★ 3.4k Very popular
Transport: stdio (local process)
Runtime: Node.js
Credentials: No credential needed
License: Other / unspecified
Last commit: 43 days ago
Tools: 8

18FMRS · D

This MCP server acts as an unofficial exploration tool providing access to leaked Claude Code source. Its functionality is technically sound, but users should be aware of its unofficial nature.

Strongest · Maintenance 5/20 Weakest · Setup experience 2/20

Reliability

3/20

Security and permissions

4/20

Maintenance

5/20

Documentation

4/20

Setup experience

2/20

Why each score

Reliability 3/20: Only the README and manifest suggest 8 tools and 5 prompts, but no source code or test evidence beyond server.json is provided. The README labels the source as 'leaked' and 'not an official release'. Without actual implementation or tests, we cannot confirm the tools exist or complete the handshake. Static calibration caps reliability at 12 without execution evidence; here even the basic structure is unverifiable, so the score is minimal.
Security and permissions 4/20: The repository contains reportedly leaked proprietary Anthropic source code, with README explicitly stating it is 'not licensed for redistribution'. This is a major unresolved legal/licensing risk. As an MCP server, it requires access to the entire source tree (via CLAUDE_CODE_SRC_ROOT), but there is no evidence of least-privilege (e.g., read-only, path restrictions). The execution environment can run arbitrary commands (no restrictions mentioned in README). Due to the red-line risk, security is capped at 4.
Maintenance 5/20: The repo shows recent activity (3201 stars, 15 open issues), but has NOASSERTION license. The 'backup' branch preserves the 'original leak'. There is no security response channel, contribution guidelines aside from a note, or clear versioning policy. Given the legal warnings and lack of license, maintenance is poorly governed.
Documentation 4/20: README is detailed on installation and tool lists, but lacks specifics on parameters, limits, cost, or troubleshooting. The 8 tools and 5 prompts are claimed without detailed parameter schemas or examples. No evidence of reviewable docs (e.g., test files, run logs). Documentation is only indirectly linked to claimed functionality.
Setup experience 2/20: Installation instructions involve npm or building from source, requiring Node.js. However, static review does not verify dependencies or build process. No evidence of tests or CI configuration. With multiple manual steps and lack of execution verification, plus no clear platform compatibility, setup score is low.

Static review · not runListed 2026-08-07

Read the FMRS scoring method →

Fit and risk

What it can accessReads local files

Best for

Developers who want to deeply understand Claude Code internals
Technical writers or bloggers writing about Claude Code source
Contributors needing to debug or extend Claude Code

Not for

Users not interested in Claude Code
Developers who need to interact with Claude Code, not just read its source
Users looking for an officially supported or maintained server

Required permissions

Reads environment variable CLAUDE_CODE_SRC_ROOT if set to locate source
Runs local Node.js processes
Accesses network to download npm package (if using npx)

Risks and side effects

This server is based on unofficial leaked source, which may contain unreleased or unauthorized code
Using third-party npm packages presents supply chain risks
The source may be inaccurate or outdated as it is not an official release

Setup

Before you start

Runtime：Node.js

Other optional settings (1)

CLAUDE_CODE_SRC_ROOT optional Custom path pointing to the cloned repo's src/ directory; only needed when running from source, not required for the npm install; not a secret.

Install the npm package: npm install -g warrioraashuu-codemaster or use npx.
For Claude Code: run claude mcp add claude-code-explorer -- npx -y warrioraashuu-codemaster.
For Claude Desktop, add the provided JSON config to your config file.
For VS Code/Cursor, add the same config to .vscode/mcp.json or ~/.cursor/mcp.json.

claude_desktop_config.json

{
  "mcpServers": {
    "claude-code-explorer": {
      "command": "npx",
      "args": [
        "-y",
        "warrioraashuu-codemaster"
      ]
    }
  }
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json

{
  "servers": {
    "claude-code-explorer": {
      "command": "npx",
      "args": [
        "-y",
        "warrioraashuu-codemaster"
      ]
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal

claude mcp add claude-code-explorer -- npx -y warrioraashuu-codemaster

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After running claude mcp add warrioraashuu-codemaster -- npx -y warrioraashuu-codemaster, tools like list_tools and get_architecture should appear in the client's tool list; calling get_architecture and getting an architecture overview confirms the connection.

Troubleshooting

Ensure network connectivity for npx
Verify CLAUDE_CODE_SRC_ROOT points to the correct src/ directory
Ensure Node.js version is compatible (Node 14+ required)
Check MCP client configuration for correct command and args

Things to try

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

How does the BashTool work?
Search for where permissions are checked
Show me the /review command source
List all agent tools with their source files

Tools 8

list_tools read-only

List all ~40 agent tools with source files.

list_commands read-only

List all ~50 slash commands with source files.

get_tool_source read-only

Read the full source of any tool (e.g., BashTool, FileEditTool).

get_command_source read-only

Read source of any slash command (e.g., review, mcp).

read_source_file read-only

Read any file from src/ by path.

search_source read-only

Grep across the entire source tree.

list_directory read-only

Browse src/ directories.

get_architecture read-only

High-level architecture overview.

Use cases

Understanding the implementation of specific Claude Code tools

Searching the source for answers about commands or permissions

Browsing directory structure for a high-level understanding

Generating architectural documentation for tools or commands

Supported clients

Claude Desktop

Claude Code

VS Code

Cursor

Listed from the project's documentation, not tested by this site.

Overview

The Claude Code Explorer MCP server allows any MCP-compatible client (e.g., Claude Code, Claude Desktop, VS Code Copilot, Cursor) to explore the full source code of the Claude Code CLI interactively. It provides tools to list tools and commands, read source files, search across the 512K-line codebase, and get an architecture overview.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 62.9k · Tools 2 Compare with this →

NPM Sentinel MCP Server 79 · B

AI-powered NPM package analysis MCP server

★ 18 · Tools 19 Compare with this →

MartinLoop MCP Server 79 · B

An independent control layer that gives AI coding agents budgets, brakes, and receipts

★ 410 Compare with this →

GitHub MCP Server 76 · B

GitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language

★ 33.5k · Tools 15 Compare with this →

Compare with other MCP servers

More servers from this repository

Source revision eec3692193a3 Data synced 2026-10-12 Read the FMRS scoring method