qartez_add_rootLABSCO SUMMARY
Asks the questions grep cannot: what breaks, who owns it, what is dangerous to touch.
Lookup is the easy half. The part that earns the index is the derived signals - blast radius, co-change partners, bus factor, complexity trend - because those are the questions a reviewer asks and no text search can answer. The refactor tools preview by default, which is the right way round for something that rewrites files.
What it is
A code-intelligence server for agents rather than humans. It indexes the repository once and answers structural questions from the index: what a symbol is, who calls it, what breaks if it changes, and which files are risky.
What you get
- A core set of eight tools for daily use: a ranked project map, symbol lookup, indexed search, targeted source reads, file outlines, blast radius, dependency graphs and codebase metrics
- Eighteen analysis tools including references, call hierarchies, git co-change, dead exports, code clones, smells, security findings, authorship and bus factor, and shortest path between two symbols
- A prioritised health list that crosses hotspots with smells, plus an ordered refactor plan naming a technique per step with its expected complexity impact
- Seven refactor tools - rename, move, rename a file, replace a symbol, insert before or after one, and a safe delete that reports importers first - all in preview mode until you pass apply
- Meta tools for the build toolchain, an auto-generated architecture document, and adding project roots or workspace domains at runtime
- A discovery tool that lists the tiers and unlocks them on demand, for keeping the visible tool list small
Requirements
A one-line installer for macOS, Linux, WSL or Windows PowerShell; it verifies the download against the release checksums, installs the binaries, and configures the MCP-capable editors it finds. Indexing happens automatically when you open a project and a file watcher keeps it fresh. Rust 1.88 is needed only for the from-source fallback on unsupported platforms. Semantic search is optional and needs a downloaded model. Progressive mode hides all but the core tier at startup.
Setup effort
One command — curl -sSfL https://qartez.dev/install | sh
USE CASES
Deciding whether a file is safe to change
Read its blast radius - direct importers, transitive dependents, co-change partners and test coverage - before editing anything.
Working out where to start in a new repository
Pull the importance-ranked project map, then the codebase metrics, then outline the files that keep coming up.
Finding the code that most needs attention
Read the health list, which crosses hotspots with smells, then ask for an ordered refactor plan for the worst file.
Renaming something used all over the codebase
Preview the rename first, read what it would touch, and only then apply it.
Deleting code nobody calls
List the dead exports, then use the safe delete, which refuses while importers remain rather than leaving dangling imports.
Finding out who to ask about a function
Blame the symbol's own line range rather than the whole file, and check the module's bus factor.
42 tools
Listed in project docs. Your client may show a different list.
qartez_blameqartez_boundariesqartez_callsqartez_clonesqartez_cochangeqartez_contextqartez_depsqartez_diff_impactqartez_findqartez_grepqartez_healthqartez_hierarchyqartez_hotspotsqartez_impactqartez_insert_after_symbolqartez_insert_before_symbolqartez_knowledgeqartez_list_rootsqartez_maintenanceqartez_mapqartez_moveqartez_outlineqartez_pathqartez_projectqartez_readqartez_refactor_planqartez_refsqartez_renameqartez_rename_fileqartez_replace_symbolqartez_safe_deleteqartez_securityqartez_semanticqartez_smellsqartez_statsqartez_test_gapsqartez_toolsqartez_trendqartez_unusedqartez_wikiqartez_workspaceBEFORE YOU INSTALL
What to know first
Tools you get
42 tools named in the project's documentation. All tools are available by default; QARTEZ_PROGRESSIVE=1 shows only the core tier and qartez_tools at startup.
INSTALLATION
Connect your client
Server setup
macOS / Linux / WSL 2: curl -sSfL https://qartez.dev/install | sh (binaries land in ~/.local/bin/)
Windows (native PowerShell 5.1+/7+): powershell -ExecutionPolicy Bypass -c "iwr https://raw.githubusercontent.com/kuberstar/qartez-mcp/main/install.ps1 -useb | iex" (binaries land in %LOCALAPPDATA%\Programs\qartez\)
The installer downloads the prebuilt binary, verifies its SHA-256 against the release SHA256SUMS, installs qartez / qartez-guard / qartez-setup, and runs qartez-setup non-interactively to configure every MCP-capable IDE it detects
From source instead: git clone https://github.com/kuberstar/qartez-mcp.git ; cd qartez-mcp ; make deploy
Optional: qartez-setup --ide cursor,zed,claude to configure only specific IDEs; make setup for the interactive picker
Then just open a project — Qartez indexes on session start; manual re-index is qartez --root <YOUR_ROOT> --reindex
MCP Clients
Claude Code
{
"mcpServers": {
"qartez": {
"command": "qartez",
"args": []
}
}
}Claude Desktop
{
"mcpServers": {
"qartez": {
"command": "<YOUR_PATH_TO_QARTEZ>",
"args": []
}
}
}Cursor, Zed
qartez-setup --ide cursor,zed