Before you get started, ensure you follow the steps in the README.md file. This will help you get up and running and connected to your Azure DevOps organization.
This MCP Server supports only Azure DevOps Services. Several required API endpoints are not yet available for on-premises deployments. We currently do not have plans to support Azure DevOps on-prem.
No, you can connect to only one organization at a time. However, you can switch organizations as needed.
Currently, you need to fetch the list of projects so the LLM has context about the project name or ID. We plan to improve this experience in the future by leveraging prompts. In the meantime, you can set a default project name in your copilot-instructions.md file.
Yes! Personal Access Tokens (PATs) are supported via the pat authentication type. See the Authentication Methods section in the Getting Started guide for setup instructions, including the required base64 encoding format.
At this time, only the local version of the MCP Server is supported.
Unfortunately, personal accounts are not supported. To maintain a higher level of authentication and security, your account must be backed by Entra ID. If you receive an error message like this, it means you are using a personal account.
We receive this question frequently. The good news is that work is currently underway. Development began in early January 2026. Once we can provide a reliable timeline, we will publish it on the public Azure DevOps roadmap.