Azure DevOps MCP Server

A Model Context Protocol (MCP) server implementation for Azure DevOps, allowing AI assistants to interact with Azure DevOps APIs through a standardized protocol.

Overview

This server implements the Model Context Protocol (MCP) for Azure DevOps, enabling AI assistants like Claude to interact with Azure DevOps resources securely. The server acts as a bridge between AI models and Azure DevOps APIs, providing a standardized way to:

- Access and manage projects, work items, repositories, and more
- Create and update work items, branches, and pull requests
- Execute common DevOps workflows through natural language
- Access repository content via standardized resource URIs
- Safely authenticate and interact with Azure DevOps resources

Server Structure

The server is structured around the Model Context Protocol (MCP) for communicating with AI assistants. It provides tools for interacting with Azure DevOps resources including:

- Projects
- Work Items
- Repositories
- Pull Requests
- Branches
- Pipelines

$3

- AzureDevOpsServer: Main server class that initializes the MCP server and registers tools
- Feature Modules: Organized by feature area (work-items, projects, repositories, etc.)
- Request Handlers: Each feature module provides request identification and handling functions
- Tool Handlers: Modular functions for each Azure DevOps operation
- Configuration: Environment-based configuration for organization URL, PAT, etc.

The server uses a feature-based architecture where each feature area (like work-items, projects, repositories) is encapsulated in its own module. This makes the codebase more maintainable and easier to extend with new features.

Getting Started

$3

- Node.js (v16+)
- npm or yarn
- Azure DevOps account with appropriate access
- Authentication credentials (see Authentication Guide for details):
- Personal Access Token (PAT), or
- Azure Identity credentials, or
- Azure CLI login

$3

If you just want to run the published server package, you do not need to clone or build this repository:

