Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

RepoGraph MCP

Release candidate: RepoGraph Canvas 0.2.0rc4 / kit 0.2.0-rc.4. Explore a repository, follow a change's potential impact, inspect source evidence and preview proposed edits without changing files. The light interface works as an offline HTML export or an embedded MCP Apps view in supporting hosts. Includes guided tours, test suggestions and clearly labelled agent interpretations. See Canvas usage and limits. Use the explicit Canvas prerelease; the stable 0.1.2 channel remains separate:

npx repograph-kit@0.2.0-rc.4 canvas --enable-verification

With the new kit installed, run repograph-kit canvas --enable-verification in your repository. It opens a live map with whole-repository search, change impact, test selection and reviewed/approved execution. Omit the flag for analysis only. On Windows PowerShell use repograph-kit.cmd if script policy blocks .ps1.

Stable release: repograph-kit 0.1.2, bundling Python candidate 0.1.0rc4 and skill 1.0.2. Adds native Node verification, upgrades preserving client tool policies, focused uncertainty candidates, batched/scoped Git comparison and separate verification-input readiness. See release acceptance for publication status. Standalone 0.1.0rc1 artifacts remain unchanged. See the real-repository acceptance follow-up for measured results and remaining limits.

Local, model-agnostic repository intelligence using the Model Context Protocol. No LLM API key, cloud database, Docker, or telemetry is required.

The published repograph-kit npm installer packages the server and skill with project setup for Codex, Claude Code, Cursor and VS Code Copilot. Public registry installation and setup passed; see release acceptance.

Latest practical review

On a 361-file JavaScript/JSX project (4.93 MB of source), rc3 corrected Node test detection and Git ownership-trust handling. Indexing/navigation speed was broadly similar to rc2. The local review measured:

Operation rc2 rc3
Index 361 files 8.66 s 8.63 s
Cached refresh 3.70 s 3.25 s
Symbol lookup 123 ms 125 ms
Dependency lookup 117 ms 130 ms
Discover tests 278 ms 310 ms
Impact analysis 0.93 s 1.12 s

These are local engine measurements excluding MCP/model/approval overhead. Lookup/discovery timings are medians of three calls; indexing/impact timings are single samples. Small differences do not establish a speed improvement/regression. rc3 correctly identified 20 Node test files and 57 lexical tests. The sampled change still selected all 20 files (one graph-linked plus 19 fallback files). Full Git comparison took 16.58 seconds and was incomplete on oversized tracked archives/bundles. Parser recovery and unresolved relationships remain limitations; the unresolved-edge percentage is not an accuracy/error rate.

Improvements in 0.1.2 / Python rc4

  • Preserve client-added per-tool approval settings when upgrading the server path. Updating the npm package alone does not replace an active MCP connection.
  • Add approved, bounded Node built-in test execution with machine-readable results. Real execution checks passed on Node 22/24 across Linux, Windows and macOS.
  • Map literal dynamic imports and separate focused test evidence from specific uncertainty candidates. A local static follow-up now identifies two receipt test files plus four fallback candidates, rather than all 20 files. Broader testing is still recommended; this is not proof that excluded tests cannot regress.
  • Batch Git attribute/blob-size metadata and support explicit comparison scopes: get_changes(paths=["src", "tests"]), or repeated CLI --change-path flags. Full-repository limitations remain visible; scoped completeness covers only the requested paths.

See candidate checks and real-project follow-up. Repeated local Git profiling measured a 12.56-second rc3 median and a 1.61-second candidate median (three samples each), retaining the same incomplete 19-change report. This is a local observation, not a general latency guarantee. Doctor now also distinguishes source readiness from non-source verification-input blockers.

Published 0.1.2 includes Node execution; 0.1.1 was discovery-only. All 26 release CI jobs passed. Trials across additional real projects continue before wider promotion. No GUI-client certification or general speed/accuracy claim is implied.

Get started

With Node 22+ and either uv or Python 3.11-3.13, run in the target repository:

npm i repograph-kit
npx repograph-kit setup

Choose an agent, reload it, and approve its MCP connection if prompted. Setup checks source limits, Git availability and runner evidence without running tests. For an existing stock install, run npm i repograph-kit@0.1.2, then npx repograph-kit setup --agent codex --upgrade and npx repograph-kit doctor --agent codex (replace codex with your agent). Optional --enable-verification opts in to reviewed test execution; each concrete plan still requires approval. Use framework node:test for native Node tests. Exclude custom generated output with Git-style rules in .repographignore before retrying an oversized-file failure. Doctor does not prove a successful index/GUI connection. See npm setup for options and requirements. After upgrading, confirm health reports 0.1.0rc4 and re-index once for the new extractor/resolver policy. Doctor can report source indexing ready while deployment archives still block verification fingerprints; review their exclusions/limits. To install the standalone Python server from this source checkout instead:

Install Python 3.12 and uv, then from this checkout:

uv sync --locked --no-dev --python 3.12
.venv/bin/repograph --root /absolute/repository overview
.venv/bin/repograph --root /absolute/repository index
.venv/bin/repograph --root /absolute/repository overview

On Windows, use .venv/Scripts/repograph.exe. overview reports saved index state; index reads supported files without executing repository code. For development checks, wheel installation and troubleshooting, see installation.

MCP clients

