Enforce consistent C++ style and best practices across your codebase. Analyze naming conventions, memory safety, and const correctness, and get
Enforce consistent C++ style and best practices across your codebase. Analyze naming conventions, memory safety, and const correctness, and get actionable modernization suggestions up to C++23. Accelerate reviews with ready-made prompts. Exposed over MCP by the cpp guidelines mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Everything the assistant can do here goes through one of these:
check_naming — Validate C++ identifiers (variables, classes, functions, etc.) against naming conventionscheck_include_guard — Verify header file include guards or #pragma once usageanalyze_memory_safety — Detect memory leaks, dangling pointers, and unsafe memory patternssuggest_modern_cpp — Get modernization suggestions targeting C++11 through C++23check_const_correctness — Find missing const qualifiers on member functions, parameters, and variablesThe server ships on npm as @smithery/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Cpp Guidelines MCP's toolset — check_naming, check_include_guard, analyze_memory_safety and 2 more — is a fair guide to whether it matches your workflow. It is maintained by songjiangzhou; 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.
| Tool | What it does |
|---|---|
| check_naming | Validate C++ identifiers (variables, classes, functions, etc.) against naming conventions |
| check_include_guard | Verify header file include guards or #pragma once usage |
| analyze_memory_safety | Detect memory leaks, dangling pointers, and unsafe memory patterns |
| suggest_modern_cpp | Get modernization suggestions targeting C++11 through C++23 |
| check_const_correctness | Find missing const qualifiers on member functions, parameters, and variables |
{
"mcpServers": {
"cpp-style": {
"command": "uv",
"args": ["run", "mcp", "run", "cpp_style_server.py"],
"cwd": "/path/to/cpp_guidelines_mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.