- Open your app.
- Find elements, click, type, and assert.
- Get a screenshot after every step.
Before you begin
- An MCP client that supports remote servers, such as Claude, Claude Code, Cursor, VS Code, or ChatGPT.
- A TestDriver account. Sign up at console.testdriver.ai. The free plan includes 30 testing minutes and needs no credit card.
Add the server
- Claude
- Claude Code
- VS Code
- Cursor
- ChatGPT
- Other clients
- Open Settings → Connectors → Add custom connector.
- Paste
https://mcp.testdriver.ai/mcp. - Click Connect, and sign in to TestDriver when the browser opens.
Sign in
The first time your client connects, it opens a browser window where you sign in to TestDriver. Every tool call afterward runs against the team you signed in with. Its usage counts toward that team’s plan. Clients find the sign-in page automatically. The server uses OAuth 2.1 and publishes its authorization details as RFC 9728 protected-resource metadata athttps://mcp.testdriver.ai/.well-known/oauth-protected-resource.
Try it
Ask your client to drive a browser:Available tools
Each action also returns the SDK code for that step. The agent uses it to assemble a runnable Vitest test as it works.
To turn that test into a file you run locally and in CI, set up a project.
Run the server locally
Run the server as a local stdio process for headless automation, or to authenticate with an API key instead of a browser sign-in:TD_API_KEY environment variable. Create a key at console.testdriver.ai/team/api-keys.
Then configure your client to start the server:
.mcp.json
Troubleshooting
The TestDriver tools don't appear in my client
The TestDriver tools don't appear in my client
Check that the URL is exactly
https://mcp.testdriver.ai/mcp. Then restart your client, since most clients read their MCP configuration only at startup.The browser sign-in never finishes
The browser sign-in never finishes
Your client needs to support OAuth 2.1 with Dynamic Client Registration.Clients that only support local (stdio) servers can’t connect to the hosted URL. Run the server locally with an API key instead.
The sandbox expired in the middle of a session
The sandbox expired in the middle of a session
A sandbox shuts down after 5 minutes with no activity.Ask the agent to call
session_extend to keep it alive, or session_start to get a new one.I ran out of testing minutes
I ran out of testing minutes
Sandbox time counts against your plan’s testing minutes. Check your usage and upgrade at console.testdriver.ai/usage.
Next steps
Generate tests
Prompts that get the best tests out of the agent.
Set up a project
Save generated tests and run them locally and in CI.
Provision apps
Launch browsers, extensions, and desktop apps in the sandbox.
Run in CI/CD
Run your tests on every pull request.

