Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirA Model Context Protocol (MCP) server for integrating Azure DevOps with Cursor IDE. This tool allows Claude AI in Cursor to interact with Azure DevOps, providing access to projects, work items, repositories, and pull requests.
azure_devops_test_plans - List all test plans for a projectazure_devops_test_plan - Get a test plan by IDazure_devops_test_suites - List all test suites for a test planazure_devops_test_suite - Get a test suite by IDazure_devops_test_cases - List all test cases for a test suitenpm install -g cursor-azure-devops-mcp
npm install cursor-azure-devops-mcp
The server can be configured using multiple sources, with the following priority:
.env fileYou can configure the server using command line arguments:
npx cursor-azure-devops-mcp --azure-org-url=https://dev.azure.com/your-organization --azure-token=your-token --azure-project=YourProject
Available options:
You can configure the server in your VSCode or Cursor IDE settings:
~/.vscode/settings.json or ~/.cursor/settings.json.vscode/settings.json or .cursor/settings.jsonExample settings:
{
"azureDevOps.organization": "your-organization",
"azureDevOps.token": "your-personal-access-token",
"azureDevOps.project": "YourProject",
"cursor-azure-devops-mcp": {
"port": 3000,
"logLevel": "info"
}
}
Create a .env file in your project root with the following variables:
AZURE_DEVOPS_ORG_URL=https://dev.azure.com/your-organization
AZURE_DEVOPS_TOKEN=your-personal-access-token
AZURE_DEVOPS_PROJECT=YourProject
PORT=3000
LOG_LEVEL=info
You can also copy the provided .env.example file:
cp .env.example .env
Then edit the file with your Azure DevOps credentials.
The easiest way to use this MCP server is with npx:
npx cursor-azure-devops-mcp
Cursor IDE supports two methods for connecting to MCP servers: Command mode and SSE mode.
The Command mode runs the MCP server as a process directly from Cursor. This is the most reliable method and should be your first choice:
Open Cursor IDE
Go to Settings > Features > MCP Servers
Click "Add New MCP Server"
Enter a name for your server (e.g., "Azure DevOps")
Select "command" from the dropdown
Enter the command to run the server:
cursor-azure-devops-mcp
If you haven't installed it globally, you can use npx:
npx cursor-azure-devops-mcp
Click "Add"
Important: When using Command mode, the server will automatically use your environment variables from your system or from a .env file in your current working directory. Make sure your .env file is properly set up with your Azure DevOps credentials.
Troubleshooting Command Mode:
If you encounter the error "server.setRequestHandler is not a function" or similar errors:
npm install -g cursor-azure-devops-mcp.env file is correctly set up with your Azure DevOps credentialsNote: SSE mode is more prone to connection issues. If you're experiencing problems, please use Command mode instead.
The SSE mode connects to an HTTP server with Server-Sent Events:
First, start the HTTP server with SSE support:
npm run sse-server
or
npx cursor-azure-devops-mcp-sse
This will start a server on port 3000 by default.
Open Cursor IDE
Go to Settings > Features > MCP Servers
Click "Add New MCP Server"
Enter a name for your server (e.g., "Azure DevOps SSE")
Select "sse" from the dropdown
Enter the SSE endpoint URL:
http://localhost:3000/sse
Click "Add"
If you're using Windows and experiencing issues with the command mode, try this format:
cmd /k npx cursor-azure-devops-mcp
{
"azure-devops": {
"command": "cmd",
"args": [
"/c",
"npx",
"cursor-azure-devops-mcp",
"--azure-org-url",
"https://your-organization.visualstudio.com",
"--azure-token",
"your-personal-access-token",
"--azure-project",
"your-project"
]
}
}
const { McpServer } = require('@modelcontextprotocol/sdk/server/mcp.js');
const { registerTools } = require('cursor-azure-devops-mcp');
const azureDevOpsService = require('cursor-azure-devops-mcp/lib/azure-devops-service');
// Create MCP server
const server = new McpServer({
name: 'cursor-azure-devops-mcp',
version: '1.0.0'
});
// Register Azure DevOps tools with the server
registerTools(server, azureDevOpsService);
// Connect to your transport of choice
// ...
The test management tools provide comprehensive access to Azure DevOps test plans, suites, and cases:
List all test plans in a project:
{
"project": "YourProject"
}
Get a specific test suite:
{
"project": "YourProject",
"testPlanId": 185735,
"testSuiteId": 186771
}
List test cases in a suite:
{
"project": "YourProject",
"testPlanId": 185735,
"testSuiteId": 186771
}
When working with test management tools, you should:
azure_devops_test_plansazure_devops_test_suitesazure_devops_test_casesThe response format includes truncation metadata when necessary:
{
"items": [...],
"totalCount": 100,
"isTruncated": true,
"truncatedCount": 80,
"message": "Response was truncated. Showing 20 of 100 items."
}
Azure DevOps Cursor IDE MCP server plugin
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Cursor Azure Devops roda localmente via stdio.
Última verificação: 2026-10-27. Azure DevOps Cursor IDE MCP server plugin