TestWatch

dev.testwatchPublished by testwatch.devOfficial publisherv1.1.0Updated Oct 29, 2026

Run your end-to-end tests, read why they failed, write new tests. Sign in with OAuth.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

TestWatch is a remote MCP server that lets an assistant run end-to-end tests, inspect why they failed, and write new tests.

What you can do
  • Run end-to-end test suites from the assistant.
  • Read and explain the reasons tests failed.
  • Write new end-to-end tests.
  • Authenticate through OAuth sign-in, or with a bearer API key for headless use.
When to use it
Useful when you want an assistant to trigger end-to-end test runs, diagnose failing tests, and draft new tests without leaving the conversation.
Requirements
A remote MCP endpoint at mcp.testwatch.dev over streamable HTTP. OAuth sign-in is required for interactive clients; headless use needs a TestWatch API key sent in the Authorization header. No local package or environment variables are declared.
Before you install
The server requires authentication: an OAuth sign-in or a TestWatch API key in the Authorization header, which is a secret to keep private. It can run tests and write new tests, so changes may affect your test suite.

Installation

In SourceWeft

  1. Open TestWatch in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.testwatch%2Ftestwatch/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "testwatch": {
      "type": "http",
      "url": "https://mcp.testwatch.dev/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestOct 29, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.