# Testsy MCP server

Source: https://glimind.com/server/mcp-registry%2Fdev.testsy%2Ftestsy
Registry id: `mcp-registry/dev.testsy/testsy`
Status: live (checked 2026-11-22T16:20:06.687Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 900
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "testsy-mcp-server": {
      "type": "http",
      "url": "https://app.testsy.dev/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http testsy-mcp-server https://app.testsy.dev/mcp
```

## Tools (48)

- `add_credential`: Store 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 th
- `add_endpoint`: Save the definition of one call into your own system that the tester may make during a run (for example "create a voucher"). This only stores the definition: it
- `add_test_file`: Add 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-Na
- `complete_build_upload`: Finish the upload with every part's etag. The build is checked (app id, version, whether our devices can run it) and returned. Use the returned build.id in run_
- `create_build_upload`: Start a build upload and get signed links that upload the file without an API key: run the returned command in a shell, or PUT each part and POST complete to th
- `create_project`: Create a project, for example one per site or app. Reference: https://testsy.dev/docs/mcp/
- `create_schedule`: Run 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. Reference: https://testsy
- `create_share_link`: A read-only link to a run's result, replay and video that anyone can open without signing in, until it expires. Reference: https://testsy.dev/docs/mcp/
- `create_test`: Create 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
- `create_watch_link`: A 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
- `delete_build`: Delete a build. Runs that used it keep their results; a build a test pins cannot be deleted. Reference: https://testsy.dev/docs/mcp/
- `delete_credential`: Delete a sign-in account. Tests that sign in with it stop running until it is added again or they are edited. Reference: https://testsy.dev/docs/mcp/
- `delete_endpoint`: Delete an endpoint. Reference: https://testsy.dev/docs/mcp/
- `delete_project`: Archive a project: its tests stop running; past runs stay in the run history. Reference: https://testsy.dev/docs/mcp/
- `delete_schedule`: Delete a schedule. Reference: https://testsy.dev/docs/mcp/
- `delete_share_link`: Turn off a share link straight away. Reference: https://testsy.dev/docs/mcp/
- `delete_test`: Archive a test: it stops running; past runs stay in the run history. Reference: https://testsy.dev/docs/mcp/
- `delete_test_file`: Remove one of a test's files. Reference: https://testsy.dev/docs/mcp/
- `duplicate_test`: Copy 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
- `find_build`: Is this build already uploaded? Looks up the project's newest ready build by the file's sha256, else by a native fingerprint; build is null when neither matches
- `get_build`: One build: its app id, version, status and any warnings. Reference: https://testsy.dev/docs/mcp/
- `get_network`: How our browsers reach your sites: the static addresses to allow-list, the country they browse from, and the countries available. Reference: https://testsy.dev/
- `get_project`: One project. Reference: https://testsy.dev/docs/mcp/
- `get_run`: A 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 r
- `get_test`: One test: its start address, requirement, plan, options and latest run. Reference: https://testsy.dev/docs/mcp/
- `get_usage`: Plan, runs used this billing period, included runs, extra-run packs and runs left. Reference: https://testsy.dev/docs/mcp/
- `get_workspace`: The workspace this key belongs to: its id, name and plan, and this period's usage. Reference: https://testsy.dev/docs/mcp/
- `import_build`: Fetch a build from an https link (an EAS, Bitrise, S3 or GitHub artifact link, up to the build size limit) into the project; it is checked and ready to run. Not
- `list_builds`: The app builds uploaded to a project (Android .apk, iOS Simulator .app zipped), newest first, with the largest size and part size for uploads. Reference: https:
- `list_credentials`: The sign-in accounts stored for a project: names, usernames and sites. Passwords are never returned. Reference: https://testsy.dev/docs/mcp/
- `list_devices`: The phones and tablets app tests can run on, and their OS versions (latest first). Pass device and osVersion to create_test, update_test, run_test or run_projec
- `list_endpoints`: Calls into your own systems the tester may make during a run (for example "create a voucher"). Headers are never returned. Reference: https://testsy.dev/docs/mc
- `list_projects`: The projects in this workspace (a project groups the tests of one site or app). Reference: https://testsy.dev/docs/mcp/
- `list_runs`: Recent runs, newest first, optionally for one test or project or with one status; or the runs with the given ids. Reference: https://testsy.dev/docs/mcp/
- `list_schedules`: When tests run by themselves: every schedule in the workspace, or those of one test or project. Reference: https://testsy.dev/docs/mcp/
- `list_share_links`: The share links made for a run, with when they expire and how often they were opened. Reference: https://testsy.dev/docs/mcp/
- `list_test_files`: Files a test can upload during its steps (for example an import file). Reference: https://testsy.dev/docs/mcp/
- `list_tests`: The tests of a project, each with its latest run. Reference: https://testsy.dev/docs/mcp/
- `plan_test`: Have the assistant draft a test from a plain-language description, or revise a plan, without saving anything. Returns the proposed steps, checks, values to reco
- `revoke_watch_link`: Turn off every watch link of a run straight away. Reference: https://testsy.dev/docs/mcp/
- `run_project`: Start 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 ru
- `run_test`: Start 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 
- `set_browse_from`: Choose 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 us
- `stop_run`: Stop a queued or running run. A run you stop is not counted. Reference: https://testsy.dev/docs/mcp/
- `update_project`: Rename a project or change its description. Reference: https://testsy.dev/docs/mcp/
- `update_schedule`: Pause or resume a schedule. Reference: https://testsy.dev/docs/mcp/
- `update_test`: Change 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 t
- `wait_run`: Wait 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 fina

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
