Qartez Mcp

by kuberstar

63 544 downloads Not rated yet

About

Code intelligence MCP server - PageRank, blast radius, co-change, hotspots, clone detection across 34 languages in a single Rust binary.

Explore

- Pre-computed knowledge graph of the entire codebase
- 43 MCP tools for querying symbols, impact, and structure
- Supports 37 programming languages
- Reduces AI token consumption by ~94% vs. grep-based approaches
- Includes modification guard hooks for Claude Code
- Works with 19 editors and agents out of the box
- Platform support: macOS 13+, Ubuntu 22.04+, Windows, WSL2 (x86_64 and arm64)

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name Qartez Mcp
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository

Platform support: macOS 13+, Ubuntu 22.04+ (and other modern Linux, gnu or musl), Windows (native PowerShell 5.1+/7+) and WSL 2. Architectures: x86_64 and arm64. Rust MSRV is 1.88 - only needed for unsupported platforms or the --from-source escape hatch.

Pick the one-liner for your operating system. Both commands do the same thing: download a pre-built binary, verify its SHA-256 against the release's SHA256SUMS, install the three binaries (qartez, qartez-guard, qartez-setup), and launch qartez-setup in non-interactive mode to configure every MCP-capable IDE it detects (including the modification-guard hooks for Claude Code).

macOS / Linux / WSL 2 - bash installer, binaries land in ~/.local/bin/:

curl -sSfL https://qartez.dev/install | sh

Windows (native PowerShell 5.1+/7+) - PowerShell installer, binaries land in %LOCALAPPDATA%\Programs\qartez\:

powershell -ExecutionPolicy Bypass -c "iwr https://raw.githubusercontent.com/kuberstar/qartez-mcp/main/install.ps1 -useb | iex"

Unsupported platforms (e.g. linux-musl arm64 without a published artifact) fall back to a local cargo build automatically; pass --from-source (bash) or -FromSource (PowerShell) to force that path. Rust MSRV 1.88 is only required for that fallback.

Open any project in your IDE - Qartez indexes it automatically on session start. No manual step needed. The file watcher keeps the index fresh as you edit.

<details>
<summary>Alternative: install from source (all platforms)</summary>

git clone https://github.com/kuberstar/qartez-mcp.git
cd qartez-mcp
make deploy

Want to inspect the install script before piping it into sh? Read it on GitHub: install.sh (bash) or install.ps1 (PowerShell).
</details>

<details>
<summary>Interactive install, targeted install, and other options</summary>

qartez-setup --ide cursor,zed,claude

Configure a specific subset of IDEs only. Detected paths:

| IDE | Config path |
|---|---|
| Claude Code | ~/.claude/settings.json |
| Claude Desktop | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Gemini | ~/.gemini/settings.json |
| Cursor | ~/.cursor/mcp.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| Kiro | ~/.kiro/settings/mcp.json |
| Zed | ~/.config/zed/settings.json |
| Continue.dev | ~/.continue/config.yaml |
| Copilot CLI | ~/.copilot/mcp-config.json |
| Amazon Q | ~/.aws/amazonq/mcp.json |
| Amp | ~/.config/amp/settings.json |
| Cline | VS Code global storage saoudrizwan.claude-dev/settings/cline_mcp_settings.json |
| Roo Code | VS Code global storage rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json |
| Goose | ~/.config/goose/config.yaml |
| Warp | ~/.warp/mcp_settings.json |
| Augment | ~/.augment/settings.json |
| OpenCode | ~/.config/opencode/opencode.json (or opencode.jsonc) |
| Codex CLI | ~/.codex/config.toml |
| Antigravity | ~/.gemini/antigravity/mcp_config.json |

Every install path is idempotent and backs up the existing config.

make uninstall

Removes Qartez from every configured IDE and deletes the binaries.

</details>

