DevOps Enhanced MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging by setting the environment variable (e.g., 'devops-mcp'). |
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-itemsC | Get work items from Azure DevOps |
| create-work-itemC | Create a new work item in Azure DevOps |
| update-work-itemC | Update an existing work item in Azure DevOps |
| add-work-item-commentC | Add a comment to an existing work item in Azure DevOps |
| get-repositoriesC | Get repositories from Azure DevOps project |
| get-buildsC | Get build definitions and recent builds |
| get-pull-requestsC | Get pull requests from Azure DevOps repository |
| trigger-pipelineC | Trigger a build pipeline in Azure DevOps |
| get-pipeline-statusC | Get status of a specific build or pipeline |
| get-current-contextC | Get current Azure DevOps context based on directory |
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 10 tools
Each tool has a clearly distinct purpose targeting specific Azure DevOps resources and actions. For example, create-work-item, get-work-items, update-work-item, and add-work-item-comment form a coherent work item lifecycle without overlap, while get-builds, get-pipeline-status, and trigger-pipeline cover distinct pipeline operations. No tools appear to do the same thing.
All tools follow a consistent verb_noun pattern with hyphens, using clear action verbs like 'get', 'create', 'update', 'add', and 'trigger' paired with specific nouns. There are no deviations in naming conventions, making the set predictable and readable throughout.
With 10 tools, this server is well-scoped for Azure DevOps operations, covering work items, pipelines, repositories, and pull requests. Each tool earns its place by addressing a core DevOps workflow, avoiding both thin coverage and bloat.
The tool surface provides strong coverage for key Azure DevOps domains, including CRUD operations for work items and pipeline management. Minor gaps exist, such as no tools for creating or merging pull requests or managing repository branches, but agents can work around these with the available tools.