MCP server exposing AST-based tools and graph representations for efficiently exploring codebases.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mcp-codebase-cartography","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# `mcp-codebase-cartography` This repository hosts the code for an MCP server exposing various tools aimed at efficiently exploring codebases without wasting tokens, using AST-based tools and graph representations. ## Usage MCP configuration `mcp.json`: ```json { "servers": { "mcp-codebase-cartography": { "type": "stdio", "command": "uvx", "args": ["mcp-codebase-cartography", "serve"] } } } ``` ### Building from source The server ships a native extension (`python-bindings/`) built with [maturin](https://www.maturin.rs). From `python-bindings/`, build and install it into the active virtual environment: ```sh maturin develop --release ``` or build a wheel and install it: ```sh maturin build --release pip install target/wheels/mcp_codebase_cartography-*.whl ``` ### Installing from PyPI The package is published to PyPI. Run it without installing via `uvx`, or install it with pip: ```sh uvx mcp-codebase-cartography serve pip install mcp-codebase-cartography ``` ### Releasing Releases are cut from semver tags. The version lives in `python-bindings/Cargo.toml` (`package.version`) and is read dynamically by `pyproject.toml`. 1. Bump `package.version` in `python-bindings/Cargo.toml`. 2. Run the quality gates (`cargo clippy`, `cargo test`, `uvx ruff check python-bindings`, `uv run pyrefly check python-bindings`). 3. Commit and push a matching tag: `git tag v0.1.0 && git push origin v0.1.0` (or `jj tag set v0.1.0`). Pushing a `vMAJOR.MINOR.PATCH` tag triggers `.github/workflows/release.yml`, which builds the sdist and wheels, verifies the tag matches the package version, publishes to PyPI, and creates a GitHub release with the artifacts. Prerequisite: PyPI [Trusted Publishing](https://docs.pypi.org/trusted-publishers/) must be configured for the `pypi` GitHub environment so the workflow can publish without a token. ### Repository root The server indexes the repository root, discovered from the process working directory by…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.