# Let Cursor check its own work in a real browser

> Connect Testsy to Cursor over MCP so the agent can save a plain-language test, run it against your deployed app or a phone build, and read the verdict.

By Jason Nguyen, Founder, Testsy. Published 2026-11-21. https://testsy.dev/blog/let-cursor-check-its-own-work-in-a-browser/

## Why the agent should not grade itself

Cursor can write a feature and a test for it in the same breath. Both come from the same context, so they share the same assumptions: if the agent misunderstood what "save the draft" means, the test checks the misunderstanding. When the tests pass, they tell you the code matches what the agent believed.

A check from outside does not share those beliefs. It opens your deployed app, does what the sentence says, and reports what was on the screen. That is the job Testsy does, and over MCP Cursor can ask for it directly.

## Connect it

Two ways, from [the MCP docs](https://testsy.dev/docs/mcp/):

- **The plugin.** [testsy-ai/testsy-cursor](https://github.com/testsy-ai/testsy-cursor) holds the MCP configuration and three skills.
- **By hand.** Create an API key in **Settings → API keys** (choose the kind that can also create and edit tests if Cursor should save new tests), store it as `TESTSY_AI_API_KEY`, and add the server to Cursor's MCP settings:

```json
{
  "mcpServers": {
    "testsy": {
      "url": "https://app.testsy.dev/mcp",
      "headers": { "Authorization": "Bearer qa_…" }
    }
  }
}
```

Keep the key in an environment variable or secret store. Do not paste it into a prompt or commit it. To get the skills without the plugin, copy the `skills/` folders from the plugin repository into your project's `.cursor/skills/`.

The three skills are **testsy-check-release** (check a change before you call it done), **testsy-investigate-run** (read a failed result and find the cause) and **testsy-regression-from-bug** (turn a bug into a saved test).

## What Cursor does with it

Ask in plain words: "Check that a new user can sign up and create a project on our staging site." The agent works through the same steps you would in the app:

1. `list_projects`, then `plan_test` with what you asked. Testsy drafts the steps and the checks.
2. It shows you the plan. You correct it ("the button is called Create workspace, not New project") and it calls `plan_test` again with the change.
3. `create_test` saves the confirmed plan; `run_test` starts it and returns a watch link you can open to see the run live, no sign-in needed.
4. `wait_run` until the verdict is final, then it reads each check, its reason and the value it was decided on.
5. If a check failed, it fixes the code, deploys, and runs the same test again.

![A plan before it runs: the steps, the checks, and the options such as the screen size and the sign-in account.](https://testsy.dev/docs/img/plan-light.webp)

The test is saved in your workspace. Next week, after a different change, Cursor (or you, or CI) runs it again.

## Apps too

For an iPhone or Android app, the agent can upload the build it just made and run the app's tests on it: `find_build` to reuse a build that is already there, otherwise `create_build_upload` and a shell command that sends the file. The steps are in [the MCP docs](https://testsy.dev/docs/mcp/#upload-a-new-app-build-and-run-it).

## Keep a person in the loop

- Review the plan before the first run. Runs can create accounts and change data, so point them at staging with made-up details.
- Cursor's own approval settings decide when it asks before a tool runs. Leave approvals on until you trust the flow.
- Read the evidence, not only the verdict. Every result keeps the screen each check was read from.

Every run counts toward your plan like any other. The free trial has 10.

This post is part of [Testing an app you built with AI](https://testsy.dev/blog/test-an-app-you-built-with-ai/). The same setup for other agents: [Claude Code](https://testsy.dev/blog/make-claude-code-test-what-it-built/), [Codex](https://testsy.dev/blog/let-codex-check-its-own-work-in-a-browser/), [Gemini CLI and the Claude app](https://testsy.dev/blog/connect-testsy-to-gemini-cli-and-the-claude-app/).
