To deploy the Azure DevOps MCP Server on Azure Cloud, you can follow the guidance for deploying a self-hosted remote Azure MCP Server and connecting it with Copilot Studio. The MCP Server for Azure DevOps is designed to bring contextual information from Azure DevOps into VS Code using GitHub Copilot.
Here are the steps you can follow based on the available documentation:
- Use the Azure Deployment Template: The deployment involves using the
azdtemplate which includes several Bicep modules that orchestrate the deployment of all resources necessary for the MCP Server. - Bicep Modules: The modules include:
-
main.bicep: Orchestrates deployment of all resources. -
aca-infrastructure.bicep: Deploys the Container App hosting the Azure MCP Server. - Additional modules for creating identities and roles.
-
- Configuration: You will need to configure a custom connector in Power Apps to connect your Copilot Studio agent to the MCP Server. This includes setting up OAuth 2.0 authentication and defining the necessary API methods.
- Testing: After deployment, you can test the connection using the custom connector and ensure that your Copilot Studio agent can access the tools provided by the MCP Server.
As for your question regarding whether the MCP server includes access to Azure DevOps, the MCP Server for Azure DevOps specifically integrates with Azure DevOps services, allowing you to leverage work items, builds, search, repos, and wiki functionalities.
For detailed steps and configurations, you can refer to the official documentation on deploying the remote MCP Server and connecting it with Copilot Studio.
References: