Page History

...

The MCP server is located at <INSTALL_DIR>/integration/mcp/.

Prerequisites:

• dotTEST is installed.

• Java is available (the launcher uses  uses dotTEST's bundled JRE automatically).

...

Run the MCP launcher script: <INSTALL_DIR>/integration/mcp/dottestmcp.batbat When launched, the MCP server starts a local process that communicates over stdio using the Model Context Protocol. The coding agent connects to it and gains access to the following tools:

• Search dotTEST documentation — queries dotTEST feature docs bundled in dottest-ai-docs.zip

• Get static analysis rule documentation — retrieves detailed documentation for

...

• specific dotTEST

...

• rules

• Get relevant rules — finds rules related to a given topic or keyword

• Get violations from a report — parses and filters

...

dotTEST

...

• a dotTEST XML report (report.xml) to retrieve violations

• Get a path to dottestcli — returns a path to dottestcli inside the same installation directory as the MCP server. This can be customized by setting the dottest.cli.path property in the mcp/etc/dottestmcp.properties file.

The server uses the current working directory as the workspace root and stores its local cache in .dottest/dottestmcp/ within that directory.

...

The MCP server reads its settings from <INSTALL_DIR>/integration/mcp/etc/dottestmcp.properties. The default configuration is: 

documentation.path=${dottestmcp:root_dir}/dottest-ai-docs.zip
rule.documentation.path=${dottestmcp:root_dir}/dottest-ai-rules.zip
rule.doc.html.location=${dottestmcp:root_dir}/../../rules/doc.zip
product.name=dotTEST

These paths are resolved relative to the MCP server root directory and generally do not need to be changed.

...

However adding the dottest.cli.path property can change the behavior of the get_dottestcli_path tool in case customization is needed.

Local Storage

The MCP server stores its runtime cache in the following location:

...