Azure DevOps Wiki MCP Server

🌟 Azure DevOps Wiki MCP Server

A Model Context Protocol (MCP) server that brings Azure DevOps Wiki context to your AI agents, enabling seamless integration with Azure DevOps wikis.

📄 Table of Contents

• 🌟 Project Overview
• ⚙️ Supported Tools
• 🔌 Installation & Getting Started
• 🔑 Authentication
• 🛠️ Development
• 🏗️ Architecture
• 🤝 Contributing
• 📝 License

🌟 Project Overview

The Azure DevOps Wiki MCP Server enables AI applications to interact with Azure DevOps wikis through the Model Context Protocol. It provides comprehensive wiki operations including content search, page management, and hierarchical structure navigation.

Key Features:

• 🔍 Search across wiki content
• 📄 Read and update wiki pages
• 🌲 Navigate hierarchical page structures
• 📋 List and manage wikis
• 🔐 Secure authentication via Azure CLI or PAT

⚙️ Supported Tools

🔍 search_wiki

Search across wiki content using Azure DevOps Search API.

Parameters:

• organization (required): Azure DevOps organization name
• project (required): Project name
• searchText (required): Search query string
• wikiId (optional): Specific wiki identifier

🌲 wiki_get_page_tree

Retrieve hierarchical page structure from wiki.

Parameters:

• organization (required): Azure DevOps organization name
• project (required): Project name
• wikiId (required): Wiki identifier
• depth (optional): Maximum depth to retrieve

📄 wiki_get_page

Get content of a specific wiki page.

Parameters:

• organization (required): Azure DevOps organization name
• project (required): Project name
• wikiId (required): Wiki identifier
• path (required): Page path or page ID

✏️ wiki_update_page

Update content of an existing wiki page or create a new page if it does not exist.

Parameters:

• organization (required): Azure DevOps organization name
• project (required): Project name
• wikiId (required): Wiki identifier
• path (required): Page path or page ID
• content (required): New page content (Markdown)

📋 list_wiki

List all wikis in a project.

Parameters:

• organization (optional): Azure DevOps organization name
• project (optional): Project name

Note: Both parameters are optional and will use environment defaults if not provided.

🔌 Installation & Getting Started

Prerequisites

• Node.js 18 or higher
• Azure CLI installed and configured (az login) Required only if you wish to authenticate with Azure, not required if you choose to use PAT token
• Appropriate Azure DevOps permissions for target organization

Configure in Claude Desktop using PAT authentication

Add to your claude_desktop_config.json:

Configure in Claude Desktop using Azure authentication

1. Authenticate with Azure:
   az login
2. Configure with Claude Desktop: Add to your claude_desktop_config.json:
   { "mcpServers": { "azure-devops-wiki": { "command": "npx", "args": [ "-y", "azure-devops-wiki-mcp" ], "env": { "AZURE_DEVOPS_URL": "https://dev.azure.com/your-organization", "AZURE_DEVOPS_PROJECT": "your-project", "AZURE_DEVOPS_ORGANIZATION": "your-organization-name" } } } }

🔑 Authentication

This server supports two authentication methods:

1. Azure CLI Authentication (Default)

Make sure you're logged in:

The server will use your Azure CLI credentials to authenticate with Azure DevOps.

2. Personal Access Token (PAT)

You can also use a Personal Access Token for authentication by setting environment variable AZURE_DEVOPS_PAT.

Creating a PAT:

1. Go to Azure DevOps → User Settings → Personal Access Tokens
2. Create a new token with the following scopes:
   • Wiki: Read & Write
   • Project and Team: Read (for project access)
3. Copy the token and set it in the AZURE_DEVOPS_PAT environment variable

Environment Variables:

When using PAT authentication, the server will prioritize the PAT over Azure CLI credentials.

🛠️ Development

Setup

Available Commands

For Local Development

Add to your claude_desktop_config.json:

Debug in IDE

1. Start up @modelcontextprotocol/inspector with inspection turned on:
   mcp-inspector node --inspect dist/index.js # Alternatively, set the environment variables when you launch it mcp-inspector -e AZURE_DEVOPS_URL="Your DevOps URL" -e AZURE_DEVOPS_PROJECT="Your DevOps Project" -e AZURE_DEVOPS_PAT="Your PAT" -e AZURE_DEVOPS_ORGANIZATION="Your DevOps Organization" node --inspect dist/index.js
2. Use IDE (vscode / cursor), select "Attach to MCP Server" and start debug
3. Enter local test data from MCP Inspector UI

🏗️ Architecture

The server follows the Model Context Protocol specification and integrates with Azure DevOps Wiki API through the official azure-devops-node-api client library.

Key Components:

• MCP Server: Implements MCP protocol using @modelcontextprotocol/sdk
• Azure DevOps Client: Wrapper around azure-devops-node-api for Wiki API operations
• Tool Handlers: Five main tools implementing MCP tool interface
• Authentication: Azure CLI-based authentication with PAT fallback

📦 Package Publishing & Release Management

Version Bumping

The project includes automated version bumping scripts for semantic versioning:

Each version bump command automatically:

1. Updates the version in package.json
2. Creates a git commit with the version number
3. Creates a git tag (e.g., v1.0.1)

🤝 Contributing

1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Add tests
5. Submit a pull request

📝 License

MIT