ado-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADO_DATA_DIR | No | Data directory path (used if no config file found). | |
| ADO_SEARCH_CONFIG | No | Path to JSON config file with dataDir and adoSearchPath. |
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 |
|---|---|
| ado_searchB | Full-text search of indexed Azure DevOps work items and wiki pages |
| ado_grepB | Regex pattern search across work item fields (title, description, comments, etc.) |
| ado_childrenA | List children or descendants of a work item by parent ID |
| ado_showA | Show full content of a work item (by numeric ID) or wiki page (by path). Returns formatted markdown. |
| ado_list_linksB | List links on a work item (fetched live from Azure DevOps) |
| ado_list_commentsA | List comments on a work item (fetched live from Azure DevOps) |
| ado_fetchA | Fetch specific work items by ID from Azure DevOps and add to local store |
| ado_createB | Create a new work item in Azure DevOps |
| ado_updateC | Update an existing work item in Azure DevOps |
| ado_add_commentB | Add a comment to a work item |
| ado_add_linkB | Add a link between two work items |
| ado_remove_linkB | Remove a link between two work items |
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 12 tools
Most tools map clearly to distinct actions, but a few pairs overlap: ado_fetch and ado_show both retrieve work items by ID, and ado_search and ado_grep both search work items. The descriptions help differentiate local-store caching vs. formatted output and full-text vs. regex, but an agent could still misselect.
The consistent 'ado_' prefix helps, but the verb part is mixed: list_comments/list_links and add_link/remove_link use verb_noun, while fetch/create/update/search/show are bare verbs and children is a bare noun. This is readable but not a uniform convention.
Twelve tools is well within the ideal scope for an Azure DevOps work-item search and management server. Each tool covers a distinct operation such as searching, CRUD, comments, links, or hierarchy, so none feels like filler.
The set covers reading, creating, updating, searching, commenting, linking, and hierarchy traversal for work items. Minor gaps exist—there is no delete operation and no explicit general list/query tool—but the core workflows agents need are covered.