AI 어시스턴트가 Testomat.io Public API와 상호작용하여 테스트, 스위트, 실행, 요구사항 및 이슈 연결을 관리할 수 있도록 지원합니다.
다른 이름 testomatio/mcp, @testomatio/mcp
- 스타
- 8
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- —
- 마지막 커밋
- 2026년 11월 13일
- 라이선스
- —
Testomat.io MCP란?
AI 어시스턴트가 Testomat.io Public API와 상호작용하여 테스트, 스위트, 실행, 요구사항 및 이슈 연결을 관리할 수 있도록 지원합니다.
프로젝트 README에서 생성된 요약
Testomat.io MCP server 정보
이 MCP server를 사용하면 AI 어시스턴트를 통해 테스트 스위트, 실행 및 요구사항을 관리할 수 있습니다. Claude, Cursor, OpenCode와 같은 도구를 Testomat.io Public API v2에 연결하여 사용자가 자연어로 품질 보증(QA) 작업을 수행할 수 있게 합니다. 이 server는 로컬 설치 시 stdio를 통해 작동하며, Cloudflare Worker에서는 호스팅된 HTTP 전송 방식을 통해 작동합니다.
개발자는 CLI 스타일의 도구 구조를 사용하여 테스트, 스위트, 실행, 플랜, 요구사항을 포함한 다양한 엔티티와 상호작용할 수 있습니다. 각 도구는 list, get, create, update, delete와 같은 명령 인수를 사용합니다. 이 server는 첨부 파일 및 요구사항을 위한 로컬 파일 경로 업로드, 리소스에 이슈 연결, 실행 상태 전환 관리를 지원합니다. 긴 세션 동안 성능을 최적화하려면 core 또는 read와 같은 다양한 도구 표면 프로필을 선택하여 노출되는 스키마를 제한할 수 있습니다.
server를 설정하려면 환경 변수 또는 커맨드 라인 플래그를 통해 제공되는 프로젝트 API 토큰과 프로젝트 ID가 필요합니다. 또한 다양한 환경을 위한 커스텀 base URL을 지원하며, Testomat.io 히스토리에서 변경 사항을 그룹화하는 자동 세션 관리 기능을 포함합니다.
활용 사례
- 1대량 테스트 관리마크다운 형식의 문자열을 제공하여 여러 테스트를 한 번에 생성하거나 업데이트합니다.
- 2테스트 실행 라이프사이클 제어특정 상태 이벤트를 사용하여 테스트 실행 상태를 finish 또는 rerun으로 전환합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Testomat.io MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Testomat.io MCP 설치
$ claude mcp add mcp -- npx -y @testomatio/mcpCursor에 Testomat.io MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@testomatio/mcp"
]
}
}
}VS Code에 Testomat.io MCP 설치
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@testomatio/mcp"
]
}
}
}VS Code CLI에 Testomat.io MCP 설치
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@testomatio/mcp"]}'Claude Desktop에 Testomat.io MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@testomatio/mcp"
]
}
}
}Codex에 Testomat.io MCP 설치
$ codex mcp add mcp -- npx -y @testomatio/mcpCodex config.toml에 Testomat.io MCP 설치
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@testomatio/mcp"]
Gemini CLI에 Testomat.io MCP 설치
$ gemini mcp add -s user mcp npx -- -y @testomatio/mcpGemini settings.json에 Testomat.io MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@testomatio/mcp"
]
}
}
}구성
NODE_EXTRA_CA_CERTSNODE_OPTIONSTESTOMATIO_BASE_URLTESTOMATIO_PROJECT_IDTESTOMATIO_PROJECT_TOKEN
| 이름 | 설명 | 유형 |
|---|---|---|
| NODE_EXTRA_CA_CERTS | — | |
| NODE_OPTIONS | — | |
| TESTOMATIO_BASE_URL | — | |
| TESTOMATIO_PROJECT_ID | — | |
| TESTOMATIO_PROJECT_TOKEN | — |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능testomatio/mcp is public and reachablegithub.com/testomatio/mcp ↗통과
- 패키지가 이 저장소를 소스로 명시@testomatio/mcp names testomatio/mcp as sourcenpmjs.com/package/@testomatio/mcp ↗통과
- 빌드 출처(Sigstore 증명)Sigstore attestation for @testomatio/mcpnpmjs.com/package/@testomatio/mcp/v/3.2.0#provenance ↗통과
- 오픈 소스 라이선스 (OSI)No license결함 발견
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-13github.com/testomatio/mcp ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음No popular package one edit away from @testomatio/mcp통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답검사되지 않음
README
GitHub에서 보기Testomat.io MCP Server
Model Context Protocol (MCP) server that enables AI assistants (Claude, Cursor, OpenCode, etc.) to interact with Testomat.io Public API v2.
Features
- One CLI-style tool per entity -
tests,suites,runs,testruns,plans,rungroups,steps,snippets,labels,requirements,branches,tags,milestones,issues; each takes acommandargument (list,get,create,update,delete, plus scopedissues_*/attachments_*/sharecommands where applicable) and flat command params - Project Information - fetch project configuration, metadata, features, and CI profiles
- Issue Linking - link/unlink issues to any resource (
issues_*commands on each entity, plus the globalissuestool) - Attachments -
attachments_*commands on tests, suites, and testruns; upload sends a local file path as multipart fieldfiles - Requirements - including file uploads from local file paths
- API Compatibility - automatic handling of payload format differences (flat vs wrapped)
- Automatic API Sessions - groups MCP changes in Testomat.io history using API sessions
- Run Management - status transitions via
status_eventparameter - TQL-Only Search -
tests/runswithcommand: "list"usetqlas the single search/filter input - Built-In TQL Reference - TQL parameters include the exact field whitelist and examples;
tql_helpprovides syntax details on demand - Tool Surface Profiles - expose only the tools a session needs via
--tools full|core|read(defaultfull); cuts the per-call schema cost for long agentic sessions
Quick Start
Installation
npm install -g @testomatio/mcp@latest
Need enterprise analytics tools? Install @testomatio/mcp-enterprise@latest instead. Details are in the Enterprise Analytics section below.
Configuration
Required credentials:
TESTOMATIO_PROJECT_TOKEN- Your project API tokenTESTOMATIO_PROJECT_ID- Your project ID
Run server:
npx testomatio-mcp --token <PROJECT_TOKEN> --project <PROJECT_ID>
Or with environment variables:
export TESTOMATIO_PROJECT_TOKEN=<PROJECT_TOKEN>
export TESTOMATIO_PROJECT_ID=<PROJECT_ID>
npx testomatio-mcp
A bare hostname is expanded to https://<host>. For full control use
--base-url / TESTOMATIO_BASE_URL, which takes precedence over the host option
Optional: tool surface profile
By default the server exposes all tools. For long, token-sensitive sessions you can expose a smaller set with --tools:
npx testomatio-mcp --token <PROJECT_TOKEN> --project <PROJECT_ID> --tools core
| Profile | What's exposed |
|---|---|
full (default) |
Everything |
core |
Core entities with all commands (excludes the steps, snippets, labels, rungroups tools) |
read |
Core entities restricted to read-only commands (list, get, search, issues_list, attachments_list) |
Values are case-insensitive; an unknown value prevents the server from starting. Set the profile at launch with the flag or the TESTOMATIO_TOOLS environment variable — it can't be changed mid-session. The CLI flag takes precedence when both are set.
Usage with AI Assistants
Cursor IDE
Add this config to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for global access:
{
"mcpServers": {
"testomatio": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@testomatio/mcp@latest",
"--token",
"<TOKEN>",
"--project",
"<PROJECT_ID>"
],
"env": {
"TESTOMATIO_BASE_URL": "https://app.testomat.io"
}
}
}
}
Claude Desktop
Add this config to:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"testomatio": {
"command": "npx",
"args": [
"-y",
"@testomatio/mcp@latest",
"--token",
"<TOKEN>",
"--project",
"<PROJECT_ID>"
],
"env": {
"TESTOMATIO_BASE_URL": "https://app.testomat.io"
}
}
}
}
OpenCode
Add this config to opencode.json in your project root, or to ~/.config/opencode/opencode.json for global access:
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"testomat": {
"type": "local",
"command": [
"npx",
"-y",
"@testomatio/mcp@latest",
"--token",
"<TOKEN>",
"--project",
"<PROJECT_ID>"
],
"enabled": true,
"environment": {
"TESTOMATIO_BASE_URL": "https://app.testomat.io"
}
}
}
}
HTTP Transport
Besides stdio, the server runs over Streamable HTTP on a Cloudflare Worker hosted by Testomat.io. The project is part of the URL, so every tool signature stays the same:
https://mcp.testomat.io/mcp/<project_id>
Point an MCP client at that URL with a project token:
{
"mcpServers": {
"testomatio": {
"url": "https://mcp.testomat.io/mcp/<PROJECT_ID>",
"headers": {
"Authorization": "Bearer <PROJECT_TOKEN>"
}
}
}
}
Web connectors such as claude.ai have nowhere to put a static token and instead run
OAuth 2.1 with PKCE and Dynamic Client Registration against the same URL. Tokens
starting with testomat_ or tstmt_ always bypass OAuth and are passed straight
through, so IDE clients and CI keep working.
The endpoint is POST only; GET returns 405, because the server never initiates
traffic. Testing with curl requires both media types in Accept:
curl -sS https://mcp.testomat.io/mcp/<PROJECT_ID> \
-H "Authorization: Bearer <PROJECT_TOKEN>" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
Self-hosted installations keep using stdio.
Quick Examples
Every entity tool works like a CLI: pass command plus the params that command needs. Each param description in the tool schema lists the commands it applies to.
List tests:
{
"name": "tests",
"arguments": { "command": "list", "page": 1, "per_page": 50, "tql": "priority == 'high'" }
}
Create test:
{
"name": "tests",
"arguments": {
"command": "create",
"title": "User login test",
"suite_id": "123",
"priority": "high"
}
}
Create run:
{
"name": "runs",
"arguments": {
"command": "create",
"title": "Smoke tests",
"kind": "automated",
"env": "production"
}
}
Finish run:
{
"name": "runs",
"arguments": {
"command": "update",
"run_id": "456",
"status_event": "finish"
}
}
Upload attachment to a test:
{
"name": "tests",
"arguments": {
"command": "attachments_upload",
"test_id": "123",
"file_path": "/path/to/screenshot.png"
}
}
Bulk create/update tests from markdown:
{
"name": "tests",
"arguments": {
"command": "bulk_upsert",
"markdown": "<!-- suite\nid: @S380c64db\n-->\n# Login Functionality\n<!-- test\nid: @T12345678\npriority: high\n-->\n# Successful Login\n<!-- test -->\n# Failed Login"
}
}
Tests with an id: @T... are updated, tests without one are created; suites are resolved by id: @S... or title and created when missing. Up to 100 tests per call. See docs/tools.md for the full semantics.
Documentation
Complete tool reference: docs/tools.md
Project Structure
src/
|- config/ # Config loading, defaults
|- core/ # Errors, logger
|- api/ # HTTP client, Testomat.io API client
|- mcp/ # MCP server, tools, registry
| |- definitions/ # Tool definitions by entity
| |- configs/ # Registry generation configs
| `- registry/ # Tool handlers
`- cli/ # CLI bootstrap
Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
TESTOMATIO_PROJECT_TOKEN |
Yes* | - | Project token (preferred) |
TESTOMATIO_API_TOKEN |
Yes* | - | Alternative token |
TESTOMATIO_PROJECT_ID |
Yes | - | Project ID |
TESTOMATIO_HOST |
No | - | API host, e.g. beta.testomat.io |
TESTOMATIO_BASE_URL |
No | https://app.testomat.io |
API base URL, wins over TESTOMATIO_HOST |
TESTOMATIO_TOOLS |
No | full |
Tool profile: full, core, or read |
*Either TESTOMATIO_PROJECT_TOKEN or TESTOMATIO_API_TOKEN
Corporate TLS Certificates
If the MCP server runs behind a corporate proxy or TLS inspection, Node.js may reject Testomat.io HTTPS requests even when the same URL works in a browser. This usually means the company root certificate is trusted by the operating system, but not by Node.js.
Use Node.js system CA support:
NODE_OPTIONS=--use-system-ca testomatio-mcp --token <TOKEN> --project <PROJECT_ID>
For MCP clients, pass NODE_OPTIONS in the server environment:
{
"mcpServers": {
"testomatio": {
"command": "testomatio-mcp",
"args": ["--token", "<TOKEN>", "--project", "<PROJECT_ID>"],
"env": {
"NODE_OPTIONS": "--use-system-ca"
}
}
}
}
If your Node.js version does not support --use-system-ca, export the corporate root certificate to a PEM file and use Node.js extra CA support:
NODE_EXTRA_CA_CERTS=/path/to/company-root-ca.pem testomatio-mcp --token <TOKEN> --project <PROJECT_ID>
Important Notes
- CLI-style Tools - One tool per entity; all operations are the
commandargument (tests+command: "list"instead of the oldtests_list). Unknown commands return an error listing the valid ones - Run Status - Use
runswithcommand: "update"andstatus_eventfor transitions (finish, launch, rerun, etc.) - Search/Filter - No dedicated
/searchendpoints; filtering is done via thelistcommand (tqlfor tests and runs, OpenAPI-aligned filters for other entities) - Slim List Responses - List commands request compact API responses by default and omit heavy entity fields and null values. Pass
verbose: trueto return full objects, orfields: ["id", "title", "description"]to return only selected fields. Both options disable the backendslim=truerequest so heavy fields remain available when requested. - TQL - Use
tqlas the single search/filter input fortests/runswithcommand: "list" - TQL Syntax - For user-facing syntax details and more examples, see the official TQL docs: https://docs.testomat.io/advanced/tql/
- TQL Scope - TQL parameter descriptions keep the documented field whitelist in-band; call
tql_helpfor syntax details and additional examples - Issue Linking - Scoped commands available on each entity:
command: "issues_link"/"issues_unlink" - Attachments - Scoped commands available on tests, suites, and testruns:
command: "attachments_list" | "attachments_upload" | "attachments_delete". Upload sends one local file path as multipart fieldfiles. - Enterprise Package - Analytics tools are intentionally exposed only by
@testomatio/mcp-enterprise, not by the standard@testomatio/mcppackage - API Sessions - The server automatically starts a Testomat.io session before the first
POST,PUT, orDELETErequest, sends the returned session hash asX-Session-Hashon later mutating requests, and stops the session when the MCP server shuts down.GETrequests do not start or use sessions.
Development
npm install
npm run start -- --token <TOKEN> --project <PROJECT_ID>
npm test
For local MCP development, point Claude Desktop to the checked-out entrypoint:
{
"mcpServers": {
"testomatio-local": {
"command": "node",
"args": ["/path/to/mcp/index.js", "--token", "<TOKEN>", "--project", "<PROJECT_ID>"]
}
}
}
Enterprise Analytics
Enterprise analytics is available only in the separate @testomatio/mcp-enterprise package.
Installation:
npm install -g @testomatio/mcp-enterprise@latest
Run:
testomatio-mcp-enterprise --token <PROJECT_TOKEN> --project <PROJECT_ID>
Included tools:
analytics_tests-GET /api/v2/{project_id}/analytics/tests/{kind}analytics_stats-GET /api/v2/{project_id}/analytics/stats/{kind}analytics_charts_list-GET /api/v2/{project_id}/analytics/chartsanalytics_charts_get-GET /api/v2/{project_id}/analytics/charts/{id}analytics_charts_results-GET /api/v2/{project_id}/analytics/charts/{id}/result
Analytics endpoints require the api_analytics subscription feature. Use q as the TQL filter parameter for analytics tools.
Example analytics_tests call:
{
"name": "analytics_tests",
"arguments": {
"kind": "flaky",
"q": "priority == 'high'",
"days": 30,
"page": 1,
"per_page": 20
}
}
Example analytics_stats call:
{
"name": "analytics_stats",
"arguments": {
"kind": "success-rate-by-date",
"q": "tag IN ['@smoke']",
"from": "2026-04-01",
"to": "2026-04-30"
}
}
analytics_charts_get returns a chart definition with its TQL queries; analytics_charts_results
returns per-query totals or the matching tests/runs of one query (by its zero-based number).
Example analytics_charts_results call:
{
"name": "analytics_charts_results",
"arguments": {
"chart_id": "abc123",
"number": 2,
"per_page": 50
}
}
Testomat.io MCP 질문
Testomat.io MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add mcp -- npx -y @testomatio/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Testomat.io MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Testomat.io MCP server를 어떻게 설치하나요?
npm install -g @testomatio/mcp@latest 명령어를 사용하여 npm으로 전역 설치할 수 있습니다.