Testmode AI

digital.amberPublished by amber.digitalv1.6.2Updated Nov 3, 2026

Write, run and check natural-language browser tests of your web app from your AI assistant.

VerifiedStreamable HTTPWeb executableBrowser AutomationDeveloper Tools

Overview

AI-generated overview

Testmode AI lets an assistant write, run and check natural-language browser tests of a web app through a hosted remote endpoint.

What you can do
  • Write natural-language browser tests for a web app from the assistant.
  • Run those tests against the app and check their results.
  • The server is a hosted remote endpoint, so the assistant connects to it directly rather than running a local package; no individual tools are listed in the supplied material.
When to use it
Useful when you want an assistant to turn plain-language descriptions of user flows into browser tests and verify them against a web app, instead of hand-writing test scripts.
Requirements
A remote MCP endpoint at the provider's API host, reached over streamable HTTP. Authentication is OAuth and required, so the user must sign in to a Testmode account through the OAuth flow. Network access to the endpoint is needed.
Before you install
Access is tied to an OAuth sign-in to the provider's service, so the assistant acts on your account. Tests run against your web app, which may involve signing in to it and touching real data or environments; check which environment and account the tests target before running them. The supplied material gives no detail on pricing or data handling.

Installation

In SourceWeft

  1. Open Testmode AI 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/digital.amber%2Ftestmode/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": {
    "testmode-ai": {
      "type": "http",
      "url": "https://api.testmode.ai/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

2
  1. v1.6.2LatestNov 3, 2026
  2. v1.6.1Oct 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.