You can configure AI-powered code editors like Claude Code or Github Copilot to use DTP as a Model Context Protocol (MCP) server. Once configured, those tools can use DTP directly.

Configuring the DTP MCP Server

You need to configure your tool to access DTP as an MCP server by providing it one of the following endpoints:

• SSE transport endpoint: <BASE_URL>/grs/mcp/sse
• HTTP stream transport endpoint: <BASE_URL>/grs/mcp

You can do this a couple ways (note that the SSE transport endpoint is used in the examples below):

Adding it to Your Configuration

You can add the endpoint to your configuration. For example:

{
  "servers": {
    "dtp": {
      "url": "http://<dtp_host>:8080/grs/mcp/sse",
      "headers": {"Authorization": "Basic <credentials>"}
    }
  }
}

Note: This example uses basic authorization. If you are using OpenID for authentication, use the header "Authorization": "Bearer <token>" instead.

Adding it with VS Code

You can add the DTP MCP server endpoint using the VS Code CLI. For example:

Linux

code --add-mcp '{"name":"dtp","url":"http://<dtp_host>:8080/grs/mcp/sse","headers":{"Authorization":"Basic <credential>"},"type":"http"}'

Windows

"<VS_CODE_INSTALLATION_DIR>\bin\code" --add-mcp {\"name\":\"dtp\",\"url\":\"http://<dtp_host>:8080/grs/mcp/sse\",\"headers\":{\"Authorization\":\"Basic <credential>\"},\"type\":\"http\"}

Available Tools

The following tools are available. You can also use your MCP Client to get a list of available tools.

• getInfo: Returns DTP server's build version and machine ID.
• getBuild: Returns the latest build.
• getFilter: Returns a filter ID that corresponds to the provided filter name.
• getTestCountResults: Returns test count results for a given build and optional filter.
• getFailedTestCases: Returns a list of failed or incomplete test cases.
• getTestCasesHistory: Provides more details about failed tests. Retrieves the history of test cases based on provided test case IDs and the specified filter ID.
• getFailedTestCasePredictedLabels: Provides more details about failed tests. Returns a map of test case IDs to their predicted labels for the provided test cases.

Example Prompts

The following examples demonstrate the kinds of things you can do with your AI-powered code editing tool once you have configured it to use DTP as an MCP server as well as an idea of the kind of responses you can get. Notice that you do not have to specify the tools you want to use by name; the AI will usually figure it out from your plain-language request. If it's struggling with this, it can be helpful to use words that point it toward the tool you expect it to use.

1. Get the DTP server information
   

   Ran getInfo - dtp (MCP Server) Here's the DTP server information: Product Name: DTP Build Version: 2025.2.0 (5.7.3.20250728) Machine ID: WIN32-9abcdxyz (Default) The server is running the 2025.2.0 build version from July 28, 2025 on a Windows machine.

2. What are the test results for my-filter?
   • Note: Replace "my-filter" with the name of your filter in DTP. The client will use the getFilter, getBuild, and getTestCountResults tools to return test results for your filter.

3. Please provide more details about my failed tests.

   • Note: This is a follow-up prompt after the one above. The client will use the getFailedTestCases, getTestCasesHistory, and getFailedTestCasePredictedLabels tools to return additional details about the failed tests.