🔌 Compatible with Cline, Cursor, Claude Desktop, and any other MCP Clients!
Ares DevOps MCP is also compatible with any MCP client
The Model Context Protocol (MCP) is an open standard that enables AI systems to interact seamlessly with various data sources and tools, facilitating secure, two-way connections.
The Ares DevOps MCP server provides:
- Seamless interaction with Azure DevOps Git repositories
- Secure repository and branch management
- Efficient pull request creation and management
- Type-safe operations with TypeScript
- Pipeline automation and monitoring
Before you begin, ensure you have:
- Azure DevOps account with appropriate permissions
- Personal Access Token (PAT) with required scopes
- Claude Desktop or Cursor
- Node.js (v14 or higher)
- Git installed (only needed if using Git installation method)
npx -y ares-devops-mcp@latest
To install Ares DevOps MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @ares-devops/mcp --client claude
The easiest way to set up the Ares DevOps MCP server in Cline is through the marketplace with a single click:
- Open Cline in VS Code
- Click on the Cline icon in the sidebar
- Navigate to the "MCP Servers" tab (4 squares)
- Search "Ares DevOps" and click "install"
- When prompted, enter your Azure DevOps credentials
Alternatively, you can manually set up the Ares DevOps MCP server in Cline:
- Open the Cline MCP settings file:
# For macOS:
code ~/Library/Application\ Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
# For Windows:
code %APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\settings\cline_mcp_settings.json
- Add the Ares DevOps server configuration to the file:
{
"mcpServers": {
"ares-devops-mcp": {
"command": "npx",
"args": ["-y", "ares-devops-mcp@latest"],
"env": {
"AZURE_DEVOPS_ORG": "your-organization",
"AZURE_DEVOPS_PROJECT": "your-project",
"AZURE_DEVOPS_PAT": "your-pat-token"
},
"disabled": false,
"autoApprove": []
}
}
}
- Save the file and restart Cline if it's already running.
Note: Requires Cursor version 0.45.6 or higher
To set up the Ares DevOps MCP server in Cursor:
- Open Cursor Settings
- Navigate to Features > MCP Servers
- Click on the "+ Add New MCP Server" button
- Fill out the following information:
- Name: Enter a nickname for the server (e.g., "ares-devops-mcp")
- Type: Select "command" as the type
- Command: Enter the command to run the server:
env AZURE_DEVOPS_ORG=your-org AZURE_DEVOPS_PROJECT=your-project AZURE_DEVOPS_PAT=your-pat npx -y ares-devops-mcp@latest
Important: Replace the environment variables with your Azure DevOps credentials
# Create the config file if it doesn't exist
touch "$HOME/Library/Application Support/Claude/claude_desktop_config.json"
# Opens the config file in TextEdit
open -e "$HOME/Library/Application Support/Claude/claude_desktop_config.json"
code %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"ares-devops-mcp": {
"command": "npx",
"args": ["-y", "ares-devops-mcp@latest"],
"env": {
"AZURE_DEVOPS_ORG": "your-organization",
"AZURE_DEVOPS_PROJECT": "your-project",
"AZURE_DEVOPS_PAT": "your-pat-token"
}
}
}
}
Once the installation is complete, and the Claude desktop app is configured, you must completely close and re-open the Claude desktop app to see the ares-devops-mcp server. You should see a hammer icon in the bottom left of the app, indicating available MCP tools.
- Create Repository:
Create a new repository named "my-project" in Azure DevOps.
- Create Pull Request:
Create a pull request from "feature-branch" to "main" in repository "my-project" with title "New Feature" and description "Adding new functionality".
- List Pipelines:
List all available pipelines in the project.
- Get Commit History:
Get the commit history for the "main" branch in repository "my-project".
-
Server Not Found
- Verify the npm installation by running
npm --version
- Check Claude Desktop configuration syntax
- Ensure Node.js is properly installed by running
node --version
- Verify the npm installation by running
-
Authentication Issues
- Confirm your Azure DevOps PAT is valid and has required scopes
- Check the PAT is correctly set in the config
- Verify no spaces or quotes around the PAT
-
Repository Access Issues
- Verify the repository exists in your Azure DevOps project
- Check repository permissions
- Ensure the PAT has appropriate access rights
- Model Context Protocol for the MCP specification
- Anthropic for Claude Desktop
- Microsoft Azure DevOps for the API