Azure DevOps MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AZURE_DEVOPS_PAT | Yes | Personal Access Token | |
| AZURE_DEVOPS_ORG_URL | Yes | Organization URL (e.g., https://dev.azure.com/myorg) | |
| AZURE_DEVOPS_MCP_DEBUG | No | Enable debug logging to .azure-devops-mcp/mcp.log | false |
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 |
|---|---|
| azuredevops_list_projectsA | List all projects in the Azure DevOps organization. Use this to discover available projects when the project name is not known or to verify a project exists. |
| azuredevops_search_work_itemsA | Search for Azure DevOps work items using WIQL (Work Item Query Language). Returns a list of work items matching the query. Project is required - discover it from project context or use azuredevops_list_projects. |
| azuredevops_get_work_itemA | Get detailed information about a specific Azure DevOps work item by its numeric ID. Project is required - discover it from project context. |
| azuredevops_create_work_itemC | Create a new Azure DevOps work item (Bug, Task, User Story, Feature, etc.). Project is required - discover it from project context. |
| azuredevops_update_work_itemA | Update an existing Azure DevOps work item using JSON Patch operations. Can modify any field including state transitions. Project is required - discover it from project context. |
| azuredevops_add_commentA | Add a comment to an existing Azure DevOps work item. Supports HTML formatting. Project is required - discover it from project context. |
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 6 tools
Each tool has a clearly distinct purpose: listing projects, searching work items, getting a work item, creating, updating, and commenting. The actions and resources are unambiguous, leaving no room for confusion.
All tool names follow a consistent snake_case pattern with the 'azuredevops_' prefix followed by a verb and object (list_projects, search_work_items, etc.). This is highly predictable and readable.
Six tools is a reasonable, well-scoped set for managing work items and projects in Azure DevOps. It might be slightly under-provisioned for broader DevOps tasks, but it covers the core work item lifecycle.
The toolset covers the essential CRUD operations for work items (create, read, update, search, comment) and project listing. However, it lacks deletion of work items and any tools for other Azure DevOps resources like repositories, pipelines, or boards, which are common in the domain.