check_namingLABSCO SUMMARY
The review comments you would have made anyway, made first.
Naming, const, include guards and the dangling pointer are what every C++ review spends its first ten minutes on. Getting them out of the way before a human reads the diff leaves the review for the parts that need an argument.
What it is
A style and safety checker for C++ source, with the guideline material behind it readable over the same connection: naming rules, best-practice guides, standard feature docs and design pattern examples.
What you get
- Identifiers validated against naming conventions — variables, classes, functions, namespaces
- Header include guards or #pragma once checked
- Memory safety analysed for leaks, dangling pointers and unsafe patterns
- Modernisation suggestions targeting anything from C++11 through C++23
- Missing const found on member functions, parameters and variables
- Reference material addressable by URI: naming by category, best practices by topic, standard features by version, and patterns including RAII, Pimpl, Factory and Observer
- Two prompt templates — a code review with a general, performance, safety, readability or modern slant, and a refactoring guide aimed at a chosen standard
Requirements
Nothing, if you point a client at the hosted endpoint https://cpp-style-guide-mcp.fly.dev/mcp. Run it locally instead with uv and a clone, or let Smithery install it into your client.
Setup effort
One command — npx -y @smithery/cli install @SongJiangzhou/cpp_guidelines --client claude
USE CASES
01
Cleaning a diff before anyone else reads it
Run the naming and const checks over the changed code so the review starts past the mechanical comments.
02
Finding the pointer bug you suspect is there
Pass the function and get the leak or dangling-pointer pattern named.
03
Bringing older code forward
Ask what a chosen standard would do instead, anywhere from C++11 to C++23.
04
Checking a new header
Confirm the include guard or #pragma once is right before it spreads through the build.
05
Settling a convention argument
Validate the disputed identifier against the convention rather than trading house styles.
5 tools
Listed in project docs. Your client may show a different list.
check_include_guardanalyze_memory_safetysuggest_modern_cppcheck_const_correctnessBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
- uv on PATH
- Python >= 3.12
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
npx
TERMINAL
npx -y @smithery/cli install @SongJiangzhou/cpp_guidelines --client claudeHosted endpoint
ENDPOINT URL
https://cpp-style-guide-mcp.fly.dev/mcpAdd this hosted endpoint to your MCP client.
MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"cpp-style": {
"command": "uv",
"args": [
"run",
"mcp",
"run",
"cpp_style_server.py"
],
"cwd": "<YOUR_PATH_TO_CPP_GUIDELINES_MCP>"
}
}
}
