← Back to directory
P

Pare Cmake

Community
Structured CMake/CTest build system operations as typed JSON.
GitHub source repository ↗
★ 138 Stars Category · Dev Tools Popular Source revision 57e1980e8375
24FMRS · D
Reliability
2/20
Security and permissions
4/20
Maintenance
10/20
Documentation
3/20
Setup experience
5/20

Pare CMake server provides structured CMake/CTest output, ideal for agent integration, but be aware of potential system impact from build commands.

Read the FMRS scoring method →

Pare CMake is an MCP server within the Pare project that wraps CMake and CTest build tools, converting brittle command-line output into schema-validated JSON for AI agents to consume directly without parsing terminal text. Built in TypeScript, it communicates via stdio and offers token-efficient structured responses.

Tools

The tool list has not been reviewed yet.

Setup

Add the following JSON to your MCP client configuration (e.g., Claude Desktop):

{
  "mcpServers": {
    "pare-cmake": {
      "command": "npx",
      "args": ["-y", "@paretools/cmake"]
    }
  }
}

Ensure Node.js >= 20 and restart your client session.

claude_desktop_config.json
{
  "mcpServers": {
    "pare-cmake": {
      "command": "npx",
      "args": [
        "-y",
        "@paretools/cmake"
      ]
    }
  }
}

Fit and risk

Best for

  • C/C++ projects using CMake build system.
  • AI coding assistants needing reliable, programmatic access to build status.

Not for

  • Not applicable for projects without CMake or CTest.
  • Not suited for scenarios requiring GUI or interactive build tools.

Required permissions

  • Executes CMake and CTest commands, potentially reading/writing project directories.
  • Receives commands via stdio and returns JSON output.

Risks and side effects

  • Executing build commands may modify the file system or run long tasks.
  • Misconfiguration or faulty build commands could lead to build failures or resource consumption.
  • As a third-party tool, there is supply chain risk; verify package authenticity.

Troubleshooting

  1. If npx is not found, verify Node.js is installed and PATH is set.
  2. If startup is slow, pre-cache by running `npx -y @paretools/cmake` once.
  3. If MCP connection times out, increase client initTimeout or set MCP_TIMEOUT.
  4. Check Node.js version is >= 20.

Use cases

Let AI agents safely execute CMake configure and build steps.
Run CTest tests and fetch structured results within agent workflows.
Reduce token consumption and errors from parsing command-line output.

Supported clients

Claude DesktopFull support
Claude CodeFull support
CursorFull support
VS Code / CopilotFull support
WindsurfFull support
Cline / Roo CodeFull support
OpenAI CodexFull support
Gemini CLIFull support
ZedFull support
Continue.devFull support