platform-setup

Katalon Platform Setup

Use this skill for Katalon MCP installation, connection, and readiness checks. Do not use it for designing or running tests unless the setup check leads directly into create-test-cases, execute-test, or the larger true-platform-testing skill.

This skill is agent-neutral. The Katalon MCP server is the same for every agent (Claude Code, Codex, Copilot, Cursor, Kiro, Windsurf, and others); only the config file location and format differ per agent. For the exact per-agent config path and snippet, read the repository README.md install section.

Setup Boundary

Be explicit about what can be verified from the current environment:

• Available through Katalon MCP once connected: project/repository discovery, requirement reads, test case/suite operations, manual runs, AI sessions, automated scheduling, results, metrics, and ALM-linked defects.
• Not directly available through Katalon MCP: create requirements, create a formal Test Plan entity, inspect live AUT pages, or guarantee AI execution completion.
• If no Katalon MCP tools are exposed in the current session, do not claim the platform is connected.

Read references/capability-boundaries.md when explaining available operations.

Required Setup Inputs

For setup requests, collect the minimum routing and authentication choices before writing or testing MCP config:

1. Resolve the Katalon MCP endpoint:
   • Default to the canonical endpoint https://platform.katalon.io/mcp. It serves every workspace and presents a picker after sign-in, so do not ask for a subdomain unless something below applies.
   • If the installed config still contains the <your.sub.domain> placeholder, replace it with the canonical endpoint rather than asking the user to fill it in.
   • Only ask for a domain when the user names a dedicated Katalon domain, or when the local config mentions more than one Katalon domain - then list the candidates and ask which one they want.
   • Normalize a bare subdomain to https://<sub>.katalon.io/mcp.
2. Ask how the user wants to authenticate when auth is required:
   • Browser OAuth flow with an agent restart/reload after login.
   • CLI/local mcp-remote login bootstrap.
   • Login email/account label only for account selection.
3. Never ask for passwords, API tokens, cookies, JWTs, MFA codes, or OAuth callback URLs in chat. If the user offers "login information", accept only non-secret routing details such as login email, organization, domain, project name, or repository/Test Project name.
4. After authentication succeeds and Katalon tools are available, call list_projects. If more than one project is returned, list the projects and ask which project to use before calling repository-specific tools.
5. After project selection, call list_repositories with the selected project_id. If more than one repository/Test Project is returned and none is clearly implied by the user's request, list the repositories and ask which one to use.