The Model Context Protocol (MCP) server is a lightweight HTTP server that runs on the host machine alongside TestComplete. The server implements MCP, a JSON-based request and response format that AI clients support natively. The AI client sends an MCP request, such as a request to list the tests in your project. The server translates the request into a TestComplete operation, runs it, and returns a structured response to the client.
Every connection requires the server URL from the MCP Settings page in TestComplete.
Prerequisites
Complete the following tasks before you configure an AI client:
-
Install and open TestComplete on the host machine.
-
Enable MCP in TestComplete, and note the port number. The default port is 3001.
-
Confirm that your AI client supports the HTTP transport of the Model Context Protocol, either streamable HTTP or Server-Sent Events (SSE).
Local Connection
Use a local connection when the AI client and TestComplete run on the same machine. Configure the client with the following server URL:
MCP Server URL: http://localhost:3001
| Note: |
If you configured a port other than 3001 in TestComplete, use that port number in the URL. |
Remote Connection
The MCP server also accepts connections from other machines. Any machine or automated agent that can reach the host machine over the network can connect if all of the following conditions apply:
-
The client machine can resolve the host name of the host machine and reach its IP address on the configured port.
-
Any firewall on the host machine, or between the two machines, allows inbound TCP traffic on that port.
To connect from another machine, replace localhost with the IP address or the fully qualified host name of the host machine:
MCP Server URL: http://192.168.1.50:3001
MCP Server URL: http://your-hostname.domain.com:3001
| Note: |
Continuous integration and continuous delivery (CI/CD) pipelines, build agents, and AI orchestration systems that run on separate infrastructure can call TestComplete directly over the network, provided that they can reach the host machine. |
Network and Firewall Considerations
The following table details common connection scenarios:
| Scenario | What to check |
|---|---|
|
Same machine. The AI client and TestComplete run on the same computer. |
No firewall changes are required. Use |
|
Local network. The AI client runs on another machine in the same network. |
In Windows Firewall on the host machine, add an inbound rule that allows TCP traffic on port 3001 or on the port that you configured. |
|
CI/CD agent. A build server or a pipeline connects to the host machine. |
Confirm that network routing between the build server and the host machine is in place, and that the configured port is open. |
|
Remote or cloud agent. The agent runs outside your network. |
A virtual private network (VPN) or network peering between the remote environment and the host machine might be required. |
| Note: |
The MCP server serves plain HTTP and does not enforce HTTPS, so traffic between the client and the server is unencrypted. For connections over untrusted networks, place the server behind a reverse proxy that terminates TLS, or restrict access to a VPN. |
Supported AI Clients
Any client that supports the HTTP transport of MCP can connect to TestComplete MCP. The following table lists common clients and where each one stores the server configuration:
| AI client | Where to configure |
|---|---|
|
Claude Desktop |
The |
|
Cursor |
The |
|
Visual Studio Code with Copilot, Cline, or Continue |
The settings panel of the MCP extension, or the |
|
Windsurf |
The MCP Servers section of the Windsurf settings. |
|
Any MCP-compatible client |
Any location where you can define the server URL. |
In each example that follows, testcomplete is the server name that appears in the client. You can change this name.
Example: Claude Desktop
For Claude Desktop, add the following entry to the claude_desktop_config.json file, and then restart the client:
{
"mcpServers": {
"testcomplete": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"http://localhost:3001"
]
}
}
}
Example: Cursor
For Cursor, add the following entry to the .cursor/mcp.json file in your project folder, and then reload the client:
{
"mcpServers": {
"testcomplete": {
"type": "http",
"url": "http://localhost:3001"
}
}
}
Example: Remote Connection
For a connection from another machine, use the address of the host machine in place of localhost. The following example works with any MCP-compatible client:
{
"mcpServers": {
"testcomplete": {
"type": "http",
"url": "http://192.168.1.50:3001"
}
}
}
| Note: |
Replace |
Verify the Connection
To verify the connection, do the following:
-
Make sure that TestComplete is running on the host machine with MCP enabled.
-
Open your AI client and confirm that it lists TestComplete as an available MCP server.
-
Prompt the AI assistant to verify the connection, for example, “Can you check if you are connected to TestComplete?” or “Ping TestComplete and tell me if the connection is working.”
The server confirms that it is reachable and reports the version of TestComplete that is running.
See Also
TestComplete MCP
Getting Started with TestComplete MCP
Working with TestComplete AI Client
Known Limitations