Skip to main content
Glama
Ares DevOps MCP Server

Ares DevOps MCP Server

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@latest

Installing via Smithery

To install Ares DevOps MCP Server for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @ares-devops/mcp --client claude

Configuring 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:

  1. Open Cline in VS Code

  2. Click on the Cline icon in the sidebar

  3. Navigate to the "MCP Servers" tab (4 squares)

  4. Search "Ares DevOps" and click "install"

  5. When prompted, enter your Azure DevOps credentials

Alternatively, you can manually set up the Ares DevOps MCP server in Cline:

  1. 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
  1. 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": []
    }
  }
}
  1. 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:

  1. Open Cursor Settings

  2. Navigate to Features > MCP Servers

  3. Click on the "+ Add New MCP Server" button

  4. 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

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.json

Add 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

  1. Create Repository:

Create a new repository named "my-project" in Azure DevOps.
  1. 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".
  1. List Pipelines:

List all available pipelines in the project.
  1. Get Commit History:

Get the commit history for the "main" branch in repository "my-project".

Troubleshooting πŸ› οΈ

Common Issues

  1. 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

  2. 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

  3. 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 tools
comment-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

    A3.5/5.0

    Scored across 8 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      An 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
      -
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables 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
      -