---

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_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` + `qartez_cochange`.

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_clones

Structural code-clone detection via AST shape hashing (identifiers, literals, and comments are normalized away). Finds duplicate logic the human reviewer would never spot.

qartez_boundaries

Architecture-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_hierarchy

Type 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_trend

Complexity trend over git history: tracks how a function's cyclomatic complexity evolved commit by commit. Flags functions that are GROWING, STABLE, or SHRINKING.

qartez_security

Security 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 category.

qartez_smells

Code 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 technique.

qartez_refactor_plan

Ordered, safety-annotated refactor plan for one file. Each step names a technique (Extract Method, Introduce Parameter Object), an estimated CC impact category (High/Medium/Low) with a range, and safety signals from impact, test coverage, and caller count.

qartez_test_gaps

Test coverage gap analysis via the import graph. Three modes: `gaps` ranks untested source files by risk, `map` shows test-to-source mappings, `suggest` recommends tests to run for a git diff range.

qartez_knowledge

**Bus-factor analysis.** Git-blame-based authorship at file and module level. Surfaces single-author files and modules where knowledge is concentrated in one contributor.

qartez_blame

**Symbol-scoped git blame.** Resolves a function/type name to its line range and blames only those lines: per-hunk commits/authors, or a per-author rollup with each author's latest commit.

qartez_semantic

Semantic search using a local embedding model. Natural-language queries ranked by hybrid FTS5 + vector similarity (RRF). Requires the `semantic` cargo feature and a one-time model download (~270 MB).

qartez_path

Shortest call/reference path between two symbols. Forward BFS over the symbol-reference graph returns the ordered symbol/file chain plus a count of alternative shortest paths. Filter edges by `kind` (`call` or `type`).

qartez_rename

Rename a symbol across the entire codebase. Definition, imports, all usages. Preview by default, `apply=true` to execute.

qartez_move

Move a symbol to another file and rewrite all import paths. One MCP call.

qartez_rename_file

Rename a file and update every import pointing to it.

qartez_replace_symbol

Replace a symbol's whole line range with new source. Caller provides the full replacement including the signature; preview by default, `apply=true` executes atomically.

qartez_insert_before_symbol

Splice new code immediately before an anchor symbol. Anchor lookup goes through the indexed symbol table - no need for the exact surrounding context.

qartez_insert_after_symbol

Splice new code immediately after an anchor symbol. Same anchor-based addressing as `qartez_insert_before_symbol`.

qartez_safe_delete

Delete a symbol after reporting every file that still imports it. Refuses to apply when importers exist unless `force=true`.

qartez_project

Auto-detects your toolchain (Cargo, npm/bun/yarn, Go, Python, Make, Gradle) and runs test/build/lint/typecheck through a single tool.

qartez_wiki

Generates a markdown architecture wiki using Leiden community detection on the import graph. Partitions files into clusters, names each one, and emits `ARCHITECTURE.md` with inter-cluster edges.

qartez_workspace

Add or remove workspace domains at runtime. Registers external directories under a custom alias in `.qartez/workspace.toml`, indexes them, and purges them on removal.

qartez_add_root

Register an additional project root at runtime. Indexes the directory, refreshes pagerank/co-change, and hot-attaches a file watcher; the alias is optional (derived from the path basename) and persistence is toggleable for ephemeral roots.

qartez_list_roots

List every project root currently tracked by the server with its alias, source (cli/config/runtime), watcher attachment state, file count, and last index timestamp.

qartez_maintenance

Inspect and compact `.qartez/index.db`. Default action `stats` reports DB / WAL sizes, top tables, current workspace fingerprint, and last full-reindex timestamp. Other actions: `checkpoint`, `optimize_fts` (merge FTS5 segments), `vacuum_incremental`, `vacuum`, `convert_incremental` (one-shot conversion to `auto_vacuum=INCREMENTAL`), `purge_stale` (drop rows for roots no longer in the workspace). Use this on a bloated DB instead of deleting `.qartez/index.db` by hand.

qartez_find

52

qartez_impact

352

qartez_outline

3,009

qartez_deps

166

qartez_map

87

qartez_grep

127

qartez_stats

155

qartez_read

150

Think of these as the standard library for AI code understanding. Each one replaces a multi-step human workflow with a single, token-efficient call the agent can reason about.

Tools are organized into tiers with progressive disclosure. Core tools are always available. Additional tiers can be unlocked on demand via qartez_tools enable: ["analysis"] (or "all").

| Tool | What it does |
|---|---|
| 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_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 + qartez_cochange. |
| 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_clones | Structural code-clone detection via AST shape hashing (identifiers, literals, and comments are normalized away). Finds duplicate logic the human reviewer would never spot. |
| qartez_boundaries | Architecture-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_hierarchy | Type 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_trend | Complexity trend over git history: tracks how a function's cyclomatic complexity evolved commit by commit. Flags functions that are GROWING, STABLE, or SHRINKING. |
| qartez_security | Security 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 category. |
| qartez_smells | Code 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 technique. |
| qartez_refactor_plan | Ordered, safety-annotated refactor plan for one file. Each step names a technique (Extract Method, Introduce Parameter Object), an estimated CC impact category (High/Medium/Low) with a range, and safety signals from impact, test coverage, and caller count. |
| qartez_test_gaps | Test coverage gap analysis via the import graph. Three modes: gaps ranks untested source files by risk, map shows test-to-source mappings, suggest recommends tests to run for a git diff range. |
| qartez_knowledge | Bus-factor analysis. Git-blame-based authorship at file and module level. Surfaces single-author files and modules where knowledge is concentrated in one contributor. |
| qartez_blame | Symbol-scoped git blame. Resolves a function/type name to its line range and blames only those lines: per-hunk commits/authors, or a per-author rollup with each author's latest commit. |
| qartez_semantic | Semantic search using a local embedding model. Natural-language queries ranked by hybrid FTS5 + vector similarity (RRF). Requires the semantic cargo feature and a one-time model download (~270 MB). |
| qartez_path | Shortest call/reference path between two symbols. Forward BFS over the symbol-reference graph returns the ordered symbol/file chain plus a count of alternative shortest paths. Filter edges by kind (call or type). |

| Tool | What it does |
|---|---|
| qartez_rename | Rename a symbol across the entire codebase. Definition, imports, all usages. Preview by default, apply=true to execute. |
| qartez_move | Move a symbol to another file and rewrite all import paths. One MCP call. |
| qartez_rename_file | Rename a file and update every import pointing to it. |
| qartez_replace_symbol | Replace a symbol's whole line range with new source. Caller provides the full replacement including the signature; preview by default, apply=true executes atomically. |
| qartez_insert_before_symbol | Splice new code immediately before an anchor symbol. Anchor lookup goes through the indexed symbol table - no need for the exact surrounding context. |
| qartez_insert_after_symbol | Splice new code immediately after an anchor symbol. Same anchor-based addressing as qartez_insert_before_symbol. |
| qartez_safe_delete | Delete a symbol after reporting every file that still imports it. Refuses to apply when importers exist unless force=true. |

| Tool | What it does |
|---|---|
| qartez_project | Auto-detects your toolchain (Cargo, npm/bun/yarn, Go, Python, Make, Gradle) and runs test/build/lint/typecheck through a single tool. |
| qartez_wiki | Generates a markdown architecture wiki using Leiden community detection on the import graph. Partitions files into clusters, names each one, and emits ARCHITECTURE.md with inter-cluster edges. |
| qartez_workspace | Add or remove workspace domains at runtime. Registers external directories under a custom alias in .qartez/workspace.toml, indexes them, and purges them on removal. |
| qartez_add_root | Register an additional project root at runtime. Indexes the directory, refreshes pagerank/co-change, and hot-attaches a file watcher; the alias is optional (derived from the path basename) and persistence is toggleable for ephemeral roots. |
| qartez_list_roots | List every project root currently tracked by the server with its alias, source (cli/config/runtime), watcher attachment state, file count, and last index timestamp. |
| qartez_maintenance | Inspect and compact .qartez/index.db. Default action stats reports DB / WAL sizes, top tables, current workspace fingerprint, and last full-reindex timestamp. Other actions: checkpoint, optimize_fts (merge FTS5 segments), vacuum_incremental, vacuum, convert_incremental (one-shot conversion to auto_vacuum=INCREMENTAL), purge_stale (drop rows for roots no longer in the workspace). Use this on a bloated DB instead of deleting .qartez/index.db by hand. |

18 tools with complete non-MCP simulations (fair token-to-token comparison):

| Tool | MCP tokens | Without MCP | Savings | Speedup |
|---|---:|---:|---:|---:|
| qartez_cochange | 92 | 14,622 | +99.4% | 2x |
| qartez_context | 107 | 4,489 | +97.6% | 533x |
| qartez_find | 52 | 1,490 | +96.5% | 210x |
| qartez_impact | 352 | 9,243 | +96.2% | 140x |
| qartez_outline | 3,009 | 77,843 | +96.1% | 5x |
| qartez_project | 68 | 1,394 | +95.1% | 0x |
| qartez_unused | 468 | 6,750 | +93.1% | 22x |
| qartez_deps | 166 | 2,286 | +92.7% | 118x |
| qartez_map | 87 | 674 | +87.1% | 1x |
| qartez_rename_file | 27 | 185 | +85.4% | 211x |
| qartez_grep | 127 | 763 | +83.4% | 72x |
| qartez_stats | 155 | 848 | +81.7% | 1x |
| qartez_move | 161 | 701 | +77.0% | 159x |
| qartez_calls | 564 | 2,409 | +76.6% | 3x |
| qartez_refs | 201 | 692 | +71.0% | 26x |
| qartez_read | 150 | 495 | +69.7% | 100x |
| qartez_hierarchy | 735 | 2,056 | +64.3% | 127x |
| qartez_rename | 439 | 648 | +32.3% | 11x |

10 additional analytical tools have no meaningful grep/read equivalent - they solve problems the non-MCP stack cannot solve at all:

qartez_hotspots, qartez_clones, qartez_smells, qartez_test_gaps, qartez_wiki, qartez_boundaries, qartez_trend, qartez_knowledge, qartez_diff_impact, qartez_security.

<details>
<summary>Multi-language bench</summary>

make bench-all runs the same 28-scenario harness against five pinned OSS fixtures - colinhacks/zod (TypeScript), spf13/cobra (Go), encode/httpx (Python), FasterXML/jackson-core (Java), plus the Qartez self-bench (Rust) - then emits a cross-language summary to reports/benchmark-<lang>.md plus a combined matrix. Every tool, every language, every scenario - measured with the cl100k_base tokenizer against a faithful Glob + Grep + Read + git log simulation.

make bench          # Rust self-bench only - fresh measurements
make bench-all      # All 5 languages (Rust, TypeScript, Python, Go, Java) + cross-language summary
make bench-fixtures # Clone and index the pinned fixture repos

Reports land in reports/benchmark.md / reports/benchmark.json for the single-language run, or reports/benchmark-<lang>.md plus a combined cross-language summary for bench-all.

</details>

---

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "qartez mcp": {
            "qartez": {
                "command": "qartez-mcp",
                "args": []
            }
        }
    }
}

McpServers

{
    "qartez": {
        "command": "qartez-mcp",
        "args": []
    }
}

<p align="center">
Qartez
<h1 align="center">Qartez MCP</h1>
<p align="center">
<strong>X-ray vision for your codebase - built for AI agents, not humans.</strong>
</p>
<p align="center">
The first code-intelligence server designed from day one to be<br>
<em>consumed by language models</em>, not read by people. Cuts AI token usage by ~94%.
</p>
<p align="center">
<a href="#quickstart">Quickstart</a> ·
<a href="#the-43-tools">43 Tools</a> ·
<a href="#modification-guard">Guard</a> ·
<a href="#benchmarks">Benchmarks</a> ·
<a href="#comparison-with-alternatives">Comparison</a> ·
<a href="#supported-languages">37 Languages</a> ·
<a href="#command-line-options">CLI</a> ·
<a href="#contributing">Contributing</a> ·
<a href="#security">Security</a> ·
<a href="CHANGELOG.md">Changelog</a>
</p>
<p align="center">
<a href="LICENSE">License</a>
MSRV 1.88
37 languages
43 MCP tools
</p>
</p>

---

Why this exists

grep, find, cat, and ls were invented in the 1970s for humans reading one file at a time in a terminal. Half a century later, your AI assistant is still using them - scanning files byte by byte, re-reading the same directories on every question, guessing at what matters, and burning your tokens on work the tools were never designed to do.

Qartez is a different species of tooling. It is not a wrapper around grep. It is a pre-computed knowledge graph of your repository - symbols, imports, call edges, blast radii, PageRank, git co-change, cyclomatic complexity - served to any LLM through the Model Context Protocol. The agent stops reading your codebase and starts querying it.

> Think of it as the first purpose-built sensory organ for coding agents. Grep sees one line at a time. Qartez sees the entire shape of the codebase in one glance.

Every time your AI assistant touches code, three expensive things happen:

1. It reads the same files over and over. No memory of the repo. Every question starts from scratch. You pay for every token - again and again.

2. It can't see what will break. Your assistant edits utils.ts without knowing 14 other files import it. You find out in CI. Or in production.

3. It wastes tokens finding things. "Where is handleRequest defined?" turns into Grep across 200 files, Read on 5 candidates, and 1,600 tokens burned before it finds the answer. Qartez answers that in 50 tokens.

The fix isn't a smarter model. It's a smarter index.

---

Quickstart

Platform support: macOS 13+, Ubuntu 22.04+ (and other modern Linux, gnu or musl), Windows (native PowerShell 5.1+/7+) and WSL 2. Architectures: x86_64 and arm64. Rust MSRV is 1.88 - only needed for unsupported platforms or the --from-source escape hatch.

Install (recommended)

Pick the one-liner for your operating system. Both commands do the same thing: download a pre-built binary, verify its SHA-256 against the release's SHA256SUMS, install the three binaries (qartez, qartez-guard, qartez-setup), and launch qartez-setup in non-interactive mode to configure every MCP-capable IDE it detects (including the modification-guard hooks for Claude Code).

macOS / Linux / WSL 2 - bash installer, binaries land in ~/.local/bin/:

curl -sSfL https://qartez.dev/install | sh

Windows (native PowerShell 5.1+/7+) - PowerShell installer, binaries land in %LOCALAPPDATA%\Programs\qartez\:

powershell -ExecutionPolicy Bypass -c "iwr https://raw.githubusercontent.com/kuberstar/qartez-mcp/main/install.ps1 -useb | iex"

Unsupported platforms (e.g. linux-musl arm64 without a published artifact) fall back to a local cargo build automatically; pass --from-source (bash) or -FromSource (PowerShell) to force that path. Rust MSRV 1.88 is only required for that fallback.

Open any project in your IDE - Qartez indexes it automatically on session start. No manual step needed. The file watcher keeps the index fresh as you edit.

<details>
<summary>Alternative: install from source (all platforms)</summary>

git clone https://github.com/kuberstar/qartez-mcp.git
cd qartez-mcp
make deploy

Want to inspect the install script before piping it into sh? Read it on GitHub: install.sh (bash) or install.ps1 (PowerShell).
</details>

<details>
<summary>Interactive install, targeted install, and other options</summary>

Works with 19 editors and agents

A single Rust binary (qartez-setup) detects and configures every supported editor. No per-editor shell scripts, no copy-paste JSON.

make deploy                          # Configure every detected IDE (non-interactive)
make setup                           # Same, but interactive checkbox prompt
qartez-setup --ide cursor,zed       # Configure specific IDEs only
make uninstall                       # Remove qartez from every IDE and delete binaries

Supported out of the box: Claude Code, Claude Desktop, Gemini, Cursor, Windsurf, Kiro, Zed, Continue.dev, Copilot CLI, Amazon Q, Amp, Cline, Roo Code, Goose, Warp, Augment, OpenCode, Codex CLI, Antigravity.

Targeted install

qartez-setup --ide cursor,zed,claude

Configure a specific subset of IDEs only. Detected paths:

| IDE | Config path |
|---|---|
| Claude Code | ~/.claude/settings.json |
| Claude Desktop | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Gemini | ~/.gemini/settings.json |
| Cursor | ~/.cursor/mcp.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| Kiro | ~/.kiro/settings/mcp.json |
| Zed | ~/.config/zed/settings.json |
| Continue.dev | ~/.continue/config.yaml |
| Copilot CLI | ~/.copilot/mcp-config.json |
| Amazon Q | ~/.aws/amazonq/mcp.json |
| Amp | ~/.config/amp/settings.json |
| Cline | VS Code global storage saoudrizwan.claude-dev/settings/cline_mcp_settings.json |
| Roo Code | VS Code global storage rooveterinaryinc.roo-cline/settings/cline_mcp_settings.json |
| Goose | ~/.config/goose/config.yaml |
| Warp | ~/.warp/mcp_settings.json |
| Augment | ~/.augment/settings.json |
| OpenCode | ~/.config/opencode/opencode.json (or opencode.jsonc) |
| Codex CLI | ~/.codex/config.toml |
| Antigravity | ~/.gemini/antigravity/mcp_config.json |

Every install path is idempotent and backs up the existing config.

Enable Qartez in a project

Qartez indexes automatically on session start. For manual re-indexing:

qartez --root /path/to/your/project --reindex

Claude Desktop (manual)

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

Uninstall

make uninstall

Removes Qartez from every configured IDE and deletes the binaries.

</details>

---

What Qartez does

Qartez builds a knowledge graph of your codebase - once - and serves it to any AI assistant through MCP. Instead of scanning files from scratch on every question, your assistant queries a pre-computed index that knows:

…

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.