Qartez MCP Server

<strong>X-ray vision for your codebase - built for AI agents, not humans.</strong>

Local serverstdioPython

What is the Qartez MCP MCP server?

X-ray vision for your codebase - built for AI agents, not humans.. The qartez mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Its toolset

Everything the assistant can do here goes through one of these:

  • qartez_refs — Trace every usage of a symbol across the codebase, with optional transitive chains
  • qartez_calls — Call hierarchy: who calls this function, and what does it call
  • qartez_cochange — Files that historically change together in git. Logical coupling invisible to the import graph
  • qartez_context — Smart context builder: given files you plan to modify, returns the optimal set of related files to read first
  • qartez_unused — Dead-code finder: exported symbols with zero importers, pre-materialized at index time
  • qartez_diff_impactBatch impact for a git diff range. Pass a revspec like main..HEAD to get changed files with PageRank, union blast radius, convergence points, and
  • qartez_hotspotsThe refactor radar. Ranks files and functions by hotspot score = cyclomatic complexity x PageRank x (1 + churn). Points straight at the
  • qartez_clones — Structural code-clone detection via AST shape hashing (identifiers, literals, and comments are normalized away). Finds duplicate logic the human
  • qartez_boundaries — Architecture-boundary enforcement. Declare "these modules may not import those" in .qartez/boundaries.toml and get every violating edge back
  • qartez_hierarchy — Type hierarchy queries: find all types implementing a trait/interface, or all traits/interfaces a type implements. Works across Rust, TypeScript
  • qartez_trend — Complexity trend over git history: tracks how a function's cyclomatic complexity evolved commit by commit. Flags functions that are GROWING, STABLE
  • qartez_security — Security scanner with 13 built-in rules. Regex-based pattern matching scored by PageRank to prioritize high-impact files. Custom rules via

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Qartez MCP.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the qartez mcp mcp server does with a few real requests.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Qartez MCP's toolset — qartez_refs, qartez_calls, qartez_cochange and 11 more — is a fair guide to whether it matches your workflow. It is maintained by kuberstar; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
qartez_refsTrace every usage of a symbol across the codebase, with optional transitive chains.
qartez_callsCall hierarchy: who calls this function, and what does it call.
qartez_cochangeFiles that historically change together in git. Logical coupling invisible to the import graph.
qartez_contextSmart context builder: given files you plan to modify, returns the optimal set of related files to read first.
qartez_unusedDead-code finder: exported symbols with zero importers, pre-materialized at index time.
qartez_diff_impact**Batch impact for a git diff range.** Pass a revspec like main..HEAD to get changed files with PageRank, union blast radius, convergence points, and co-change omissions. One call replaces N calls to qartez_impact + qart
qartez_hotspots**The refactor radar.** Ranks files and functions by hotspot score = **cyclomatic complexity x PageRank x (1 + churn)**. Points straight at the highest-risk code in the repo.
qartez_clonesStructural code-clone detection via AST shape hashing (identifiers, literals, and comments are normalized away). Finds duplicate logic the human reviewer would never spot.
qartez_boundariesArchitecture-boundary enforcement. Declare "these modules may not import those" in .qartez/boundaries.toml and get every violating edge back. suggest=true seeds a starter config from the Leiden clustering.
qartez_hierarchyType hierarchy queries: find all types implementing a trait/interface, or all traits/interfaces a type implements. Works across Rust, TypeScript, Java, Python, and Go.
qartez_trendComplexity trend over git history: tracks how a function's cyclomatic complexity evolved commit by commit. Flags functions that are GROWING, STABLE, or SHRINKING.
qartez_securitySecurity scanner with 13 built-in rules. Regex-based pattern matching scored by PageRank to prioritize high-impact files. Custom rules via .qartez/security.toml. Filters by severity (low/medium/high/critical) and categor
qartez_smellsCode smell detector: finds **god functions** (high complexity + long body), **long parameter lists**, and **feature envy** (methods that use another type more than their own). Tuneable thresholds.
qartez_health**Prioritized fix list.** Cross-references qartez_hotspots with qartez_smells and buckets files as Critical (hotspot + smell), High (hotspot only), or Medium (smell only). Each entry carries a concrete suggested refactor

How to install the Qartez MCP MCP server

### Claude Desktop (manual)

```json
{
  "mcpServers": {
    "qartez": {
      "command": "/absolute/path/to/qartez",
      "args": []
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Qartez MCP to qartez refs.
  • Use Qartez MCP to qartez calls.
  • Use Qartez MCP to qartez cochange.

Frequently asked questions

It connects Qartez MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (qartez_refs, qartez_calls, qartez_cochange, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Qartez MCP directly.