Azure DevOps Wiki MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| search_wikiC | Search across wiki content using Azure DevOps Search API |
| wiki_get_page_treeB | Retrieve hierarchical page structure from wiki |
| wiki_get_pageB | Get content of a specific wiki page |
| wiki_update_pageA | Update content of an existing wiki page or create a new page if it does not exist |
| list_wikiB | List all wikis in a project |
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 has a clearly distinct purpose: listing wikis, searching content, retrieving a page, fetching the page hierarchy, and updating/creating pages. No overlap or ambiguity.
Naming uses snake_case but mixes prefix styles: 'list_wiki' and 'search_wiki' lack the 'wiki_' prefix that appears in 'wiki_get_page', 'wiki_get_page_tree', and 'wiki_update_page'. This inconsistency may confuse an agent.
With 5 tools, the scope is well-balanced for a wiki server—covering enumeration, search, read, hierarchy, and write operations without excess or deficiency.
Core wiki operations are covered: list, search, get page, get hierarchy, and update/create. A minor gap is the lack of an explicit delete page tool, but the update tool handles creation as well.