MCP Azure DevOps Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AZURE_DEVOPS_PAT | Yes | Personal Access Token for Azure DevOps | |
| AZURE_DEVOPS_ORG_URL | Yes | Azure DevOps organization URL |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_repositoriesA | Search for repositories across all projects |
| get_repository_infoA | Get repository URL, branches with latest check-in dates, and latest PROD/QA deployment information |
| get_pipeline_variablesB | Get pipeline variables from build/release pipelines |
| get_variable_groupsC | Get variable groups from a 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 4 tools
Repository-related tools and variable-related tools are clearly separated, and the descriptions clarify their scope. The only mild ambiguity is between get_pipeline_variables and get_variable_groups, but their descriptions differentiate pipeline-scoped variables from project-level variable groups.
All tool names follow a consistent get_/search_ + noun pattern, making the naming predictable and easy to navigate. There is no mixing of conventions or vague verbs.
Four tools is slightly thin for a server claiming Azure DevOps coverage, but each tool covers a distinct read-only concern. The count is acceptable for a focused utility server, though not richly scoped.
The server only covers limited read operations for repositories, pipeline variables, and variable groups. Major Azure DevOps areas like work items, build/release execution, pull requests, and commits are entirely absent, leaving significant gaps for common agent workflows.