Katalon True Platform MCP

io.github.katalon-studio由 GitHub 账号 katalon-studio 发布v1.0.0更新于 Oct 28, 2026

Katalon True Platform MCP: design tests, run with AI, upload reports, assess release readiness.

已验证Streamable HTTP可网页运行效率与工作流开发者工具

概览

AI 生成的概览

Katalon True Platform MCP 将助手连接到你的 Katalon 工作区，用于设计测试用例、用 AI 执行测试、上传报告并判断发布是否就绪。

可以做什么
  • 列出项目与仓库、读取需求并追踪覆盖率
  • 创建、更新并关联测试用例，管理套件与文件夹
  • 创建手动运行、启动 Run with AI 会话、轮询并读取结果
  • 上传或校验 Katalon Studio、JUnit XML 与 Playwright 报告
  • 获取质量指标并提交关联 ALM 的缺陷
  • 评估发布就绪度并生成面向管理层的总结
适用场景
适合已在使用 Katalon 的测试团队，让编码助手在真实工作区中把需求转成用例、执行套件、分析失败原因，并回答某个版本能否发布。README 还附带十九个技能，可按角色和阶段路由请求。
运行要求
需要 platform.katalon.io（或自有 Katalon 子域名）的远程 streamable HTTP 端点。首次连接时通过浏览器 OAuth 登录并选择工作区，无需粘贴令牌或密钥。部分客户端需借助 mcp-remote 包装器；可选技能需另行通过 skills CLI 或插件市场安装。
安装前请注意
仅支持浏览器 OAuth 认证；切勿在对话中粘贴或提交密码、API 令牌、Cookie、JWT、MFA 验证码或 OAuth 回调地址。助手可在工作区中创建和更新测试用例、套件、运行与缺陷，会写入真实项目数据。平台操作会将工作区数据发送给 Katalon，受其隐私政策约束。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Katalon True Platform MCP，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.katalon-studio%2Ftestops-mcp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "mcpServers": {
    "katalon-true-platform": {
      "type": "http",
      "url": "https://platform.katalon.io/mcp"
    }
  }
}

README

Ask your coding agent to read a requirement, design the test cases, run them with AI, upload the reports, and tell you whether the release is safe to ship. The skills do the platform work through the Katalon MCP, so the agent operates your real project instead of guessing at it.

[Example agent session: install the skills, analyze requirement CEL-6, design and import cases, run with AI, upload the report, and get a ship decision]

An example session. Your requirement keys, suites, and verdicts come from your own workspace.

Quickstart

1. Install the skills. The skills CLI detects the agent you already run (70+ supported) and drops the skills into its native directory.

bash
npx skills add katalon-labs/true-skills

2. Point it at your Katalon workspace. Add the MCP server to your agent's config file (the install section says which file yours is):

json
{  "mcpServers": {    "katalon-prod-mcp": {      "type": "http",      "url": "https://platform.katalon.io/mcp"    }  }}

First connect opens a browser OAuth flow and lets you pick your workspace. Nothing to fill in, no tokens to paste, no keys to store.

3. Ask for something real.

text
Set up Katalon MCP and verify my projects.Create manual tests from requirement CEL-6 and link them.Which requirements in this sprint have no test coverage?Run that suite with AI and summarize what broke.Generate a Playwright script from test case TC-1042.Upload my Playwright report to Katalon and verify the run.Is release 3.2 safe to ship?

Or hand over the whole chain: "Analyze CEL-6, design and import the cases, build a suite, run it with AI, and tell me if we can ship."

Start where you are

Four jobs. Say the situation in your own words and the agent picks the skill.

You are aYou sayIt starts at
Manual tester
QA analyst, test analyst		I just got requirement CEL-6 and need cases · Run this suite with AI and tell me what broke · Is this failure the app or my testcreate-test-cases → test-data → execute-test → analyze-failures
Unscripted session? exploratory-charter.
Automation tester
SDET, automation engineer		Turn TC-1042 into a Playwright spec · Get my run into the platform · Our suite went flaky this monthtest-case-to-playwright → playwright-execute → test-maintenance
Test lead
QA lead, QE lead		What should we test first this sprint · Is this suite ready for the pipeline · Which requirements have no coveragetest-plan → test-estimation → test-review → test-management
Test manager
QA manager, head of quality		Can we ship 3.2 · How long will this take and with how many people · Build the summary I present upwardrelease-analyze → test-estimation → test-reporting

