Overview
C/C++test provides includes an MCP (Model Context Protocol) Server extension that allows you to smoothly integrate your LLM agents or applications (for example, Copilot) with enables seamless integration between C/C++test functionality. The C/C++test and AI agents or LLM-based coding assistants (such as GitHub Copilot). This MCP Server can be integrated used within any LLM-based enabled development environment that supports MCP Server integration, including Eclipse, Visual Studio, VS Code, and others. With this extension, an LLM AI agent can interact directly with C/C++test, providing delivering context-aware guidance, analysis, and analysisautomation.
This extension allows you to use your LLM agentsuse an AI coding assistant to:
- Retrieve details about static analysis rules.
Review static analysis violations reported in your project.
Suggest fixes for violations based on provided code snippets or files.
- Suggest rules that are appropriate for specific issues.
- Access information from the product user guide.
The MCP server launcher is located in the <INSTALL_DIR>/integration/mcp directory.
| Note |
|---|
The Parasoft MCP server uses the stdio transport protocol exclusively. Parasoft MCP tools do not access any external systems or services. |
The following procedures demonstrate how to integrate an LLM-based agent (using Copilot as an example) with C/C++test in different environments.
...
MCP Server Tools Reference
| Tool | Description | Notes |
|---|---|---|
| get_relevant_rules | Returns a list of static analysis rules matching the user query. Each entry contains the rule header and a comma-separated list of corresponding rule identifiers. | |
| get_rule_documentation | Returns the documentation for the static analysis rule together with a path to the original documentation file for reference. | An exact rule ID must be provided, for example, BD-PB-ARRAY. |
| get_violations_from_report_file | Extracts violations from a report XML file and outputs them in JSON format along with key details. Results are refined using optional filters: rule ID, severity and source file name. | An absolute path to the report XML file must be provided. The server must have local access to the file. |
| search_documentation | Searches the documentation to retrieve relevant pages matching the user query. Returns the content of each page and its source URL. To search static analysis rule documentation, use get_rule_documentation or get_relevant_rules tools. |