SmarTT MCP

What it is for#

Writing browser automation is a loop: read the test, write a plan, run it, see what broke, fix it, run it again. Doing that through a chat window means a person copying context in one direction and code back in the other, which is slow and lossy.

The MCP server removes the copying. The agent reads the test from SmarTTest itself, writes the automation back into it, runs the Quality Engine on what it produced, and fixes what the scorecard flags, without you in the middle of each step.

The package#

Two ways to connect#

There is a hosted server you connect to over the network, and a local server you run on your own machine. They expose the same tools, with one difference that decides which you want.

Setting up the remote connector#

The remote server speaks Streamable HTTP and authenticates with OAuth 2.1, using dynamic client registration and PKCE, so there is no key to create, paste, or rotate.

1. 1

   Add the connector in your client

   Point it at:

   MCP server URL

   https://www.smarttest.cloud/api/mcp/http

   In Claude, this is Settings → Connectors → Add custom connector.
2. 2

   Approve access

   Your browser opens on SmarTTest. Log in if you are not already, review what the connector is asking for, and approve.
3. 3

   Done

   The tools appear in your client. Access tokens are short-lived and refresh on their own.

Setting up the local server#

1. Create an API key

In SmarTTest, go to Settings → MCP API Keys and create one. It is shown once, and only a hash is stored, so it cannot be recovered later.

{
  "mcpServers": {
    "smarttest": {
      "command": "npx",
      "args": ["-y", "@smarttest/mcp"],
      "env": {
        "SMARTT_MCP_API_KEY": "your-key-here"
      }
    }
  }
}

Requirements for local execution#

Running tests locally needs a browser and a video encoder. The package installs Playwright as a dependency; the browser binaries themselves are a separate download:

npx playwright install chromium
npx playwright install ffmpeg

How to use it#

The agent works best when you let it close its own loop rather than approving each step. A productive session looks like:

1. 1

   Point it at a test

   "Automate the checkout test in the Payments folder." It finds the project, the folder, and the test on its own.
2. 2

   Let it iterate

   With the local server it can execute without a runId, which leaves no trace in any run. That is the point: the develop-run-develop loop should not pollute your history.
3. 3

   Make it check its own work

   "Run analyze_test_quality and fix what it finds." The scorecard is deterministic, so this is a real check rather than the agent grading itself.
4. 4

   Then execute for real

   Pass a runId when you want the result recorded, or queue the whole run with run_on_runner.

The tools#

Forty tools, grouped by what they touch. Each one is documented with its parameters and what it is for in the tool reference.

• Projects, folders and tags: finding your way around.
• Tests: reading, creating, updating, archiving, and quality analysis.
• Reusable actions: the shared blocks and how tests attach to them.
• Environments and variables: what execution needs, without exposing secrets.
• Runs: creating them, recording results, closing them.
• Execution: locally, or queued onto a runner.

If something is not working#

• No tools appear: the client did not connect. Restart it, and check the key is in env and not in args.
• Everything returns unauthorized: the key was revoked, or belongs to a different instance than SMARTT_API_BASE_URL points at.
• Execution tools are missing: you are on the remote connector. They only exist locally; use run_on_runner.
• Runs fail in seconds with a path error: ffmpeg is not installed. See above.