remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
Integrations
Utilizes environment variables for configuration of organization URL, Personal Access Token, and default project settings.
Enables interaction with Git repositories in Azure DevOps, including accessing repository details and branch information.
Runs on Node.js to provide a server implementation for communicating with Azure DevOps resources via the Model Context Protocol.
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
Core Components
- AzureDevOpsServer: Main server class that initializes the MCP server and registers tools
- Tool Handlers: Modular functions for each Azure DevOps operation
- Configuration: Environment-based configuration for organization URL, PAT, etc.
Getting Started
Prerequisites
- 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
Running with NPX
Usage with Claude Desktop/Cursor AI
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:
Personal Access Token (PAT) Authentication
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.
Supported Authentication Methods
- Personal Access Token (PAT) - Simple token-based authentication
- Azure Identity (DefaultAzureCredential) - Flexible authentication using the Azure Identity SDK
- Azure CLI - Authentication using your Azure CLI login
Example configuration files for each authentication method are available in the examples directory.
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 | 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.
User Tools
get_me
: Get details of the authenticated user (id, displayName, email)
Organization Tools
list_organizations
: List all accessible organizations
Project Tools
list_projects
: List all projects in an organizationget_project
: Get details of a specific projectget_project_details
: Get comprehensive details of a project including process, work item types, and teams
Repository Tools
list_repositories
: List all repositories in a projectget_repository
: Get details of a specific repositoryget_repository_details
: Get detailed information about a repository including statistics and refsget_file_content
: Get content of a file or directory from a repository
Work Item Tools
get_work_item
: Retrieve a work item by IDcreate_work_item
: Create a new work itemupdate_work_item
: Update an existing work itemlist_work_items
: List work items in a projectmanage_work_item_link
: Add, remove, or update links between work items
Search Tools
search_code
: Search for code across repositories in a projectsearch_wiki
: Search for content across wiki pages in a projectsearch_work_items
: Search for work items across projects in Azure DevOps
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
You must be authenticated.
Tools
A Model Context Protocol server that enables AI assistants to interact with Azure DevOps resources including projects, work items, repositories, pull requests, branches, and pipelines through a standardized protocol.
- Overview
- Server Structure
- Getting Started
- Authentication Methods
- Environment Variables
- Troubleshooting Authentication
- Authentication Implementation Details
- Available Tools
- Contributing
- Star History
- License
Related Resources
Appeared in Searches
- A server for information about Jenkins (automation server)
- A system for monitoring and operating terminals
- Azure DevOps and Azure Repos Integration for Developer Workflows
- A platform for hosting and collaborating on software projects
- A tool or assistant to review and suggest changes for GitHub pull requests