code-explorer-mcp
A local FastMCP server that provides deterministic code-exploration primitives for Python and TypeScript repositories.
Parsing behavior notes
- Python and TypeScript class parsing intentionally expose nested classes only one level deep. A top-level class may include direct
inner_classes, but classes nested deeper than that are ignored.
Client setup
This server inspects the current working directory by default, or an explicit path when you pass --path.
Recommended install
Install the server as a tool:
uv tool install code-explorer-mcp
This makes code-explorer-mcp and code-explorer-node-setup available as global commands if your uv tool bin directory is on PATH.
If you prefer pipx:
pipx install code-explorer-mcp
TypeScript parser setup
Python parsing works after install. TypeScript parsing also requires Node.js and npm plus one bootstrap step:
- Install Node.js and npm.
- Run:
code-explorer-node-setup
code-explorer-node-setup checks that node and npm are available, then installs the TypeScript parser runtime inside the installed package.
Run the server
- Installed package:
code-explorer-mcp - Installed package with explicit target repo:
code-explorer-mcp --path /path/to/repo - Local checkout:
uv run code-explorer-mcp - Local checkout with explicit target repo:
uv run code-explorer-mcp --path /path/to/repo
Example MCP client config
Claude Code:
claude mcp add --transport stdio code-explorer -- code-explorer-mcp --path /path/to/repo
Generic stdio configuration:
{
"mcpServers": {
"code-explorer": {
"command": "code-explorer-mcp",
"args": ["--path", "/path/to/repo"]
}
}
}
If you installed with pipx, the command stays code-explorer-mcp and the setup command is code-explorer-node-setup.
Install from source
For local development or GitHub installs:
- Sync Python dependencies:
uv sync
- Install the Node dependencies required by the TypeScript parser runtime:
uv run code-explorer-node-setup
- Run the server from the repository you want to inspect:
uv run code-explorer-mcp- or from anywhere with an explicit target:
uv run code-explorer-mcp --path /path/to/repo
Metadata
Release files for code-explorer-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| code_explorer_mcp-0.2.0.tar.gz | 31.3 kB | With provenance | Details for code_explorer_mcp-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| code_explorer_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for code_explorer_mcp-0.2.0-py3-none-any.whl |
Total release size: 59.7 kB
Release files / code_explorer_mcp-0.2.0.tar.gz
| Download URL | code_explorer_mcp-0.2.0.tar.gz |
|---|---|
| Size | 31.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
432b02d04c9624322c04b41b5d6a84224ebf8df6d6a7a13cfcf3a1b7b0f33661
|
|
BLAKE2b-256 checksum How to use checksums |
4203ac14a1f9326912c660495f5b0a3aac0082322308de4414cdc1e5784a80a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 21, 2026.
Transparency logRelease files / code_explorer_mcp-0.2.0-py3-none-any.whl
| Download URL | code_explorer_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 28.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a2a3570ce18869cae9e5904d0ab809d53fd50b324d73d71debbe55af995c147d
|
|
BLAKE2b-256 checksum How to use checksums |
c5caab94cead27d74c257958c35c02562e9a61cc96c421ae2a4d5d0bb416da82
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 21, 2026.
Transparency logSecurity for code-explorer-mcp 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for code_explorer_mcp-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.