Troubleshooting

This section addresses common issues users may encounter while interacting with the DVT MCP Server and provides step-by-step guidance for resolution.

MCP Connector Startup Issues

If the MCP Connector fails to launch, follow these troubleshooting steps:

  1. Inspect the AI agent logs for error messages or stack traces that may indicate root causes.

  2. Ensure the MCP configuration includes the DVT_HOME environment variable.

  3. Manually execute the configured command in a terminal to validate behavior.

  4. If unresolved, submit a detailed issue report.

Tool Call Failures

If a tool call initiated by the AI agent fails, follow these steps:

  1. Check the tool call result message for additional failure details.

  2. Ensure the project_path tool argument points to a valid project with an active DVT MCP CLI Endpoint (verify via dvt_mcp.sh list). Confirm the DVT MCP CLI Endpoint is not already in use (check with dvt_mcp.sh list).

  3. If the issue persists, submit a detailed issue report.

Unexpected Tool Call Results

If tool calls return unexpected data:

  1. Check if the project_path argument points to the correct target project.

  2. If anomalies persist, submit a detailed issue report.

Note

While compilation is in progress all tool calls will return a message stating this.

Outdated Tool Call Results

To address outdated data from tool calls:

  • Incremental Builds: Trigger an incremental build for modified files by instructing the LLM: “Please compile all files changed so far.”

  • Full Project Rebuild: If needed, initiate a full rebuild by instructing the LLM: “Please perform a DVT full build of the project.”