Azure DevOps MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADO_PAT | Yes | Azure DevOps Personal Access Token. Never commit or expose this. | |
| ADO_READ_ONLY | No | Set to 'true' to enable read-only mode. Keep 'true' until read operations are verified. | |
| ADO_API_VERSION | No | Azure DevOps API version, e.g., '7.1'. | |
| ADO_ORGANIZATION | Yes | Your Azure DevOps organization name. | |
| ADO_DEFAULT_PROJECT | No | Default Azure DevOps project to use when not specified. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ado_work_item_getC | Get a work item and its fields, relations, and revision. |
| ado_work_items_queryC | Run a bounded WIQL query in a project. |
| ado_work_item_createC | Create a work item when write mode is enabled. |
| ado_work_item_updateB | Update explicitly selected work item fields using JSON Patch. |
| ado_work_item_types_listC | List work item types available in a project. |
| ado_work_item_fields_listB | List work item fields available in a project. |
| ado_work_item_type_getA | Get fields, states, and rules for one work item type. |
| ado_work_item_comments_listB | List comments for a work item. |
| ado_work_item_comment_addA | Add a comment to a work item when write mode is enabled. |
| ado_pull_request_getB | Get a pull request by repository and ID. |
| ado_pull_request_threads_listB | List review threads and comments for a pull request. |
| ado_pull_requests_listC | List pull requests in a project or repository. |
| ado_pull_request_changesB | List changed files for a pull request. |
| ado_pull_request_createC | Create a pull request when write mode is enabled. |
| ado_pull_request_thread_addB | Add a general review comment thread to a pull request. |
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 15 tools
Tools split cleanly by resource (work items vs pull requests) and action (list/get/query/create/update/add). Work item query vs get are distinct via WIQL vs ID lookup, and metadata tools are clearly scoped. No two tools appear to do the same job.
All tools follow the ado_<resource>_<action> pattern, which is predictable and easy to learn. Minor inconsistencies exist: list/query sometimes use plural resources (pull_requests_list, work_items_query) while other actions use singular forms, and both 'add' and 'create' are used for different resources.
15 tools is at the upper boundary but remains well-scoped for work-item and pull-request workflows. Each tool maps to a distinct operation, and the metadata tools (types/fields) are justified by Azure DevOps's dynamic work-item models.
Work item coverage is solid with query/get/create/update/comments, but the PR side lacks update/complete/abandon operations, so a PR can be created and discussed but not merged or completed through the server. There is also no work-item delete or reply to existing PR review threads. These are notable lifecycle gaps rather than trivial workarounds.