Ares DevOps MCP Server
The Ares DevOps MCP Server enables seamless interaction with Azure DevOps Git repositories and pipelines.
Repository Management: Create new repositories and list existing repositories
Branch Operations: List branches within a repository
Pull Request Management: Create pull requests between branches and add comments to pull requests
Commit History: Get commit history for a repository branch
Pipeline Operations: List available pipelines and trigger pipelines with specified parameters
Enables interaction with Azure DevOps Git repositories, including repository creation, branch management, and commit history retrieval.
Required runtime environment for the MCP server, facilitating Azure DevOps API connectivity.
Provides type-safe operations for Azure DevOps interactions implemented using TypeScript.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Ares DevOps MCP Server create a pull request from feature-login to main in the auth-service repo"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Ares DevOps MCP Server π
π 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
Prerequisites π§
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)
Related MCP server: Ares DevOps MCP Server
Ares DevOps MCP server installation β‘
Running with NPX
npx -y ares-devops-mcp@latestInstalling via Smithery
To install Ares DevOps MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @ares-devops/mcp --client claudeConfiguring MCP Clients βοΈ
Configuring Cline π€
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.jsonAdd 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.
Configuring Cursor π₯οΈ
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@latestImportant: Replace the environment variables with your Azure DevOps credentials
Configuring the Claude Desktop app π₯οΈ
For macOS:
# 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"For Windows:
code %APPDATA%\Claude\claude_desktop_config.jsonAdd the Ares DevOps server configuration:
{
"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"
}
}
}
}Usage in Claude Desktop App π―
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.
Ares DevOps Examples
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".Troubleshooting π οΈ
Common Issues
Server Not Found
Verify the npm installation by running
npm --versionCheck Claude Desktop configuration syntax
Ensure Node.js is properly installed by running
node --version
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
Acknowledgments β¨
Model Context Protocol for the MCP specification
Anthropic for Claude Desktop
Microsoft Azure DevOps for the API
Available Tools
8 toolscomment-on-prA
Leave a comment on an existing pull request
Inputs: comment (required), repositoryId (required), pullRequestId (required), status.
create-pull-requestB
Create a pull request from one branch to another
Inputs: title (required), description (required), repositoryId (required), sourceBranch (required), +1 more.
create-repoB
Create a new repository in Azure DevOps
Inputs: name (required).
get-branchesA
List all branches of a repository
Inputs: repositoryId (required).
get-commitsC
Get commit history for a repository
Inputs: branch (required), repositoryId (required).
list-pipelinesA
List all pipelines in the project
Inputs: no named parameters.
list-reposA
List all repositories in the organization
Inputs: no named parameters.
trigger-pipelineC
Trigger a CI pipeline with parameters
Inputs: parameters (required), pipelineId (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 8 tools
Each tool targets a distinct operation: commenting on PRs, creating PRs, creating repos, listing branches, getting commits, listing pipelines, listing repos, and triggering pipelines. No two tools have overlapping purposes.
All tool names follow a consistent hyphenated lowercase verb-noun pattern (e.g., comment-on-pr, create-pull-request, get-branches). No mixing of conventions.
8 tools is well-scoped for a DevOps server covering repository, branch, commit, pull request, and pipeline operations. Each tool serves a clear purpose without being excessive.
Core workflows are covered (create/list repos, branches, commits, PRs, pipelines), but missing important operations like get pull request details, update/delete repos or PRs, and pipeline status checks. Gaps could hinder full automation.
Related MCP Connectors
The MCP server for Azure DevOps, bringing the power of Azure DevOps directly to your agents.
A MCP server built for developers enabling Git based project management with project and personalβ¦
Create, deploy, and operate MCP servers directly from your GitHub repositories.
Devopness MCP server for DevOps happiness! Empower AI Agents to deploy apps and infra, to any cloud.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables Git repository operations and GitHub PR workflows, allowing users to manage repositories, create branches, commit changes, and create pull requests through natural language.2-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables seamless interaction with Azure DevOps for managing Git repositories, branches, and pull requests through natural language. It also supports automating and monitoring pipelines while providing secure, type-safe operations within MCP-compatible clients.21 npm-
- AlicenseAqualityDmaintenanceAn MCP server that exposes 41 Azure DevOps tools to AI assistants, enabling management of pipelines, repositories, pull requests, releases, work items, test management, and wikis through natural language.41MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI assistants to manage Azure DevOps resources including Work Items, Git repositories, pipelines, and user identities.20 npmMIT