Azure DevOps MCP Server

An MCP (Model Context Protocol) server for managing Azure DevOps work items — Product Backlog Items (PBIs), Tasks, Bugs — and their comments, directly from an MCP-compatible client such as Kiro, Claude Desktop, or Cursor.

Configured for the organization DigiFY2025 and project DIGI STD FY26.

Features

• Create, read, update PBIs

• List your own unfinished work items

• Flexible search/list with filters or raw WIQL

• Add, list, update, delete comments on any work item

• Automatic sprint detection based on the current date

• Sensible defaults for area path and iteration path

Related MCP server: Azure MCP FastMCP Server

Prerequisites

• Node.js 18+ (uses the built-in fetch). See .nvmrc for the pinned version.

• An Azure DevOps Personal Access Token (PAT) with Work Items (Read & Write) scope.

Setup

1. Install dependencies:

   npm install

2. Create a .env file from the example and add your PAT:

   cp .env.example .env

   AZURE_DEVOPS_PAT=your-personal-access-token-here

   .env is git-ignored. Never commit your real PAT.

3. Run the server:

   npm start

MCP Client Configuration

Add the server to your MCP client config (e.g. .kiro/settings/mcp.json):

{
  "mcpServers": {
    "azure-devops": {
      "command": "node",
      "args": ["/absolute/path/to/azure-devops-mcp/index.js"],
      "env": {
        "AZURE_DEVOPS_PAT": "your-personal-access-token-here"
      }
    }
  }
}

Available Tools

Work items

Comments

Configuration constants

Defined at the top of index.js:

• ORG — Azure DevOps organization (DigiFY2025)

• PROJECT — project name (DIGI STD FY26)

• DEFAULT_AREA_PATH — default area path for new PBIs

• SPRINT_LIST — sprint schedule used for automatic current-sprint detection

Security

• Authentication uses the AZURE_DEVOPS_PAT environment variable only; no tokens are hardcoded.

• .env is git-ignored so your PAT stays local.

• Treat your PAT like a password: scope it minimally and rotate it if exposed.

License

MIT