{"id":72004,"date":"2025-10-13T03:00:46","date_gmt":"2025-10-13T11:00:46","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/devops\/?p=72004"},"modified":"2025-10-13T04:08:56","modified_gmt":"2025-10-13T12:08:56","slug":"azure-devops-local-mcp-server-generally-available","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/azure-devops-local-mcp-server-generally-available\/","title":{"rendered":"Azure DevOps local MCP Server is generally available"},"content":{"rendered":"

Today we are excited to take our local MCP Server for Azure DevOps<\/a> out of preview \ud83e\udd73. Since the initial preview announcement, we’ve worked closely with early adopters and the community to incorporate feature suggestions and feedback. We\u2019ve improved login and authorization, added and refined tooling, and introduced domains so users can scope active tools to stay under client limits.<\/p>\n

\ud83e\udd37\u200d\u2642\ufe0f What is an MCP Server?<\/h2>\n

A local MCP Server (Model Context Provider) is a tool that sits between your AI assistant (like GitHub Copilot) and your Azure DevOps organization. Its job is to inject rich, real-time context such as work items, pull requests, test plans, and more into the prompts sent to the LLM, allowing the assistant to provide more accurate and relevant answers tailored to your specific Azure DevOps project. The Azure DevOps MCP Server supports most of the main areas of the product, including work items, wiki, repos, search, and test plans. Unlike remote or hosted MCP Servers, a local MCP Server runs inside your network or local development environment, meaning it can safely access private data and tools without that data ever leaving your system.<\/p>\n

\ud83e\udd14 What does \u201cgenerally available\u201d mean?<\/h2>\n

For an open-source project like this, the difference between public preview and general availability is small. You can expect the same level of engagement from us as we continue to monitor issues, incorporate community feedback and contributions, refine existing tools, and introduce new ones. The main change is that now that the project is generally available, we will be more deliberate about how we make updates to minimize the risk of breaking existing tools and ensure greater stability for everyone.<\/p>\n

\u2b50 Getting Started<\/h2>\n

Getting started is simple, though it does require a few setup steps. We recommend following the full installation and setup instructions<\/a> in the repository to ensure everything is configured correctly, but here\u2019s a quick overview to help you get started.<\/p>\n

Navigate to the Azure DevOps MCP Server<\/a> repository.<\/p>\n

    \n
  1. Open Visual Studio Code<\/li>\n
  2. Copy and paste the configuration<\/a> into your local .vscode\\mcp.json<\/code> file. <\/li>\n
  3. Start the MCP Server and begin using the tools.<\/li>\n<\/ol>\n

    If you need additional help, check out the Getting Started<\/a> and Troubleshooting<\/a> guides. You can also explore various example scenarios<\/a> that demonstrate how to use the different tools available in the Azure DevOps MCP Server.<\/p>\n

    Here is one of many examples:<\/p>\n