azure-devops-server-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADO_TOKEN | Yes | Personal access token (PAT) owned by the MCP process. | |
| ADO_PROJECT | No | Default project; tool calls may override it. | |
| ADO_AUTH_TYPE | No | Authentication type. Default is 'pat'; the only v0.1 implementation. | pat |
| ADO_COLLECTION | Yes | Collection name. May contain spaces. | |
| ADO_SERVER_URL | Yes | Server root and optional virtual directory, including any virtual directory such as /tfs, without the collection or project. | |
| ADO_TIMEOUT_MS | No | Per HTTP request timeout in milliseconds. Default is '30000'; range 100-120000. | 30000 |
| ADO_API_VERSION | No | Azure DevOps REST API version. Default is '7.0'; accepts '7.1', '6.0', or '5.0'. | 7.0 |
| NODE_EXTRA_CA_CERTS | No | Absolute path to a company CA certificate PEM file for an internal CA. Configure before launching the process. | |
| ADO_ALLOWED_REPOSITORIES | No | JSON array of {project, repository} entries; restricts all repository access. Required for writes. Omission permits reads according to ADO permissions but disables all PR writes. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_infoA | Check Azure DevOps Server connectivity and safe configuration, or discover accessible projects without a configured default project. With a repository allowlist, diagnostics query only allowed repositories and discovery returns only their projects. Credentials are never returned. The API version is configured; product build is reported only if the server supplies it. |
| repo_repositoryA | Get or list Git repositories in an Azure DevOps Server project. Names and IDs are accepted. A configured ADO_ALLOWED_REPOSITORIES list restricts results and access. Use server_info/list_projects first if the project is unknown. |
| repo_branchA | Get an exact remote Git branch or list remote branches. Branch names are case-sensitive. Only heads are exposed; local Git state is supplied by the agent. |
| repo_pull_requestA | Get a pull request by ID or list pull requests in a repository, optionally filtering status and source/target branch. Returns human-facing PR URLs. |
| repo_pull_request_writeA | Create a PR after verifying both remote branches, or update its title, description, or draft state. Writes require a process-configured ADO_ALLOWED_REPOSITORIES entry; otherwise they are disabled. The agent supplies project/repository and local Git context. No merge, completion, autocomplete, policy bypass, retargeting, or branch deletion is supported. After an uncertain write outcome, list PRs before retrying. |
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 5 tools
Each tool targets a distinct resource (server, repository, branch, PR read vs. PR write), and the `_write` suffix plus description clearly separates read from write for pull requests. The only mild overlap is repo_pull_request vs. repo_pull_request_write, which is mitigated by explicit read-only vs. create/update language.
The set follows a predictable domain-prefix + resource pattern (repo_repository, repo_branch, repo_pull_request, repo_pull_request_write). server_info is the lone outlier that drops the prefix, and some tools are dual-purpose rather than verb_noun, but overall it reads consistently.
Five tools is a tight, well-scoped surface for a read-mostly Azure DevOps Git/PR server. It is slightly lean, but each tool earns its place with no redundant entries.
Coverage is deliberately narrow: repositories and branches are read-only, PRs support create/update but no merge, comments, or completion, and there is no work item or pipeline support. The descriptions reference a list_projects capability that is not present as a tool, a notable gap for the stated discovery workflow.