One backend for every editor of mcpp projects
VS Code · CLion · Neovim build, run, test, debug and pack alike
English | 简体中文
Documentation · Architecture · Protocol · For agents · Contributing · Releases
An editor integration of a build tool makes many decisions: which command a build runs, what a test
result means, how dangerous a cleanup is. If each editor makes them separately, the editors drift
apart. mcpp-ide makes them once. Its backend, mcpp-ide serve, reads only mcpp's machine contract
and answers every editor as an LSP server. Each plugin then shows those answers in its editor's own UI.
%%{init: {"theme": "base", "flowchart": {"curve": "basis", "nodeSpacing": 26, "rankSpacing": 56, "padding": 14}, "themeVariables": {"fontFamily": "ui-sans-serif, system-ui, -apple-system, Segoe UI, sans-serif", "fontSize": "14px", "lineColor": "#54aeff", "edgeLabelBackground": "#ffffff"}}}%%
flowchart TB
vscode("<b>VS Code</b><br/>mcpp-vscode"):::client
clion("<b>CLion</b><br/>mcpp-clion"):::client
nvim("<b>Neovim</b><br/>mcpp-nvim"):::client
agent("<b>Agents</b><br/>mcpp-ide skill"):::client
serve("<b>mcpp-ide serve</b><br/>LSP · every decision"):::core
mcppls("<b>mcppls</b><br/>C++ language server"):::ls
mcpp("<b>mcpp</b><br/>build · test · pack"):::tool
vscode & clion & nvim & agent --> serve
serve -- contract --> mcpp
serve -. status .-> mcppls
classDef client fill:#ffffff,stroke:#54aeff,color:#0550ae
classDef core fill:#0969da,stroke:#0550ae,color:#ffffff
classDef ls fill:#fbefff,stroke:#c297ff,color:#6639ba
classDef tool fill:#f6f8fa,stroke:#8c959f,color:#24292f
linkStyle 5 stroke:#c297ff
- One answer everywhere: what a build runs, how a test is reported and what a cleanup costs are decided by the backend
- Only mcpp's contract: no manifest parsing and no dependency resolution of its own
- Tests as mcpp states them: programs, cases, live results, diffs, metrics and Test Insights
- Jobs in order: one build at a time per project, a newer build replaces a waiting one, and cancelling ends cleanly
- Safe cleanups: each plan has a danger level, a preview and the confirmation that level requires
| VS Code 1.91+ | CLion 2026.1+ | Neovim 0.10+ | |
|---|---|---|---|
| Install | Marketplace · Open VSX | JetBrains Marketplace | xlings install mcpp-ide-nvim |
| Build · run · test | tasks, Testing view | run configurations, test runner | :Mcpp, quickfix |
| Debug | CodeLLDB · C/C++ · lldb-dap | GDB · LLDB | nvim-dap |
| Views | libraries, graphs, cache, settings | native trees, forms, JCEF graphs | floating windows |
| C++ (mcppls) | installed with it | mcppls plugin | xlings install mcppls-nvim |
| Guide | mcpp-vscode | mcpp-clion | mcpp-nvim |
mcpp.toml and build.mcpp get completion, hover, jumps and diagnostics in every editor. The VS Code and
CLion packages carry the backend for Linux x64/arm64, macOS arm64 and Windows x64; offline, install the
.vsix or .zip from Releases. Agents and other clients use xlings install mcpp-ide, then
mcpp-ide serve. Verify any install with mcpp-ide self-check; versions: docs/versions.md.
Paste this into any coding agent. It reads only what your task needs, and asks you first when the task is not clear.
Work with mcpp-ide (https://github.com/mcpp-community/mcpp-ide), the IDE layer of mcpp.
Read AGENTS.md first, then only what my task needs:
- install or use it: agents/README.md, verified with `mcpp-ide self-check` on my project
- understand it: docs/architecture.md, saying which layer owns what
- report a bug or propose a feature: .agents/skills/mcpp-ide-contributing, triage first
(mcpp, mcppls, backend or one plugin; fix or workaround), then draft the issue from its template
- change the code: that skill and .agents/skills/mcpp-ide-development, with tests that prove it
My task: <describe it, or leave it empty>
If it is empty or unclear, tell me in three lines what mcpp-ide is, then ask which of the above
I want, with one suggested first step for each. Ask me before opening an issue or a pull request,
pushing, or tagging.
mcpp build && mcpp test # the backend, its mocks and mcpp-ide-dev
(cd mide-plugins/vscode && npm ci && npm test) # VS Code, the parity gates included
(cd mide-plugins/clion && gradle buildPlugin verifyPlugin) # CLion (xlings install gradle)
nvim --headless --clean -l mide-plugins/nvim/tests/smoke.lua # NeovimThe environment, the tests for each component, common changes and the release procedure are in the development skill.
Every change starts with an issue (templates) and goes through a pull request. The rules are in AGENTS.md: who owns what, how to triage (core or plugin, fix or workaround), versions and code. The procedure for people and agents is in the contributing skill. Questions go to the forum.