Use the installed executable as a local stdio server. The client starts it on demand with an absolute --root; no background service or port is needed. See Codex, Claude Code, Cursor and VS Code setup. Protocol connectivity is tested with the official SDK; GUI clients have not been manually certified.

Optional companion skill

The Apache-2.0 RepoGraph skill teaches agents to explore dependencies, assess potential change impact and choose tests with evidence. It uses an existing local MCP connection; the server also works independently. See packaging and installation for the installable ZIP, client skill locations and marketplace draft.

Implemented scope

Phases 1–7 are implemented: stdio MCP, CLI, configuration, JSON stderr logs, SQLite migrations/cache, nested .gitignore discovery, SHA-256 hashing, and Tree-sitter extraction for Python, JavaScript/JSX, TypeScript, and TSX. MCP tools: health, list_files, parse_file, scan_repository; resource: repograph://status. Parse/list tools paginate with offset and limit (max 200). Phase 3 adds index_repository, query_symbols, and get_dependencies, plus repograph index and repograph symbols SEARCH. Static graph publication is transactional and preserves unresolved references and cyclic dependencies. Phase 4 adds set_baseline, get_changes, get_changed_symbols, and compare_snapshots. Git analysis includes staged/unstaged and commit changes, rename evidence, changed symbols and bounded line ranges. Git must be installed on the host; configure its working-tree root as the repository boundary. Phase 5 adds analyze_impact and repograph impact [PATH]: direct/transitive potential dependents, evidence chains, affected modules, stale-graph checks and explicit uncertainty. Index first; retain a before snapshot for deleted code. Phase 6 adds static test discovery, evidence-backed suggestions, reviewed verification plans, bounded pytest/Jest/Vitest/Node runs and saved regression comparisons. Execution is disabled by default and requires host opt-in plus explicit approval. Phase 7 adds get_repository_overview, the repograph://overview resource and repograph overview CLI command, plus local installation and client guides.

.venv/bin/repograph --root /absolute/repository index
.venv/bin/repograph --root /absolute/repository symbols Invoice
.venv/bin/repograph --root /absolute/repository baseline HEAD
.venv/bin/repograph --root /absolute/repository changes
.venv/bin/repograph --root /absolute/repository --target INDEX changes
.venv/bin/repograph --root /absolute/repository --baseline HEAD~1 --target HEAD changes
.venv/bin/repograph --root /absolute/repository --before SNAPSHOT_A --after SNAPSHOT_B snapshot-diff

Configure limits before the command, for example:

.venv/bin/repograph --root /absolute/repository --max-files 5000 --max-file-bytes 1000000 scan

Source must be UTF-8. Links, dependency/build directories, and RepoGraph state are excluded. Computed imports remain unresolved; literal JS dynamic imports add heuristic local-module evidence. Cross-file resolution supports the documented static patterns; runtime behavior remains uncertain. GUI clients have not been manually certified.

Change reports with complete=false contain explicit limitations. Filters are never executed, binary/unsupported data lacks symbol detail, and heuristic renames/call targets remain candidates. Git comparison honors local text/eol settings and the host's safe core.autocrlf scalar, while suppressing other global/system Git configuration during analysis.

See verification workflow for interpreter setup, reviewed commands, execution gates and limitations. Phase 8 adds reproducible benchmarks, adversarial regression tests, container boundary validation, a compatibility matrix and host-only history maintenance.

Version 0.1.0rc1 is an Apache-2.0 release candidate, available as a GitHub prerelease. The full remote matrix, public-wheel installation and TestPyPI publication/installation passed. Production PyPI still requires its separate trusted-publisher registration. See the demo, release procedure, changelog, contributing guide and security policy.

See architecture, contracts, and roadmap for scope and limitations.

Metadata

Release files for repograph-mcp 0.2.0rc4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for repograph-mcp 0.2.0rc4
File Size Uploaded Provenance Actions
repograph_mcp-0.2.0rc4.tar.gz 482.7 kB With provenance Details for repograph_mcp-0.2.0rc4.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for repograph-mcp 0.2.0rc4
File Interpreter ABI Platform Actions
repograph_mcp-0.2.0rc4-py3-none-any.whl Python 3 none any Details for repograph_mcp-0.2.0rc4-py3-none-any.whl

Total release size: 752.2 kB

Release files / repograph_mcp-0.2.0rc4.tar.gz

Download URL repograph_mcp-0.2.0rc4.tar.gz
Size 482.7 kB
Tags Source
SHA-256 checksum
How to use checksums
7976a80ed0edb10be6b4a3b4929ec5b08591b02fbda0c355d9b771d928ad7ec8
BLAKE2b-256 checksum
How to use checksums
9be6cf7d37aa3a010c8fc22d68cef161713f58288ede7e10c924f578494088b0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Release files / repograph_mcp-0.2.0rc4-py3-none-any.whl

Download URL repograph_mcp-0.2.0rc4-py3-none-any.whl
Size 269.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
12f24f2af7ab0b7b6370773f20a57558aa6ade30680c6ff6cbd3adb92aec37fb
BLAKE2b-256 checksum
How to use checksums
4b964958ed668111bfefa8cdf0d0d0db4fa33c539b089501eb17801e0f5bc5a4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 12, 2026.

Transparency log

Security for repograph-mcp 0.2.0rc4

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.

Select from 2 files

Attestation for repograph_mcp-0.2.0rc4.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 Nov 12, 2026.

Transparency log

A 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.

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page