home / mcp / azure mcp fastmcp server

Azure MCP FastMCP Server

Provides Azure DevOps integration with MCP client compatibility for managing projects, work items, teams, and policies.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "ahmedrowaihi-azure-mcp-fastmcp": {
      "command": "npx",
      "args": [
        "-y",
        "@ahmedrowaihi/azure-mcp-fastmcp"
      ],
      "env": {
        "AZURE_ORG_URL": "https://dev.azure.com/yourorg",
        "AZURE_PERSONAL_ACCESS_TOKEN": "your_token"
      }
    }
  }
}

This MCP server provides Azure DevOps integration through a set of tools for managing projects, work items, teams, and policies. It runs as a standalone executable, streams commands from MCP clients, and authenticates with Azure DevOps using your organization URL and Personal Access Token (PAT).

How to use

You use this server with any MCP client by starting the server locally or running it via a remote command. The server exposes its MCP endpoints so the client can manage Azure DevOps resources like projects, work items, teams, and branch policies. Start the server using the standard runtime and connect your MCP client with the appropriate server configuration. When you initialize a client, provide your Azure DevOps organization URL and PAT so the server can authenticate to Azure DevOps and perform the requested actions.

How to install

Prerequisites you need before installing and running this MCP server are a JavaScript runtime and a modern shell. You will mostly use a runtime that can execute the bundled server, or you can install dependencies locally for development.

# Quick start (no installation required when using npx)
npx -y @ahmedrowaihi/azure-mcp-fastmcp

# Local development flow
# 1) Clone the repository
git clone https://github.com/ahmedrowaihi/azure-mcp-fastmcp.git
cd azure-mcp-fastmcp

# 2) Install dependencies (Bun is used in the project)
bun install

# 3) Build the project
bun run build

# 4) Run the built server
bun run dist/main.js

Configuration and environment

Configure the server with your Azure DevOps credentials to enable REST API access for Projects, Work Items, and other resources.

# Required environment variables
AZURE_ORG_URL=https://dev.azure.com/yourorg
AZURE_PERSONAL_ACCESS_TOKEN=your_pat_here

Security and permissions

Your Personal Access Token (PAT) must include the necessary permissions to read project data, read and write work items, and access repository information. Ensure the PAT has at least the following scopes: Code (Read), Work Items (Read & Write), Project and Team (Read), and Policy (Read). Use a PAT with the minimal permissions required for your use case.

Usage examples

Basic startup is done by launching the MCP server. You can then connect with an MCP client configured to point at this server and your Azure DevOps organization.

Example client configuration (conceptual): you map a local MCP server entry to the Azure DevOps MCP server, specifying how to start the server and which environment variables to pass. The client uses this mapping to route requests to the server.

Development notes

If you are developing or extending the server, you can build and run the project locally: install dependencies, build, and start the server from the generated distribution.

# Install dependencies
bun install

# Build the project
bun run build

# Start the development server (built output)
bun run dist/main.js

Known issues

If you encounter issues updating iteration or other project-level nodes via the Azure DevOps SDK, try fetching by ID or use the REST API directly to verify the current state of the node. SDK REST/SOAP interactions may occasionally mismatch permissions or payload formats.

Available tools

Projects

Manage Azure DevOps projects including creation, lookup, and core properties.

WorkItems

Create, read, and update work items across your projects.

Teams

Manage project teams and memberships.

Policies

Interact with branch policies and enforce governance.