Testsy

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

• 연결 방식: 클라우드에서 실행
• 전송 방식: Streamable HTTP
• 카테고리: 기타
• 입력해야 할 값: Authorization

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

필요한 것

• 클라우드에서 실행설치할 것 없음. 인터넷으로 연결돼요

어떤 앱을 쓰세요?

claude mcp add --transport http testsy https://app.testsy.dev/mcp --header 'Authorization: your-value'

{
  "mcpServers": {
    "testsy": {
      "url": "https://app.testsy.dev/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "servers": {
    "testsy": {
      "type": "http",
      "url": "https://app.testsy.dev/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

직접 입력할 값

• Authorization 비밀 HTTP header
  Optional: Bearer followed by a Testsy workspace API key. Without it, clients sign in with OAuth when a tool is first called; listing the tools needs neither.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

어떤 앱에서 쓸 수 있나요

이 서버의 연결 방식과 각 앱의 공식 문서를 바탕으로 했어요. 2026년 11월 10일 확인.

인터넷으로 연결하는 앱

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

모든 앱과 장단점 →

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 10일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

• get_workspace

  The workspace this key belongs to: its id, name and plan, and this period's usage.

• get_usage

  Plan, runs used this billing period, included runs, extra-run packs and runs left.

• get_network

  How our browsers reach your sites: the static addresses to allow-list, the country they browse from, and the countries available.

• set_browse_from

  Choose the country our browsers visit your sites from (web tests), or automatic: the site's own country.

• list_projects

  The projects in this workspace (a project groups the tests of one site or app).

• get_project

  One project.

• create_project

  Create a project, for example one per site or app.

• update_project

  Rename a project or change its description.

• delete_project

  Archive a project: its tests stop running; past runs stay in the run history.

• list_tests

  The tests of a project, each with its latest run.

• get_test

  One test: its start address, requirement, plan, options and latest run.

• 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 `plan` (from plan_test, after the requester confirmed it): it is stored as the approved checklist and the tester follow

• 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 the others keep their values.

• delete_test

  Archive a test: it stops running; past runs stay in the run history.

• 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 record, assumptions and any questions only the requester can answer. Show the plan to the requester; to change it, call agai

• list_test_files

  Files a test can upload during its steps (for example an import file).

• 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-Name header (or ?name=), or JSON {name, contentBase64}. MCP: name and contentBase64. A file with the same name replaces th

• delete_test_file

  Remove one of a test's files.

• list_credentials

  The sign-in accounts stored for a project: names, usernames and sites. Passwords are never returned.

• 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 the account by name ("Sign in as the account \"customer\""). Through MCP the password passes through your AI agent: prefer

• delete_credential

  Delete a sign-in account. Tests that sign in with it stop running until it is added again or they are edited.

• list_endpoints

  Calls into your own systems the tester may make during a run (for example "create a voucher"). Headers are never returned.

• add_endpoint

  Add 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 fills in. Headers (for example Authorization) are encrypted a

• delete_endpoint

  Delete an endpoint.

• 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 their app unless buildId names another (see list_builds). watchUrl is a view-only link anyone can open (no sign-in) to w

• 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 runs the one of its own app. Tests that could not start are listed in skipped with the reason. REST: send an Idempotency-K

• list_runs

  Recent runs, newest first, optionally for one test or project or with one status; or the runs with the given ids.

• 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 result page.

• 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 final is false. The answer comes back the moment the run is final (verdict, checks and evidence in), or when the time is up

• stop_run

  Stop a queued or running run. A run you stop is not counted.

• 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; this makes another, or one for a run started from the web app. The link shows the live screen, the steps and checks so

• revoke_watch_link

  Turn off every watch link of a run straight away.

• list_share_links

  The share links made for a run, with when they expire and how often they were opened.

• 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.

• delete_share_link

  Turn off a share link straight away.

• list_schedules

  When tests run by themselves: every schedule in the workspace, or those of one test or project.

• 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.

• update_schedule

  Pause or resume a schedule.

• delete_schedule

  Delete a schedule.

• 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_project. A new app test runs on a phone with the latest OS unless you choose otherwise; the version is saved with the test, so

• 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.

• get_build

  One build: its app id, version, status and any warnings.

• 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. A sha256 match means the exact file is uploaded: run it with run_test {buildId} / run_project {buildIds} instead of up

• 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 the links. The build is then checked and ready to run. For AI agents: tool arguments cannot carry a build, so hand the byt

• 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. Nothing to upload from your side. The link must be https to a public host name; up to 3 redirects are followed. headers (op

• 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_test {buildId} or run_project {buildIds} to run the new build. Uploading alone does not start a run. The command from cr

• delete_build

  Delete a build. Runs that used it keep their results; a build a test pins cannot be deleted.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 11일 점검

• ✓ 통과

  제작자와 저장소 일치

  레지스트리 이름이 도메인 testsy.dev 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)

• ✓ 통과

  계속 관리되고 있음

  코드 마지막 변경: 오늘

• … 아직 점검 안 함

  라이선스 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• ✓ 통과

  엔드포인트 응답

  354ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✓ 통과

  도구 설명에 숨겨진 지시 없음

  도구 설명 47개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

기타 카테고리의 다른 서버와 비교i

• 이 카테고리의 다른 서버 19103개 중 0%보다 스타가 많아요
• 이 카테고리의 다른 서버 19103개 중 97%보다 최근에 레지스트리에 공개됐어요
• 기본 점검 결과가 이 카테고리의 다른 서버 19103개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

제작자의 README

npm run check

codex mcp add testsy --url "$(node -p "require('./config.json').app + '/mcp'")" --bearer-token-env-var QA_AI_API_KEY

claude --plugin-dir ./dist/claude

gemini extensions install ./dist/gemini

node bin/testsy.mjs version

steps: