Agents Index

Testsy

OnlineNew

Run plain-English QA tests on websites and mobile apps, then inspect each check and its evidence.

Visit publisherConnectJSON

What it can do: 48 tools

  • get_workspace read-onlyThe workspace this key belongs to: its id, name and plan, and this period's usage.
  • get_usage read-onlyPlan, runs used this billing period, included runs, extra-run packs and runs left.
  • get_network read-onlyHow our browsers reach your sites: the static addresses to allow-list, the country they browse from, and the countries available.
  • set_browse_fromChoose the country our browsers and devices reach your sites and app servers from (web and app tests), or automatic: the site's own country (an app test then uses our default country).
  • list_projects read-onlyThe projects in this workspace (a project groups the tests of one site or app).
  • get_project read-onlyOne project.
  • create_projectCreate a project, for example one per site or app.
  • update_projectRename a project or change its description.
  • delete_projectArchive a project: its tests stop running; past runs stay in the run history.
  • list_tests read-onlyThe tests of a project, each with its latest run.
  • get_test read-onlyOne test: its start address, requirement, plan, options and latest run.
  • create_testCreate a test of a website (url) or of an app (platform android or ios, and appId; device phone or tablet and osVersion, default a phone on the latest OS). Pass `plan` (from plan_test, after the requester confirmed it):
  • update_testChange a test: its title, start address, requirement, plan or options. Only the fields you pass change; within `options`, only the options you pass change and the others keep their values.
  • duplicate_testCopy a test under a new title: the test's info is copied over (start address, requirement, plan, options and files). Its run history and schedules stay with the original. The copy counts toward the plan's test limit. Wit
  • delete_testArchive a test: it stops running; past runs stay in the run history.
  • plan_test read-onlyHave the assistant draft a test from a plain-language description, or revise a plan, without saving anything. Returns the proposed steps, checks, values to record, assumptions and any questions only the requester can ans
  • list_test_files read-onlyFiles a test can upload during its steps (for example an import file).
  • add_test_fileAdd a file the tester can upload during the test: up to 25 MB, up to 10 files per test. REST: send the raw bytes as the body with the file name in the X-File-Name header (or ?name=), or JSON {name, contentBase64}. MCP: n
  • delete_test_fileRemove one of a test's files.
  • list_credentials read-onlyThe sign-in accounts stored for a project: names, usernames and sites. Passwords are never returned.
  • add_credentialStore a sign-in account the tester can use. The password is encrypted, never returned, and never sent to the tester's AI: the tester types it. Tests refer to the account by name ("Sign in as the account \"customer\""). T
  • delete_credentialDelete a sign-in account. Tests that sign in with it stop running until it is added again or they are edited.
  • list_endpoints read-onlyCalls into your own systems the tester may make during a run (for example "create a voucher"). Headers are never returned.
  • add_endpointAdd a call the tester may make into your system. It sees only the name, the description and what the call returned. Using endpoints in a run needs a paid plan. bodyTemplate may contain {{param}} placeholders the tester f
  • delete_endpointDelete an endpoint.
  • run_testStart a run of one test. Runs take minutes: poll get_run until final is true. watchUrl opens the run live without signing in. App tests run the newest build of their app unless buildId names another (see list_builds). wa
  • run_projectStart a run of every test in a project (a suite). Each started run has a watchUrl to watch it live without signing in. buildIds: builds to use; each app test runs the one of its own app. Tests that could not start are li
  • list_runs read-onlyRecent runs, newest first, optionally for one test or project or with one status; or the runs with the given ids.
  • get_run read-onlyA run: its status, and once final the verdict, the headline, each check's result with the reason, the values read, and links to the video, screenshots and the result page.
  • wait_run read-onlyWait up to seconds (default 25, at most 55) for a run to finish, then return it: one call instead of polling get_run every few seconds. Call it again while final is false. The answer comes back the moment the run is fina
  • stop_runStop a queued or running run. A run you stop is not counted.
  • create_watch_linkA view-only link to watch a run live and read its result, with no sign-in, valid while it runs and for some hours after. Runs started here get one automatically; this makes another, or one for a run started from the web
  • revoke_watch_linkTurn off every watch link of a run straight away.
  • list_share_links read-onlyThe share links made for a run, with when they expire and how often they were opened.
  • create_share_linkA read-only link to a run's result, replay and video that anyone can open without signing in, until it expires.
  • delete_share_linkTurn off a share link straight away.
  • list_schedules read-onlyWhen tests run by themselves: every schedule in the workspace, or those of one test or project.
  • create_scheduleRun a test by itself: on chosen weekdays, or monthly on a day, at a time in a time zone. Each scheduled run counts like any other run.
  • update_schedulePause or resume a schedule.
  • delete_scheduleDelete a schedule.

…and 8 more.

Connect it

Claude Code
claude mcp add --transport http testsy https://app.testsy.dev/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://app.testsy.dev/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "testsy": {
      "url": "https://app.testsy.dev/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "testsy": {
      "type": "http",
      "url": "https://app.testsy.dev/mcp"
    }
  }
}

Questions

What does Testsy do?

Run plain-English QA tests on websites and mobile apps, then inspect each check and its evidence. It exposes 48 tools to AI assistants.

What tools does Testsy provide?

48 tools, including get_workspace, get_usage, get_network, set_browse_from, list_projects, get_project, create_project, update_project, delete_project, list_tests, get_test, create_test….

How do I connect Testsy to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://app.testsy.dev/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Testsy require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Testsy online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Testsy?

testsy.dev. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Project Management