Azure DevOps MCP Server for Cline
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 | |
| 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 |
|---|---|
| get_work_itemC | Get work items by IDs |
| list_work_itemsC | List work items from a board |
| create_work_itemC | Create a new work item using JSON patch operations |
| update_work_itemB | Update an existing work item using JSON patch operations |
| get_boardsC | List available boards in the project |
| get_wikisB | List all wikis in the project |
| get_wiki_pageC | Get a wiki page by path |
| create_wikiC | Create a new wiki |
| update_wiki_pageC | Create or update a wiki page |
| list_projectsB | List all projects in the Azure DevOps organization |
| list_pipelinesC | List all pipelines in the project |
| trigger_pipelineC | Trigger a pipeline run |
| list_pull_requestsC | List all pull requests in the project |
| create_pull_requestB | Create a new pull request |
| update_pull_requestC | Update an existing 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
Each tool targets a distinct resource and action (e.g., get_wikis vs get_wiki_page, list_work_items vs get_work_item). No two tools have overlapping purposes, and the descriptions clearly differentiate them.
All tools follow a consistent verb_noun pattern using snake_case, with verbs like get, list, create, update, and trigger. There are no deviations or mixed conventions.
With 15 tools covering projects, wikis, work items, pipelines, pull requests, and boards, the count is well-scoped for an Azure DevOps management server. Each tool addresses a meaningful operation.
Core workflows (create, read, update, list) are covered for work items, wikis, and pull requests, plus project and pipeline management. Minor gaps like delete operations or merge PR are absent but not critical for basic usage.