cxpak_contextLABSCO SUMMARY
Five tools with an op argument, where there used to be 26.
The consolidation in 3.0.0 affects MCP clients only — the CLI, the HTTP API and the LSP methods are unchanged, and the 26 old names still answer as deprecated aliases for one release. cxpak_context is the entry point: give it a task and a token budget and it returns ranked, annotated files with per-file notes on why each one was included.
What it is
A Rust context engine that indexes a repository with tree-sitter across 43 languages, builds a typed dependency graph, and produces token-budgeted context bundles for an LLM.
What you get
- cxpak_context — context, retrieval, search, overview, stats and briefing, selected with an op argument
- cxpak_graph — graph queries plus trace, blast_radius, call_graph, dead_code, api_surface, data_flow and change prediction
- cxpak_review — review, diff and verify
- cxpak_insight — health, risks, architecture, conventions, security_surface, drift, visual and onboard
- cxpak_data — indexed or live schema
- Every context response opens with a repository conventions summary, so the model sees how your team writes code first
- An offline single-page dashboard rendered by cxpak visual, with no external assets
Requirements
brew install cxpak or cargo install cxpak; multi-arch images are published at ghcr.io/barnett-studios/cxpak. Register it in .mcp.json as cxpak serve --mcp . — indexing runs against the repository path you pass.
Setup effort
One command — cargo install cxpak
USE CASES
01
Giving an assistant the right files for a task
One call with a task and a budget, instead of five rounds of glob and grep.
02
Finding out what a change would break
Trace the symbol and read the blast radius off the dependency graph.
03
Reviewing a diff with the graph in hand
Review the change against what it actually touches, not just the lines in the patch.
04
Getting oriented in an unfamiliar repository
Ask for health, architecture and conventions before writing anything.
5 tools
Listed in project docs. Your client may show a different list.
cxpak_graphcxpak_datacxpak_reviewcxpak_insightBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
cxpak on PATH
INSTALLATION
Connect your client
Server setup
TERMINAL
cargo install cxpakMCP Clients
Claude Code, Cursor
JSON
{
"mcpServers": {
"cxpak": {
"command": "cxpak",
"args": [
"serve",
"--mcp",
"."
]
}
}
}Claude Code — plugin
CLAUDE CODE — PLUGIN · IN CLIENT
/plugin install cxpakAny MCP client — Docker
ANY MCP CLIENT — DOCKER · TERMINAL
docker run --rm -i -v "$(pwd):/repo" ghcr.io/barnett-studios/cxpak serve --mcp .
