5.10. MCPs

Note

MCP servers currently are a technology preview.

The Axivion Suite can be accessed and controlled from various coding agents / LLMs via MCP servers. There are different MCP servers available, each serving a different purpose.

5.10.1. Available MCPs

5.10.1.1. Dashboard / Results MCP

The dashboard MCP (ax_dashboard) offers access to the results stored in a given dashboard or database. It is intended for working with findings, analyzing and fixing them.

The ax_dashboard MCP server can also access the local build results if a local build has been performed, allowing it to work with the most recent analysis results alongside dashboard results. Additionally, it can execute local builds to verify whether findings have been resolved, enabling an agent loop for iterative fixing and verification.

5.10.1.2. Documentation MCP

The documentation MCP (ax_documentation) provides improved access to the Axivion documentation via semantic search. It enables LLMs and agents to query the documentation efficiently and can be used standalone or to provide additional context when working with other MCP servers.

5.10.2. How to Obtain the MCPs

The MCP servers are available as Axivion-MCPs-<version>.zip, which is distributed alongside the main Axivion Suite installer.

5.10.3. Setup and Configuration

5.10.3.1. Prerequisites

To run the servers, install the Python packages from requirements.txt inside a virtual environment, ideally managed by uv:

uv venv
uv pip install --requirements <path_to_axivion-mcps>/requirements.txt

The Python executable from this environment is then passed to the MCP server via the BAUHAUS_PYTHON environment variable.

5.10.3.2. Configuration

Dashboard MCP (ax_dashboard)

For certain commands such as creating suppression comments, ax_dashboard needs access to the current project configuration via BAUHAUS_CONFIG (set as usual).

ax_dashboard also cooperates with the Axivion Suite IDE plugins when available, using locally available build results alongside dashboard results.

Documentation MCP (ax_documentation)

The search_axivion_documentation tool requires a search index generated by parse_docs.py. Generate it once after installation:

uv run <path_to_axivion-mcps>/ax_documentation/parse_docs.py --suite-path <path_to_bauhaus-suite>

This creates <path_to_bauhaus-suite>/doc/doc_index/ from the HTML documentation and code examples shipped with the suite.

5.10.3.3. Integration into IDEs

VS Code

VS Code 1.109.2 or later is required for MCP server support. Add the servers to .vscode/mcp.json, adapting the paths to your Axivion installation and project:

{
  "servers": {
    "axdocumentation": {
      "type": "stdio",
      "command": "<path_to_bauhaus-suite>/bin/rfgscript",
      "args": [
        "<path_to_axivion-mcps>/ax_documentation/ax_documentation.py"
      ],
      "env": {
        "BAUHAUS_PYTHON": "<path_to_venv>/bin/python"
      }
    },
    "axdashboard": {
      "type": "stdio",
      "command": "<path_to_bauhaus-suite>/bin/rfgscript",
      "args": [
        "<path_to_axivion-mcps>/ax_dashboard/ax_dashboard.py"
      ],
      "env": {
        "BAUHAUS_INSTDIR": "<path_to_bauhaus-suite>",
        "BAUHAUS_PYTHON": "<path_to_venv>/bin/python",
        "BAUHAUS_CONFIG": "${workspaceFolder}/axivion",
        "AXIVION_DATABASES_DIR": "<optional_path_to_databases>"
      }
    }
  }
}

ax_documentation can also be hosted centrally over HTTP:

MCP_HTTP_HOST=<hostname> MCP_TRANSPORT=http DOC_HTTP_BIND=0.0.0.0 rfgscript <path_to_axivion-mcps>/ax_documentation/ax_documentation.py

For this case, add it as an HTTP server in .vscode/mcp.json instead:

{
  "servers": {
    "axdocumentation_http": {
      "type": "http",
      "url": "http://<hostname>:<port>/mcp"
    }
  }
}

Claude Desktop (Windows)

Add the following to %APPDATA%\claude_desktop_config.json:

{
  "mcpServers": {
    "ax_dashboard": {
      "command": "<path_to_bauhaus-suite>\\bin\\rfgscript.exe",
      "args": [
        "<path_to_axivion-mcps>\\ax_dashboard\\ax_dashboard.py"
      ],
      "env": {
        "BAUHAUS_PYTHON": "<path_to_venv>\\Scripts\\python.exe",
        "BAUHAUS_INSTDIR": "<path_to_bauhaus-suite>",
        "BAUHAUS_CONFIG": "<path_to_project_config>"
      }
    }
  }
}