Not connected yet? Start at platform-setup, which everyone runs once.

Not sure which one you are, or the request spans several? Ask true-platform-testing and it routes by role and by stage. The full map from intent to skill, including what to fall back to for the parts not built yet, is in lifecycle-map.md.

The skills

Nineteen skills, one folder each under skills/. The agent picks the right one from its description, so you rarely name a skill yourself.

SkillStageWhat it does
platform-setupsetupInstalls and verifies the Katalon MCP, and diagnoses auth or access failures. Start here.
get-startedsetupFirst-run onboarding after the connection is installed. Confirms the signed-in account, picks the default project in at most two questions, and opens the Katalon home view. The ChatGPT plugin runs it on install.
test-plan1 planTurns quality goals into scope, ranks the work by requirement coverage and risk, and builds the folder and suite structure that acts as the executable plan.
test-estimation1 planSizes a test cycle from scope, risk, and historical execution data, resources it across the manual and automated lanes, and states the uncertainty instead of inventing precision.
create-test-cases2 designReads a requirement or free text, designs atomic manual cases with ISTQB techniques as reference, skips duplicates, imports only what is missing, and links each case back to the requirement.
test-data2 designDesigns the data a case runs on, decides what must exist before a run, keeps literals out of the step text, and resets state afterwards so the next run starts clean.
exploratory-charter2 designWrites a charter with a mission, areas, oracles, and a timebox, runs the session, and turns what was found into defects and scripted cases.
test-management3 manageOrganizes folders and suites, finds assets at scale, and produces a requirement to case to suite traceability report with coverage percentage and orphans.
test-review4 reviewReviews coverage, case quality, and flakiness before anything enters the pipeline, and returns Approve, Approve with fixes, or Reject plus the specific weak cases.
execute-test5 executeRuns a case, a list, or a suite as a manual run, a Run with AI session, or scheduled automation, then reports pass, fail, and blocked.
upload-report5 executeRuns automation and uploads or verifies Katalon Studio/KRE, JUnit XML, and Playwright reports on the platform.
test-case-to-playwright5 executeConverts manual cases into Playwright TypeScript with Page Object Model and fixtures.
test-case-to-katalon-studio5 executeConverts manual cases into Katalon Studio test cases and Groovy scripts, keeping the .tc and .ts pair GUID-consistent.
playwright-execute5 executeRuns Playwright specs, ships the report with @katalon/playwright-reporter, and verifies the run landed.
analyze-failures6 analyzeSorts failures into product defect, automation defect, and environment noise, clusters them by signature, and files ALM defects for the real bugs.
release-analyze6 analyzeReads coverage, stability, and defect data to return Ready, Ready with risk, or Not ready, with the reasons attached.
test-reporting6 analyzeTurns platform quality data into the few metrics that answer a stakeholder question, trended across releases, as a summary a manager can present upward.
test-maintenance7 maintainFinds flaky and broken cases from stability history, repairs or regenerates them, and hands the refreshed gap list back to planning.
true-platform-testingallThe router and end to end runner. Routes any request to the right stage, or drives the full chain from requirement to ship decision.

Multi-skill playbooks live in combination-recipes.md. Copy-paste prompts and cross-model notes are in prompt-recipes.md.

The lifecycle

Seven stages, each owned by a skill. The loop closes when maintenance feeds its gap list back into the plan.

[The seven-stage testing lifecycle and the skill that owns each stage, with the maintenance gap list feeding back into planning]

platform-setup sits before all seven, connecting the MCP. Every skill states which Katalon MCP tools it uses and where the platform stops. Full stage map: lifecycle-map.md. Every tool in one line each: mcp-tool-index.md. A self-contained visual for humans: docs/lifecycle.html.

Where the boundary is

Each skill names its limits up front so the agent does not promise work the platform cannot do.

Through the MCP: list projects and repositories, read requirements, create and update and link test cases, manage suites and folders, create manual runs, start Run with AI, poll AI sessions, read results, fetch quality metrics, and file ALM-linked defects.

