Skip to main content

MCP Servers and Tools in StudioAssist

This document explains how MCP servers can be helpful, and shows you how to configure MCP servers and their tools in StudioAssist.

Understanding MCP servers​

An MCP server, or Model Context Protocol server, allows an LLM (Large Language Model) AI model to do more than just generate texts.

Think of MCP servers as a toolbox. When you prompt, they analyze the prompt, find the tools for your AI agent, and then tell it to use these tools for the job. For example, you can ask it to create and write test cases, update Jira tickets, and so much more, just through natural prompting.

Built-in vs. external MCP servers in Katalon Studio​

In StudioAssist, we provide 3 Katalon's built-in MCP servers. These servers can help you query Katalon's knowledge base, write/edit test cases in Katalon Studio, and interact with TestOps objects. See Katalon's built-in MCP servers for more details.

Katalon's built-in servers are included and enabled by default. You don't need to do anything further to use our built-in MCP servers.

We also support adding external MCP servers for StudioAssist's AI agent (see Adding external MCP Servers in StudioAssist below for more details). Adding these allows StudioAssist to integrate with these external tools and can help you accomplish more.

Supported transport methods for MCP servers​

Note
  • StudioAssist currently does not work with servers using STDIO as a transport method.
  • Starting version 10.4.0, Katalon Studio supports MCP servers that require authentication (e.g. Atlassian, Linear, Asana, Notion, Webflow... )

Currently, StudioAssist supports MCP servers with SSE or HTTP transport methods:

Transport methodExecution environmentUser typeInput requirement
SSE (HTTP with Server-Sent Event)On your own machine (local) or remote (online)Multiple users can access the MCP serverURL to an SSE endpoint
HTTP (Modern Streamable HTTP)On your own machine (local) or remote (online)Multiple users can access the MCP serversURL to an HTTP endpoint

Adding an external MCP Server​

To add an external MCP server, first click on the setup panel for MCP servers icon next to Agent Mode. This is the the MCP server settings, where you configure MCP servers, their tools, and more.

icon of Tool Settings config

Follow our interactive guide to add an MCP server:

  1. Click Add MCP Server. A dialogue Connect to a remote HTTP Server will open.
button for adding an MCP server
  1. Fill in these fields:

    1. Transport Type: either HTTP or SSE. Your MCP server provider should specify this. You can consider adding these remote MCP servers.
    2. Server URL: the MCP server's URL.
    3. Name: give your MCP server a name, no spaces or special characters. The name is used for Katalon's internal management system - there shouldn't be two servers with the same name.
    4. 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.
prompt with fields for adding an MCP server
  1. Click OK. The server loads for a while then expands to display its tool list.

If the MCP server you're adding requires authentication, like Atlassian's MCP server, an icon will display like so.

mcp server requiring authentication studioassist.png

You'll need to click on the server to expand it, and click Authorize. You'll be redirected to the server's authentication site - simply follow through. Once authorized successfully, you can go back to Katalon Studio and see the server along with its tool list.

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.

mcp server refresh authentication.png

Manage MCP servers and tools​

In the settings menu, you can:

  • (1) Search for an MCP tool

  • (2) Enable all/Disable all MCP tools in a server

  • (3) Enable/Disable an MCP tool: disabling a tool means the AI agent won't use the tool.

  • (4) Reload an MCP server: reload an MCP server to fetch its up-to-date tools.

  • (5) Connect/Disconnect an MCP server: StudioAssist keeps the server's information, but no longer maintains a connection to it.

  • (6) Remove: StudioAssist removes an MCP server and its tools from the list. This helps with de-cluttering - you can always add them back later if needed.

features and buttons for configuring MCP servers and tools
Was this page helpful?