zzop MCP server
Commit Nov 3, 2026Analyzes repository dependency graphs and performs cross-tree joins to identify connectivity gaps between frontend and backend codebases.
Also known as eezz4/zzop
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.41.0
- Last commit
- Nov 3, 2026
- License
- MIT
What is zzop MCP?
zzop analyzes repository dependency graphs and performs cross-tree joins to identify connectivity gaps between frontend and backend codebases.
Summary generated from the project's README
About zzop MCP server
zzop acts as a kernel for analyzing repository dependency graphs to find connectivity gaps between different codebases. It is designed for developers who need to verify that frontend calls correctly reach backend routes. The tool converts source code into a language-neutral intermediate representation to build dependency graphs and perform cross-tree joins. It works locally and does not make network requests or write code, ensuring that the same commit always produces the same findings.
Users can interact with the system via the zzop CLI or through the zzop-mcp server using stdio. The MCP server allows AI agents to access specific tools like analyze_repo, cross_repo, and check_endpoint. While it includes built-in parsers for TypeScript, JavaScript, Python, Java, C#, Go, Rust, Prisma, and SQL, it is built to be extensible. Developers can inject their own parsers or rule packs to handle custom stacks or specific project conventions.
What you can do with it
- 1Identify broken API connectionsFind instances where a frontend mutation call does not reach a corresponding backend endpoint.
- 2Verify repository coverageDetermine how much of a specific codebase the analyzer is actually able to see and parse.
- 3Debug specific endpointsInvestigate why a particular HTTP method and path are not successfully joining between two trees.
- 4Automate CI failure logicConfigure continuous integration to fail only when findings reach a specific severity level.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableeezz4/zzop is public and reachablegithub.com/eezz4/zzop ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-03github.com/eezz4/zzop ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubzzop ( Zero Zone Of Pain )
zzop reads a whole repository and answers the same way every time — one tree, or a frontend and a backend joined so you can see which calls reach which routes and which reach nothing.
zzop is a kernel you attach to your own source environment. It turns source into one language-neutral IR, builds the dependency graph and the cross-tree join over it, runs rules, and writes one JSON reply that says what it found and what it could not see. What it reads and what it judges is yours to inject: a parser or adapter for your stack (a Normalized AST envelope, or an overlay on top of a native parse), your own conventions in the config, your own rule packs. Each run names the next gap and how to fill it.
Built-in parsers and rule packs ship on by default — TypeScript/JavaScript, Python, Java, C#, Go and
Rust, plus Prisma and SQL schemas. They are an option, not the product: the Cargo feature
builtin-units carries them, and cargo build -p zzop-cli-bin --no-default-features builds the kernel
alone, which analyzes only what an envelope or overlay hands it.
Same commit in, same findings out. zzop never writes code and makes no network request.
Install
Every lane installs the same two Node-free binaries: zzop (the CLI) and zzop-mcp (an MCP server
over stdio, for AI agents).
| Lane | How |
|---|---|
| Binary | Download zzop-cli-<platform>[.exe] and/or zzop-mcp-<platform>[.exe] from GitHub Releases. Each release carries a SHA256SUMS asset: sha256sum -c SHA256SUMS --ignore-missing. |
| npm | npm i -g @zzop/cli — the same native zzop binary, fetched for your platform (packages/cli/README.md). |
| Claude Code | /plugin marketplace add eezz4/zzop, then /plugin install zzop@zzop. The plugin fetches zzop-mcp on the first session; restart once and the tools appear. On Windows the fetch needs a POSIX shell (Git for Windows). |
| Claude Desktop | The one-click zzop-mcp-<platform>.mcpb bundle from the same release. Read BUNDLE-README.md before installing (updates are manual; macOS Gatekeeper; privacy). |
| Any MCP client | Run zzop-mcp (bare, or zzop-mcp mcp) as a stdio server. |
| Source | cargo build -p zzop-cli-bin -p zzop-mcp --release (CONTRIBUTING.md). |
Which tags carry release assets is owned by VERSIONING.md.
First three commands
A config is required — zzop guesses nothing about your project that you did not declare. Put one config at the top of your workspace; every tree under it finds it by walking up.
cd ~/work/shop # holds ./api and ./web, each its own git repository
zzop init # writes zzop.config.jsonc here, declares both repos as `trees`
zzop analyze ./api # one tree
zzop cross ./api ./web # the join between them
zzop init on that layout prints what it did and the next step:
wrote .\zzop.config.jsonc
added `**/.zzop/` to .\.gitignore
declared the 2 repositories under it as `trees`: api, web
next: `zzop cross .\api .\web` joins them under this one config; `zzop analyze .\api` reads one of them alone.
and zzop cross answers with a short screen:
zzop cross — ./api ./web (2 trees)
read 2 of 4 files parsed across 2 trees
joined 1 edges, 1 of them between trees (http 1)
findings cross-layer 2 (warning 2)
warning cross-layer/unconsumed-mutation-endpoint src/server.ts:9 (./api)
warning cross-layer/unprovided-mutation-call src/users.ts:7 (./web)
...
next zzop endpoint "PUT /api/users/me" ./api ./web — who provides and who calls the first row's key, and why they did or did not join
full ...\shop\.zzop\last-cross.json (38 KB, every value with its meaning — `--json` prints it here instead)
Getting started continues from here: attaching an overlay for a route zzop cannot see, adding your own rule pack, and quieting a finding.
Reading the output
- The screen (stdout, default) — what was read, what was not, the finding counts and first rows,
and one
nextstep. Follow thenextline; it is how zzop guides you to the gap that matters. .zzop/last-<command>.json— the full reply, written beside the config that governed the run. It explains itself: its blocks carry…Meaningfields saying what each value is and is not.zzop initgit-ignores.zzop/, which also holds the per-file cache (safe to delete;"cacheDir": nullwrites no cache).--json— prints the full reply on stdout instead and writes nothing. Use it from scripts.
Every finding carries a rule id, a severity, a file and line, and a message. findings.byRule and
findings.bySeverity count the whole run; findings.shown is the capped list (--limit). Read
warnings and coverageGaps before trusting a short list: an empty findings list can mean a clean
tree or a blind run, and only those fields tell the two apart.
The exit code is 0 whatever was found. For CI, --fail-on <severity> exits 3 when a finding
reaches that severity, and --baseline <file> fails only on rules that find more than the recorded
baseline. zzop --help prints both, with every other knob.
Everything else
zzop --help is the canonical list of subcommands and flags, and zzop <subcommand> --help prints
one. In short:
zzop coverage <path>— how much of each tree zzop actually sees, per extension and per io channel.zzop file <path> <tree>— everything known about one file;--source-idpicks the tree when several declare the same path.zzop endpoint "<METHOD> <path>" <trees>— who provides and who consumes one key, and why they did or did not join.zzop map <path>/zzop graph <path>— the module map as data / a picture for an external renderer.zzop facts <path>— the uncapped post-assembly facts, for a rule program of your own.zzop manifest <a> <b>andzzop diff old.json new.json— commit a structural contract and compare a later run against it (--allow-tool-driftto compare across zzop builds).zzop validate-envelope,zzop validate-rule-pack— check what you inject before you inject it.zzop analyze-envelope <envelope.json>— analyze an envelope with no native parsing at all.zzop explain <rule-id>— one rule's data, its suppress marker and its off-switch.zzop contract [<name>]— the embedded authoring contracts (envelope schema, DSL reference, rule catalog, config surface, starter config, …).zzop version(orzzop --version;--verboseadds each parser's fingerprint).
From an AI agent. zzop-mcp answers the same questions through the same handlers, so a tool call
and a CLI run on the same path agree. The server exposes the tools analyze_repo, cross_repo,
check_file, check_endpoint, check_coverage, module_map, analyze_envelope, validate_envelope,
validate_rule_pack — plus zzop://contract/* resources carrying the same documents
zzop contract prints, so an adapter or rule pack can be written with nothing but the binary.
Embedding. The zzop-facade crate is the JSON-in/JSON-out contract under both binaries
(zzop_facade::analyze_json, analyze_trees_json, analyze_envelope_json). It is workspace-internal
and not on crates.io, so in-process use means vendoring this workspace; shelling out to
zzop … --json needs no linkage.
Where next
- Getting started — the guided path: two repos, an overlay, a rule pack.
- Adapters and Normalized AST — inject a parser or an overlay for a language or framework.
- Rule authoring, DSL reference and the rule catalog — write a rule pack, look up a rule.
- Architecture — how a tree becomes IR, graphs and a reply.
- Versioning — pre-1.0 (
0.x): pin an exact version. Which surfaces are stable and where breaks are recorded (CHANGELOG.md). - Contributing · Security · documentation site: https://eezz4.github.io/zzop/
License
MIT — see LICENSE.
zzop MCP questions
Does zzop make network requests?
No, zzop is designed to be deterministic and secure; it never makes network requests.
What programming languages are supported out of the box?
The built-in parsers support TypeScript/JavaScript, Python, Java, C#, Go, Rust, Prisma, and SQL schemas.
Can I use zzop with an AI agent?
Yes, the zzop-mcp server allows AI agents to use tools like analyze_repo, cross_repo, and check_endpoint via stdio.
How do I install it via npm?
You can install the native binary for your platform using the command npm i -g @zzop/cli.