Not through the MCP: creating requirements, creating a formal Test Plan entity, guaranteeing an AI run finishes, or inspecting the live app UI without a browser tool. A named suite plus a release or sprint association stands in for the Test Plan entity.

Some work is a product surface rather than an API call: object capture and resilience design in Studio, custom fields and Git config and governance in the TestOps UI, self-healing and Time Capsule and TrueTest regeneration, and rerun, terminate, and Live Monitor. The full list is in unavailable-capabilities.md.

Install

Every path needs the Katalon MCP configured.

Any agent via the skills CLI
bash
npx skills add katalon-labs/true-skills                          # all skills, this projectnpx skills add katalon-labs/true-skills --skill platform-setup   # just onenpx skills add katalon-labs/true-skills -g                       # user-global, every agentnpx skills update                                                # pull the latest

The CLI installs skill files only. Configure the MCP yourself with the snippet below, or use the Claude Code and Codex plugin paths, which bundle it.

Any agent via the Agent Plugins standard

This repository conforms to the Agent Plugins specification 1.0.0: plugin.json + skills/ + mcp.json at the repo root form a portable plugin any conformant client can load directly, and plugins/katalon-true-platform/ ships the same contract as a standalone plugin directory. Skills follow the Agent Skills format. Point your standard-aware client at either directory; mcp.json already declares the canonical endpoint as a streamable-http server, so there is nothing to fill in.

Claude Code plugin marketplace
bash
claude plugin marketplace add katalon-labs/true-skillsclaude plugin install katalon-true-platform@katalon-true-platform-marketplace

Developing against a checkout:

bash
claude --plugin-dir plugins/katalon-true-platform

The plugin ships the skills and an .mcp.json. If your setup does not auto-load the bundled MCP, add it manually.

Codex plugin marketplace
bash
codex plugin marketplace add katalon-labs/true-skills

Open Plugins in Codex and install Katalon True Platform. Set your subdomain in the plugin's .mcp.json.

GitHub Copilot agent skills + MCP
bash
mkdir -p .github .vscode \  && cp -R <checkout>/.github/skills .github/ \  && cp -R <checkout>/.github/prompts .github/ \  && cp <checkout>/.github/copilot-instructions.md .github/ \  && cp <checkout>/.github/mcp.json .github/ \  && cp <checkout>/.vscode/mcp.json .vscode/
  • VS Code (agent mode) - skills in .github/skills/ load automatically; prompt files stay available as /platform-setup etc. Start the katalon-prod-mcp server when VS Code offers it: it signs you in through the browser OAuth flow and you pick your workspace. Nothing to configure, no token pasting.
  • Copilot CLI - the same skills are auto-discovered (/skills list to see them). The MCP server auto-loads from .github/mcp.json with no edits; or register it interactively with /mcp add (type http, same URL). The CLI does not read .vscode/mcp.json.
  • Copilot coding agent & code review - read .github/skills/ from your repository automatically. Neither surface supports OAuth remote MCP servers yet, so keep Katalon platform operations in VS Code or the CLI for now.
Cursor project rules
bash
cp -R <checkout>/.cursor .cursor

