Run your end-to-end tests, read why they failed, write new tests. Sign in with OAuth.
Connect Remote server
claude mcp add --transport http testwatch https://mcp.testwatch.dev/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"testwatch": {
"url": "https://mcp.testwatch.dev/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"testwatch": {
"type": "http",
"url": "https://mcp.testwatch.dev/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://mcp.testwatch.dev/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server asks for a key before it lists its tools. Connect it with your own key to see them.
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | Optional: Bearer <TestWatch API key> for headless use. Interactive clients sign in with OAuth. |
Details
| Endpoint | https://mcp.testwatch.dev/mcp (Streamable HTTP) |
| First published | 29 Oct 2026 |
| Last updated | 29 Oct 2026 |
| Registry name | dev.testwatch/testwatch |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
