The CodeXX MCP Server connects your AI coding agent to the CodeXX C++ engine over the Model Context Protocol. Instead of pasting files into the model and hoping it infers structure, the agent asks: find this symbol, who calls it, what does it reference, what does this type look like in memory, show me exactly these lines.

It speaks the same protocol your agent already knows. You point it at a C++ project, connect it to your client, and the model gains a precise, queryable view of the code.

What it gives your agent

Find symbols, not strings

Resolve a name to the real declaration — function, class, struct, namespace, enum — with its kind, signature, and file:line. Or enumerate every symbol of a kind, or in a file, to map an unfamiliar codebase.

Follow the real relationships

Who calls this function? What does it reference, and from where? The server answers from the engine’s analysis of your actual source, so the agent reasons about the code that exists — not a plausible guess.

Navigate code structure

Walk a function’s control flow, a class inheritance tree, or a file’s include graph — as a compact, paged structure the model can traverse without loading whole files into its context.

Read exactly the right lines

Pull the precise source span for a symbol, with original on-disk coordinates and paging for large bodies — no guessing at offsets, no dumping an entire file to see one function.

See type layout in memory

For builds with debug info, get a type’s byte-by-byte layout — fields, base classes, the vtable pointer, and padding as a named region — so the agent can reason about size, alignment, and waste directly.

Leave notes that stick

The agent can attach short labels and longer descriptions to symbols. They persist across restarts and show up inline on later lookups, so knowledge built up in one session is there for the next.

Warm, incremental, local

The project is indexed once and kept warm; edits are picked up incrementally. Your source is read locally by the engine and is not sent anywhere by the server.

One call to learn the surface

A single discover call tells a cold agent the full tool set, where to start, and the recommended workflow — so it can use the server effectively without being pre-taught.

---

How it fits together

flowchart LR
  A[AI agent / MCP client] -- MCP --> B[CodeXX MCP Server]
  B --> C[CodeXX C++ engine]
  C --> D[Your C++ project]

Your agent talks to the server over MCP. The server is backed by the CodeXX engine, which has already parsed and analysed your project. The agent gets structured answers — symbols, references, structure, layout — instead of raw text it has to interpret.

The CodeXX MCP Server is in preview. See Installation to connect it to your agent, or jump to the Quick Start.