AI Architect Codebase MCP server

<!-- mcp-name: io.github.cdeust/ai-architect-mcp-codebase -->

Stop your coding agent from guessing at your codebase. It answers who calls this, what breaks if I change it, and how does execution get here from a real graph of your code — not from grepping and hoping. Runs entirely on your machine. Read-only: it never writes code, opens PRs, or runs CI.

What An Agent Can Ask · Getting Started · Pipeline · Tools · Architecture · Zetetic Standard

One of three MCP servers that each run standalone and keep evolving — memory, code graph (this), spec verification — plus visualization and reasoning-agent companions. How they fit together ↓

Every AI coding assistant hits the same wall: you ask it to change handletoolcall, and it either hallucinates a function that was renamed last week, edits something in the wrong community of the codebase, or silently breaks a call chain three modules away. Agents operate on strings; codebases have structure. The gap is where bugs live.

This server gives it the structure. It parses your repository into a real graph of symbols and their relationships, then answers structural questions directly — with source links, and with its own limitations stated alongside the answer.

What you get

• Real answers about your code. Who calls this function, what breaks if I change it, how does execution reach here, what belongs together — resolved across files, not guessed from text matches.
• Your agent stops re-reading files. One graph query replaces the open-five-files-and-scroll loop. On our offline evaluation that is 14.26× fewer payload tokens and 5.20× fewer tool calls than a Grep/Glob/Read baseline (protocol, caveats and what it does not prove ↓).
• 11 languages. Rust, Python, TypeScript, Java, Kotlin, Swift, Objective-C, C, C++, Go get full extraction; Ruby gets a shallow pass (node kinds, no deep extraction).
• Read-only by design. It supplies evidence for the next stage — a fix, a PRD, a review. It never edits your code.
• It says what it cannot see. Every answer carries its analysis limitations, so you can tell a real "no callers" from an unresolved import.

Sovereign intelligence, eco-responsible by intent

Sovereign is what it is today. Native Rust and tree-sitter parse your code on your machine — no model is called to read it, and nothing is uploaded. The graph is a local database file you own.

Shortened. The full README is on GitHub.