Tizzani.AzureDevOps.MCP

This MCP server integrates with the Azure DevOps REST API. It exposes a server named mcp-azuredevops that uses the tizzani.adomcp CLI entry point to communicate with Azure DevOps using your provided token, organization, and project. The tool is designed to facilitate automation and tooling within MCP workflows by enabling operations such as retrieving work items, projects, builds, and other Azure DevOps resources through the MCP ecosystem. Use the provided flags to configure authentication and scope for the Azure DevOps project you intend to work with. Once running, you can invoke capabilities exposed by the MCP entry point to query, manage, or synchronize data with Azure DevOps as part of your dev-ex, CI/CD, or integration pipelines.

Prerequisites:

• .NET SDK installed on your machine (compatible with the tool you are running).
• Access to NuGet (for package discovery) and permission to install global dotnet tools.

Installation steps:

1. Install the MCP tool globally from NuGet:

dotnet tool install --global Tizzani.AzureDevOps.MCP --prerelease

2. Verify installation:

tizzani.adomcp --help

3. Configure the MCP server (see README example) by adding the mcpServers section to your MCP configuration file (or use the default snippet shown).

4. Run the MCP server with your configured settings and start interacting with Azure DevOps REST API through the MCP interface.

Notes and tips:

• The server expects an Azure DevOps token with appropriate permissions for the requested organization and project.
• In the example, authentication and target scope are provided via command-line arguments: --ado_token, --ado_organization, --ado_project. Ensure these values are kept secure in your environment.
• If you rotate tokens, update the MCP configuration accordingly.
• This server is designed to work within MCP workflows; ensure your MCP tooling can route requests to the mcp-azuredevops server name and pass any required parameters.
• For troubleshooting, verify that dotnet tool is correctly installed and that the token has the necessary Azure DevOps REST API permissions (e.g., Work Items, Projects, Boards, Pipelines as needed).
• If you encounter network or Azure DevOps API rate limits, consider implementing retry/backoff in your orchestration and ensure token scopes align with requested resources.