Setting up Azure DevOps MCP server for StudioAssist

This document explains how to set up a proxy Azure DevOps MCP server to integrate with Katalon Studio's StudioAssist agent.

requirements

• Node.js (version 14 or higher) - Download here. npx is included automatically with Node.js
• Python and either UV (installation guide here) or pipx (installation guide here) to install mcp-proxy
• Access to an Azure DevOps organization

Set up and connect Azure DevOps MCP server to StudioAssist

Step summary:

1. Install mcp-proxy.
2. Install required packages for Azure DevOps MCP server globally or locally.
3. Create and setup a Personal Access Token (PAT) to authenticate with Azure DevOps.
4. Host your Azure DevOps MCP server.
5. Connect to the server in Katalon's StudioAssist MCP server settings.

Refer to these steps below for more details.

Install mcp-proxy

Run the following command in your terminal to install mcp-proxy. You can choose either UV:

uv tool install mcp-proxy

or pipx:

pipx install mcp-proxy

Install required packages for Azure DevOps MCP server

Run the following command in your terminal to install required packages for Azure DevOps MCP server.

You can install the required packages globally:

npm install -g mcp-proxy @azure-devops/mcp

Or install for your project only (local install):

npm install mcp-proxy @azure-devops/mcp

Create and setup a Personal Access Token (PAT)

You need a Personal Access Token (PAT) to authenticate with Azure DevOps. Follow these steps:

1. Go to Azure DevOps: <https://dev.azure.com/{YourOrganization}>
2. Click on User Settings (top right) > Personal Access Tokens.

3. Click + New Token.
4. Configure:
   • Name: Give it a descriptive name (e.g., "MCP Bridge")
   • Organization: Select your organization (e.g., "Katalon")
   • Expiration: Set expiration date
   • Scopes: Select the permissions you need:
     • Work Items: Read & Write
     • Code: Read
     • Build: Read
     • Or select Full Access for all permissions

5. Click Create

6. Copy the token - you won't be able to see it again.

7. Set up the PAT as an environment variable:

   For Windows (PowerShell):

   $env:AZURE_DEVOPS_PAT = "your-pat-token-here"

   For Windows (CMD):

   set AZURE_DEVOPS_PAT=your-pat-token-here

   For macOS/Linux:

   export AZURE_DEVOPS_PAT="your-pat-token-here"

   For macOS/Linux (Permanent setup):

   Add to your ~/.zshrc or ~/.bashrc:

   echo 'export AZURE_DEVOPS_PAT="your-pat-token-here"' >> ~/.zshrc source ~/.zshrc

Host your Azure DevOps MCP Bridge server

In your terminal, run the MCP proxy server with your Azure DevOps organization:

mcp-proxy --port 3000 --host 127.0.0.1 --stateless --allow-origin '*' npx @azure-devops/mcp "Katalon"

Replace "Katalon" with your Azure DevOps organization name.

Parameter	Description
--port 3000	Server port (customize as needed)
--host 127.0.0.1	Server host (localhost)
--stateless	Enable stateless mode
--allow-origin '*'	Allow all CORS origins (use specific origin in production)
"Katalon"	Your Azure DevOps organization name

Connect to the server in StudioAssist

Once the server is running, add it to StudioAssist:

1. Server URL: <http://127.0.0.1:3000/mcp>
2. TransportType: HTTP

Result

You can see the tool list in the added MCP server for Azure DevOps:

Troubleshoot

• If you encounter "Port already in use" error, it's likely you're already using port 3000 for another task. Change --port 3000 to another port (e.g., --port 3001).

• If you encounter "Connection fails" error, double check to ensure mcp-proxy is running in the terminal.

• If you encounter CORS errors, double-check to make sure --allow-origin "*" is in the command