Add an external MCP server in Katalon AI Assistant
This document explains how to connect to an external MCP server in Katalon AI Assistant.
Supported MCP servers​
- Starting version 10.4.0, Katalon Studio supports MCP servers that require authentication (e.g. Atlassian, Linear, Asana, Notion, Webflow... )
Katalon Studio provides 3 built-in MCP servers that help you query Katalon's knowledge base, write/edit test cases in Katalon Studio, and interact with TestOps objects.
For external MCP servers, we support the followings:
| Transport method | Execution environment | User type | Requirement |
|---|---|---|---|
| SSE (HTTP with Server-Sent Event) | Local or remote | Multiple users can access the MCP server | URL to the SSE endpoint |
| HTTP (Modern Streamable HTTP) | Local or remote | Multiple users can access the MCP servers | URL to the HTTP endpoint |
| STDIO | Local | Single user on the local machine running the MCP server | Server command and arguments |
Starting in Katalon Studio 11.1.0, STDIO MCP servers are supported directly in Katalon AI Assistant, so you no longer need to use MCP proxy for these servers. If you are using an earlier version of Katalon Studio, set up MCP proxy as a workaround. Servers hosted via this method can be treated as SSE/HTTP types to connect to Katalon AI Assistant. Learn more at Set up MCP proxy for STDIO MCP servers below.
Add an external MCP Server​
Follow these steps to add an MCP server:
- Click the Settings icon, then select Agent Mode settings.
- Click Add MCP Server:
- Fill in these fields:
- Transport Type:
HTTPorSSE. Your MCP server provider should specify this. Check out our external MCP servers for common servers you could add.- Server URL (for
HTTPandSSE): the MCP server's URL.
- Server URL (for
- **Command and arguments (for
STDIO): the command used to start the MCP server and its arguments. The syntax should be:
{
"command": "npx",
"args": ["-y", "chrome-devtools-mcp@latest"]
}
- Name: this name should contain no spaces or special characters (for example, "atlassian-mcp-server"). This name should be unique for the server list, and kept as short as possible (see limitation notes below).
- Title (Optional): the title is the display name of the server. You can have servers with the same name, but we highly recommend giving unique titles to servers.
- Click OK. The server is now added. You can expand to view its tool list.
-
AI providers (OpenAI, Azure OpenAI, Gemini, and AWS Bedrock) enforce a limitation of 64 characters on the combined length of the MCP Server name and tool name (
{server_name}_ _ _{tool_name}). Exceeding this limit may cause Katalon AI Assistant Agent mode to fail when calling these APIs. -
To prevent this, try to keep the MCP Server name (or the tool's name if you host your own server) short, or temporarily disable the tool and revert back later. The Title of the MCP server is not affected by this limit, and can remain as long as needed.
-
Some AI service providers also enforce a limit of
128MCP tools per request. Starting in Katalon Studio 11.3.0, Katalon AI Assistant can automatically select the tools most relevant to your prompt before an Agent mode request. This helps reduce the chance of hitting the tool limit when you add external MCP servers. If the error still occurs, disable tools or servers you do not need.
Authentication for MCP servers​
Some servers (like Atlassian's) require authentication:
To authenticate, click Authorize. You'll be redirected to the server's authentication site - simply follow through.
When a server's token expires, Katalon Studio reminds you to re-grant authorization.
Simply click Authorize, and follow the steps above again. If it doesn't load properly due to connection issues, you can reload it with the Reload button.
External MCP servers to add to Katalon AI Assistant​
You can easily add any of the available open MCP servers from the remote MCP servers list.
See below some of the OAuth MCP servers we currently support, grouped by purposes.
Project management​
Integrate with these MCP servers to enable Katalon AI Assistant to:
- Create and update ticket descriptions automatically
- Read requirements, documentation, and test plans as context for test generation
- Log and create bugs when tests fail
| Server | Transport type | Server URL/Command and Arguments |
|---|---|---|
| Atlassian | HTTP | https://mcp.atlassian.com/v1/mcp |
| Notion | HTTP | https://mcp.notion.com/mcp |
SSE | https://mcp.notion.com/sse | |
| Linear | HTTP | https://mcp.linear.app/mcp |
| Asana | SSE | https://mcp.asana.com/sse |
| Azure DevOps MCP (ADO) | HTTP when using mcp-proxy | See further setup instructions at Setting up MCP server for Azure DevOps. |
STDIO (KS 11.1.0+) | { "command": "npx", "args": ["-y", "@azure-devops/mcp@next", "Katalon"] } | |
| GitHub | HTTP | https://api.githubcopilot.com/mcp/ with PAT |
STDIO | { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-github"], "env": { "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_xxxxxxxxxxxx" } } | |
| GitLab | STDIO (KS 11.1.0+) | Requires Node.js 18+ (so npx works) and a GitLab personal access token with the api scope.{ "command": "npx", "args": ["-y", "@modelcontextprotocol/server-gitlab"], "env": { "PATH": "/opt/homebrew/bin:/usr/local/bin:/usr/bin:/bin", "GITLAB_PERSONAL_ACCESS_TOKEN": "<your-token>", "GITLAB_API_URL": "https://gitlab.com/api/v4" } }Note about PATH: On macOS, keep the PATH property. Run echo $PATH in Terminal, then copy the result and use it as the PATH value. On Windows, remove the entire "PATH": "...", property from the configuration. |
| Google Drive | STDIO (KS 11.1.0+) | { "command": "npx", "args": ["-y", "@piotr-agier/google-drive-mcp"] }. Requires GCP OAuth setup — see further setup instructions at Set up Google Drive MCP server. |
See how we use Katalon AI Assistant to create a test case from requirements, with Atlassian MCP server: