Ares DevOps MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AZURE_DEVOPS_ORG | Yes | Your Azure DevOps organization name | |
| AZURE_DEVOPS_PAT | Yes | Your Azure DevOps Personal Access Token (PAT) with required scopes | |
| AZURE_DEVOPS_PROJECT | Yes | Your Azure DevOps project name |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create-repoB | Create a new repository in Azure DevOps |
| list-reposA | List all repositories in the organization |
| get-branchesA | List all branches of a repository |
| create-pull-requestB | Create a pull request from one branch to another |
| comment-on-prA | Leave a comment on an existing pull request |
| get-commitsC | Get commit history for a repository |
| trigger-pipelineC | Trigger a CI pipeline with parameters |
| list-pipelinesA | List all pipelines in the project |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.