``bash
npx -y @tiberriver256/mcp-server-azure-devops
`

$3

From a checkout of this repository:

`bash
npm ci
cp .env.example .env # then edit values
npm run build
npm start # runs: node dist/index.js
`

For iterative development (auto-reload):

`bash
npm run dev # runs src/index.ts via ts-node-dev
`

$3

To integrate with Claude Desktop or Cursor AI, add one of the following configurations to your configuration file.

#### Azure Identity Authentication

Be sure you are logged in to Azure CLI with az login then add the following:

`json
{
"mcpServers": {
"azureDevOps": {
"command": "npx",
"args": ["-y", "@tiberriver256/mcp-server-azure-devops"],
"env": {
"AZURE_DEVOPS_ORG_URL": "https://dev.azure.com/your-organization",
"AZURE_DEVOPS_AUTH_METHOD": "azure-identity",
"AZURE_DEVOPS_DEFAULT_PROJECT": "your-project-name"
}
}
}
}
`

#### Personal Access Token (PAT) Authentication

`json
{
"mcpServers": {
"azureDevOps": {
"command": "npx",
"args": ["-y", "@tiberriver256/mcp-server-azure-devops"],
"env": {
"AZURE_DEVOPS_ORG_URL": "https://dev.azure.com/your-organization",
"AZURE_DEVOPS_AUTH_METHOD": "pat",
"AZURE_DEVOPS_PAT": "",
"AZURE_DEVOPS_DEFAULT_PROJECT": "your-project-name"
}
}
}
}
`

Azure DevOps Server (on-prem) requires PAT authentication. Example:

`json
{
"mcpServers": {
"azureDevOps": {
"command": "npx",
"args": ["-y", "@tiberriver256/mcp-server-azure-devops"],
"env": {
"AZURE_DEVOPS_ORG_URL": "https://server:8080/tfs/DefaultCollection",
"AZURE_DEVOPS_AUTH_METHOD": "pat",
"AZURE_DEVOPS_PAT": "",
"AZURE_DEVOPS_DEFAULT_PROJECT": "your-project-name"
}
}
}
}
`

For detailed configuration instructions and more authentication options, see the Authentication Guide.

Authentication Methods

This server supports multiple authentication methods for connecting to Azure DevOps APIs. For detailed setup instructions, configuration examples, and troubleshooting tips, see the Authentication Guide.

$3

1. Personal Access Token (PAT) - Simple token-based authentication
2. Azure Identity (DefaultAzureCredential) - Flexible authentication using the Azure Identity SDK
3. Azure CLI - Authentication using your Azure CLI login

Example configuration files for each authentication method are available in the examples directory.

Azure DevOps Server (on-prem) supports PAT authentication only. Azure Identity and Azure CLI are supported for Azure DevOps Services.

Environment Variables

For a complete list of environment variables and their descriptions, see the Authentication Guide.

Key environment variables include:

| Variable | Description | Required | Default |
| ------------------------------ | ---------------------------------------------------------------------------------- | ---------------------------- | ---------------- |
| AZURE_DEVOPS_AUTH_METHOD | Authentication method (pat, azure-identity, or azure-cli) - case-insensitive | No | azure-identity |
| AZURE_DEVOPS_ORG_URL | Full URL to your Azure DevOps organization or Server collection (e.g., https://server:8080/tfs/DefaultCollection) | Yes | - |
| AZURE_DEVOPS_PAT | Personal Access Token (for PAT auth) | Only with PAT auth | - |
| AZURE_DEVOPS_DEFAULT_PROJECT | Default project if none specified | No | - |
| AZURE_DEVOPS_API_VERSION | API version to use | No | Latest |
| AZURE_TENANT_ID | Azure AD tenant ID (for service principals) | Only with service principals | - |
| AZURE_CLIENT_ID | Azure AD application ID (for service principals) | Only with service principals | - |
| AZURE_CLIENT_SECRET | Azure AD client secret (for service principals) | Only with service principals | - |
| LOG_LEVEL | Logging level (debug, info, warn, error) | No | info |

Troubleshooting Authentication

For detailed troubleshooting information for each authentication method, see the Authentication Guide.

Common issues include:

- Invalid or expired credentials
- Insufficient permissions
- Network connectivity problems
- Configuration errors

Authentication Implementation Details

For technical details about how authentication is implemented in the Azure DevOps MCP server, see the Authentication Guide and the source code in the src/auth directory.

Available Tools

The Azure DevOps MCP server provides a variety of tools for interacting with Azure DevOps resources. For detailed documentation on each tool, please refer to the corresponding documentation.

$3

- get_me: Get details of the authenticated user (id, displayName, email) (Azure DevOps Services only)

$3

- list_organizations: List all accessible organizations (Azure DevOps Services only)

$3

- list_projects: List all projects in an organization
- get_project: Get details of a specific project
- get_project_details: Get comprehensive details of a project including process, work item types, and teams

$3

- list_repositories: List all repositories in a project
- get_repository: Get details of a specific repository
- get_repository_details: Get detailed information about a repository including statistics and refs
- get_file_content: Get content of a file or directory from a repository
- get_repository_tree: List a repository's file tree from any path and depth
- create_branch: Create a new branch from an existing one
- create_commit: Commit multiple file changes to a branch using unified diffs or search/replace instructions

$3

- get_work_item: Retrieve a work item by ID
- create_work_item: Create a new work item
- update_work_item: Update an existing work item
- list_work_items: List work items in a project
- manage_work_item_link: Add, remove, or update links between work items

$3

- search_code: Search for code across repositories in a project
- search_wiki: Search for content across wiki pages in a project
- search_work_items: Search for work items across projects in Azure DevOps

$3

- list_pipelines: List pipelines in a project
- get_pipeline: Get details of a specific pipeline
- list_pipeline_runs: List recent runs for a pipeline with optional filters
- get_pipeline_run: Get detailed run information and artifact summaries
- download_pipeline_artifact: Download a single artifact file as text
- pipeline_timeline: Retrieve the stage and job timeline for a run
- get_pipeline_log: Retrieve raw or JSON-formatted log content
- trigger_pipeline: Trigger a pipeline run with customizable parameters

$3

- get_wikis: List all wikis in a project
- get_wiki_page: Get content of a specific wiki page as plain text

$3

- create_pull_request - Create a new pull request
- get_pull_request - Get a pull request by ID
- list_pull_requests - List pull requests in a repository
- add_pull_request_comment - Add a comment to a pull request
- get_pull_request_comments - Get comments from a pull request
- update_pull_request - Update an existing pull request (title, description, status, draft state, reviewers, work items)
- get_pull_request_changes - List changes in a pull request and policy evaluation status
- get_pull_request_checks` - Summarize status checks, policy evaluations, and their related pipelines

For comprehensive documentation on all tools, see the Tools Documentation.

Contributing

Contributions are welcome! Please see CONTRIBUTING.md for contribution guidelines.

Star History


License

MIT