About Testmo MCP

Claude Desktop

Claude Desktop's claude_desktop_config.json only launches stdio MCP servers, so connecting to our remote HTTP server uses the mcp-remote npm bridge as a thin proxy.

Open Settings → Developer → Edit Config to open claude_desktop_config.json, then add the Testmo entry:

{
  "mcpServers": {
    "testmo": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://sembi-mcp-dev.com/mcp?INSTANCE-URL=your-org.testmo.net&API-KEY=your-api-token-here"
      ]
    }
  }
}

Save the file, then fully quit Claude Desktop (⌘Q on macOS — closing the window is not enough) and relaunch it. The Testmo tools appear under the MCP indicator in the conversation toolbar. If the server doesn't load, check ~/Library/Logs/Claude/mcp*.log (macOS) or the equivalent log path on Windows for errors.

Codex

Edit ~/.codex/config.toml and add a server entry:

[mcp_servers.testmo]
url = "https://sembi-mcp-dev.com/mcp?INSTANCE-URL=your-org.testmo.net&API-KEY=your-api-token-here"

Start a new Codex session — testmo will be listed under the available MCP servers and its tools are ready to use.

ChatGPT Desktop

Open Settings → Connectors → Add new connector, choose Custom MCP server, and provide:

• Name: testmo
• URL: https://sembi-mcp-dev.com/mcp?INSTANCE-URL=your-org.testmo.net&API-KEY=your-api-token-here

Enable the connector. The Testmo tools become available in new conversations. If not already enabled, you'll need to toggle on Developer Mode at the Connectors screen.

Cursor

Open Cursor Settings → MCP → Add new MCP server, or add an entry to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "testmo": {
      "url": "https://sembi-mcp-dev.com/mcp?INSTANCE-URL=your-org.testmo.net&API-KEY=your-api-token-here"
    }
  }
}

Reload Cursor. testmo will show as connected in the MCP settings panel and its tools are available in the Composer / Agent.

Visual Studio Code

Make sure GitHub Copilot is installed and Agent mode is enabled. Register the server with one command:

code --add-mcp '{"name":"testmo","type":"http","url":"https://sembi-mcp-dev.com/mcp?INSTANCE-URL=your-org.testmo.net&API-KEY=your-api-token-here"}'

Or add it manually to .vscode/mcp.json in your workspace (or the user-level mcp.json):

{
  "servers": {
    "testmo": {
      "type": "http",
      "url": "https://sembi-mcp-dev.com/mcp?INSTANCE-URL=your-org.testmo.net&API-KEY=your-api-token-here"
    }
  }
}

Open Copilot Chat in Agent mode and the Testmo tools are ready to use.

Zed

Open the Zed settings file (Cmd/Ctrl + , or ~/.config/zed/settings.json) and add a context server entry:

{
  "context_servers": {
    "testmo": {
      "source": "custom",
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://sembi-mcp-dev.com/mcp?INSTANCE-URL=your-org.testmo.net&API-KEY=your-api-token-here"
      ]
    }
  }
}

Save the file. Open the Assistant panel and the Testmo tools are available to use.

Windsurf

Open Windsurf Settings → Cascade → MCP Servers → Add custom server, or edit ~/.codeium/windsurf/mcp_config.json directly:

{
  "mcpServers": {
    "testmo": {
      "serverUrl": "https://sembi-mcp-dev.com/mcp?INSTANCE-URL=your-org.testmo.net&API-KEY=your-api-token-here"
    }
  }
}

Click Refresh in the MCP servers panel. Once testmo shows as connected, its tools are available to Cascade.

Other MCP Hosts

The Testmo MCP Server is a standard remote MCP server over streamable HTTP, so any MCP-compatible host can connect to it. The connection details are the same regardless of host:

• Transport: HTTP (streamable)
• URL: https://sembi-mcp-dev.com/mcp?INSTANCE-URL=your-org.testmo.net&API-KEY=your-api-token-here

Most hosts accept this in one of three ways. Use whichever your host supports:

1. A built-in UI for adding an MCP server. Look for a "Connectors", "MCP", or "Tools" section in settings, choose to add a remote/HTTP server, and paste the URL above.
2. A JSON config file, typically with an mcpServers (or servers) object. Add an entry like:

   {
     "mcpServers": {
       "testmo": {
         "type": "http",
         "url": "https://sembi-mcp-dev.com/mcp?INSTANCE-URL=your-org.testmo.net&API-KEY=your-api-token-here"
       }
     }
   }

3. A stdio-only host, in which case use the mcp-remote bridge to wrap the HTTP endpoint:

   {
     "mcpServers": {
       "testmo": {
         "command": "npx",
         "args": [
           "mcp-remote",
           "https://sembi-mcp-dev.com/mcp?INSTANCE-URL=your-org.testmo.net&API-KEY=your-api-token-here"
         ]
       }
     }
   }

After adding the server, restart or reload the host. The Testmo tools (projects, runs, cases, automation, etc.) should appear in the host's MCP tool list and be ready to call.