Azure MCP FastMCP Server
A Model Context Protocol (MCP) server that provides Azure DevOps integration through a set of tools for managing projects, work items, teams.
Table of Contents
š Features
Standalone Executable: No dependencies required when using npx
Azure DevOps Integration: Full access to Azure DevOps REST API
MCP Protocol: Compatible with any MCP client
Multiple Tools: Projects, Work Items, Teams, and Policies management
š¦ Installation
Using npx (Recommended)
Local Development
š§ Configuration
Environment Variables
The server requires the following environment variables:
Setting Environment Variables
Method 1: Direct Environment Variables
Method 2: Using .env File
Create a .env file in your project root:
Then run:
Method 3: System Environment Variables
Add to your shell profile (~/.bashrc, ~/.zshrc, etc.):
š ļø Available Tools
š Azure DevOps Permissions
Your Personal Access Token (PAT) needs the following permissions:
Code: Read (for repository access)
Work Items: Read & Write (for work item management)
Project and Team: Read (for project and team information)
Policy: Read (for branch policy access)
š Usage Examples
Basic Usage
With MCP Client Configuration
If using an MCP client like Claude Desktop, add to your configuration:
Bulk Create Work Items
Assign Work Item to Iteration
š ļø Development
Prerequisites
Bun (JavaScript runtime)
Node.js 18+ (for compatibility)
Development Commands
Project Structure
š License
This project is licensed under the MIT License.
š¤ Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
š Support
If you encounter any issues or have questions, please open an issue on GitHub.
Note: This MCP server is designed to be a standalone executable that doesn't require installing dependencies when used with npx. All dependencies are bundled into the final executable for optimal user experience.
ā ļø Known Issues
Iteration Node Update Limitation: Updating project-level iteration node dates (start/end) via the Azure DevOps SDK fails with "Iteration node not found" even when the node is confirmed to exist and is fetchable by ID. All tested path formats fail for update/fetch by path, but fetching by ID works. This may be an SDK bug, REST/SOAP mismatch, or permissions issue. If you encounter this, consider using the Azure DevOps REST API directly or check for updates to the SDK.