Rules in .cursor/rules/*.mdc load by description when relevant. MCP config lives in .cursor/mcp.json.

Kiro steering docs
bash
cp -R <checkout>/.kiro .kiro

Steering docs use manual inclusion, so reference one in chat with #true-platform-testing. MCP config lives in .kiro/settings/mcp.json.

Kiro Crew app

Kiro Crew installs this as an app — apps/katalon-testing-skills/ carries an app.json manifest that registers all 19 skills and the katalon-prod-mcp server on install. From the dashboard's Apps page, install from the local path, or submit the repo to the Kiro Crew app registry so it appears under Apps → Discover. First MCP connect opens the browser OAuth flow and a workspace picker.

bash
# local/developer install: point Kiro Crew at the app directoryapps/katalon-testing-skills/

Details in apps/katalon-testing-skills/README.md.

Windsurf rules
bash
cp -R <checkout>/.windsurf .windsurf

Rules in .windsurf/rules/*.md trigger on their description. Add the MCP under Settings → MCP, or in ~/.codeium/windsurf/mcp_config.json.

Cline project rules
bash
cp -R <checkout>/.clinerules .clinerules

Cline loads every file in .clinerules/. Add the MCP through its MCP Servers panel.

Continue rules and MCP block
bash
cp -R <checkout>/.continue .continue

Rules live in .continue/rules/*.md, the MCP block in .continue/mcpServers/katalon.yaml.

Anything else via AGENTS.md

Point your agent at AGENTS.md. It indexes every skill and tells the agent to open skills/<name>/SKILL.md. Use the root .mcp.json for the server config.

Connect the Katalon MCP

One endpoint serves every workspace: https://platform.katalon.io/mcp. Sign-in presents a workspace picker, so there is no subdomain to look up. The canonical shape lives in .mcp.json:

json
{  "mcpServers": {    "katalon-prod-mcp": {      "type": "http",      "url": "https://platform.katalon.io/mcp"    }  }}

Agents without native remote-MCP support (Kiro, Continue, Codex) use the mcp-remote wrapper against the same endpoint:

sh
npx -y mcp-remote https://platform.katalon.io/mcp --transport http-first
  1. Complete the browser OAuth flow that opens on first connect.
  2. Pick your workspace.
  3. Reload the agent if the tools do not show up.

On a dedicated Katalon domain, substitute https://<your-sub-domain>.katalon.io/mcp.

Auth is browser OAuth only. Never paste passwords, API tokens, cookies, JWTs, MFA codes, or OAuth callback URLs into chat, and never commit them. The skills enforce this.

How it is built

The skill bodies live once. Everything each agent needs is generated from them, so no adapter can drift.

text
  skills/                      13 SKILL.md files plus references/     |     |  node scripts/build-adapters.mjs      deterministic, checked in CI     v  Claude Code · Codex · Copilot · Cursor · Kiro · Windsurf · Cline · Continue · AGENTS.md     |     |  every adapter points at the same server     v  Katalon MCP  ->  requirements, test cases, suites, Run with AI, results, defects
text
skills/                              source of truth, 19 skillsscripts/build-adapters.mjs           generates every agent configplugins/katalon-true-platform/       Claude Code and Codex plugin      (generated).claude-plugin/  .agents/            plugin marketplaces               (generated).cursor/  .kiro/  .github/           Cursor, Kiro, Copilot             (generated).windsurf/  .clinerules/  .continue/ Windsurf, Cline, Continue         (generated)apps/katalon-testing-skills/         Kiro Crew app                     (generated).mcp.json  .vscode/mcp.json          MCP config                        (generated)AGENTS.md  llms.txt                  agent-readable index              (generated)

Contributing

Edit skills/ only. Everything else is generated. Then:

bash
node scripts/validate-skills.mjs    # skills/ matches scripts/skills.config.mjsnode scripts/build-adapters.mjs     # regenerate every agent config

The build is deterministic. Re-running it with no skill changes produces no diff, and CI rejects out-of-sync adapters. Details in CONTRIBUTING.md.

The ChatGPT plugin package has its own sources under chatgpt/ (the ChatGPT plugin.json, per-skill agents/openai.yaml overlays, the card tool map and the listing assets) and its own build, which stages an allowlisted copy in dist/chatgpt/ and refuses anything the OpenAI plugin directory rejects:

bash
python3 scripts/build-chatgpt-plugin.py      # dist/chatgpt/katalon-true-platform/ and the ZIPpython3 -m unittest discover -s tests        # one bad fixture per forbidden item

Listing copy, review cases and the submission checklist are in docs/chatgpt/.

Support

Privacy

The skills are plain markdown that runs inside the agent you already use. This repository collects nothing. Platform operations go to your own Katalon workspace over OAuth, and what Katalon does with that data is covered by the Katalon Privacy Policy.

License

MIT © Katalon. "Katalon" and "Katalon True Platform" are trademarks of Katalon, Inc.

来源：README.md，提交 334993f

工具

0
该服务器需要登录，因此 SourceWeft 无法在没有账号的情况下读取其工具，也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v1.0.0最新Sep 16, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分