cxpak

Spends CPU cycles so you don't spend tokens.

cxpak indexes your codebase using tree-sitter across 43 languages, builds a typed dependency graph, and produces token-budgeted context bundles that give LLMs a briefing packet instead of a flashlight in a dark room. It understands your code's architecture, conventions, risk profile, and data layer -- then packs exactly what the LLM needs, nothing more.

cxpak visualrenders a self-contained single-page dashboard -- three modes, inlined D3,zero external assets, works offline. Nineteen built-in colour palettes and a Cmd+K command palette over every file, symbol, and view. Every number on the page traces to a real computation; click any risk to see its exact derivation.

Overview -- a needle health dial and genome bars, ranked top risks, a proven Signals feed, and the Repo-DNA fingerprint barcode.

brew tap Barnett-Studios/tap && brew install cxpak # macOS/Linux cargo install cxpak # any platform, incl. Windows

Docker is a first-class deployment option — useful anywhere you want a reproducible, isolated install without managing a Rust toolchain: CI pipelines, sandboxed servers, Windows machines, or air-gapped environments.

Multi-arch (amd64/arm64) images are published to GitHub Container Registry on every release — no build, no Rust toolchain, no source checkout:

docker run --rm -v "$(pwd):/repo" ghcr.io/barnett-studios/cxpak overview .

Pin a tag or an immutable digest for reproducible deploys:

docker run --rm -v "$(pwd):/repo" ghcr.io/barnett-studios/cxpak:3.1.0 overview . docker run --rm -v "$(pwd):/repo" ghcr.io/barnett-studios/cxpak@sha256:<digest> overview .

cosign verify ghcr.io/barnett-studios/cxpak:3.1.0 \ --certificate-identity-regexp '^https://github.com/Barnett-Studios/cxpak/' \ --certificate-oidc-issuer https://token.actions.githubusercontent.com

Builds the full default feature set from your local checkout. First build is slow (candle ML deps); subsequent builds reuse a cached dependency layer.

# SHA-256 values are per-release — copy the two for VERSION from the releases page. docker build -f Dockerfile.standalone \ --build-arg VERSION=3.1.0 \ --build-arg SHA256_AMD64=<cxpak-x86_64-unknown-linux-gnu checksum> \ --build-arg SHA256_ARM64=<cxpak-aarch64-unknown-linux-gnu checksum> \ -t cxpak:3.1.0 .

The container runs as a non-root user; the embedding model weights (~30 MB, downloaded on first use) live under/home/cxpak/.cxpak— mount a named volume there to persist them across runs.

# One-shot command docker run --rm -v "$(pwd):/repo" ghcr.io/barnett-studios/cxpak overview . # HTTP server (--bind 0.0.0.0 required to reach the container from the host; # --token is mandatory when binding to a non-loopback address) docker run -d -p 3000:3000 \ -v "$(pwd):/repo" \ -v cxpak-models:/home/cxpak/.cxpak \ ghcr.io/barnett-studios/cxpak serve --bind 0.0.0.0 --token mysecret . # MCP — stdio only, one repo per instance (see note below) docker run --rm -i -v "$(pwd):/repo" ghcr.io/barnett-studios/cxpak serve --mcp .

# One-shot command docker run --rm -v ${PWD}:/repo ghcr.io/barnett-studios/cxpak overview . # HTTP server docker run -d -p 3000:3000  -v ${PWD}:/repo  -v cxpak-models:/home/cxpak/.cxpak  ghcr.io/barnett-studios/cxpak serve --bind 0.0.0.0 --token mysecret . # Verify (use curl.exe — PowerShell's curl alias does not work here) curl.exe http://localhost:3000/health # MCP — stdio only, one repo per instance (see note below) docker run --rm -i -v ${PWD}:/repo ghcr.io/barnett-studios/cxpak serve --mcp .

Replacemysecretwith any non-empty secret of your choice./healthis open (GET) as a liveness probe; every other endpoint requires the bearer token when one is set (with no--token, on a loopback bind, all routes are open):

curl http://localhost:3000/health # no auth required curl -X POST -H "Authorization: Bearer mysecret" http://localhost:3000/v1/conventions

MCP scope:Each MCP instance indexes exactly one repository — the path passed at startup (.in the examples above, which maps to the mounted/repo). To serve multiple repos simultaneously, run one container per repo and register each in your MCP client config. The HTTP server has the same single-repo scope.

# See your codebase the way an LLM should cxpak overview . # Trace a symbol through the dependency graph cxpak trace "handle_request" . # Generate an interactive dashboard cxpak visual --visual-type dashboard . # Get a guided reading order for onboarding cxpak onboard .

On large repositories,cxpak serve --mcpanswers the MCPinitializehandshake immediately and builds the index in the background -- fixing the startup timeout. Tool calls that arrive before the index is ready get a graceful retry status, then byte-identical results once it is built.

Auto-triggers on architecture questions and change reviews. Slash commands:/cxpak:overview,/cxpak:trace,/cxpak:diff,/cxpak:clean.

cxpak serve . # port 3000 cxpak serve --token my-secret . # with Bearer auth on /v1/ endpoints cxpak watch . # file watcher with hot index

cxpak lsp . # stdio, works with any LSP client

CodeLens, hover, diagnostics, workspace symbols, plus 16 customcxpak/methods. SupportsdidOpen/didChange/didClosefor in-editor reactivity.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

next-devtools-mcp is a MCP server that provides Next.js development tools and utilities for AI coding assistants like Claude and Cursor.

Word search, crossword, and sudoku generator MCP server with printable PDF worksheets, themed word banks, and verifiable LLM evals. Local-first, from the makers of puzzletide.com.

A demonstration server for ActionKit, providing access to Slack actions via Claude Desktop.