Dan Hellem introduces the general availability of the Azure DevOps local MCP Server, highlighting its features, local privacy benefits, and integration steps for developers.

Azure DevOps Local MCP Server Now Generally Available

Author: Dan Hellem

The local MCP (Model Context Provider) Server for Azure DevOps has reached general availability. This server bridges your AI assistant—such as GitHub Copilot—and your Azure DevOps organization, injecting real-time context into the prompts processed by large language models (LLMs).

Key improvements since preview include:

  • Enhanced login and authorization
  • Improved and expanded tooling
  • Introduction of domains, enabling scoped tool usage to stay under client limits

What Is a Local MCP Server?

A local MCP Server operates within your internal network or development environment, enabling secure, private access to Azure DevOps data such as work items, wikis, repos, searches, and test plans. Unlike remote or hosted MCP Servers, this local solution keeps your data on-premises for improved security.

The server is deeply integrated with tools like GitHub Copilot, providing tailored, context-rich suggestions and results for developers within Azure DevOps environments.

General Availability — What Does It Mean?

For this open-source project, general availability means more stable releases and careful update management. Community engagement, issue tracking, and feature contributions will remain high priorities.

Getting Started

  1. Visit the Azure DevOps MCP Server repository.
  2. Open Visual Studio Code.
  3. Copy and paste the configuration into your .vscode\mcp.json file.
  4. Start the MCP Server and use the available tools.

For full guidance, refer to the installation and setup instructions, as well as the Getting Started and Troubleshooting guides. You can also review example scenarios for practical use cases.

What’s Next?

The team will continue to collect feedback, welcome community contributions, and develop new tools to extend the server’s capabilities. Developers are encouraged to report issues or suggest features via the project’s GitHub Issues page.

For more information, ongoing updates, and full documentation, visit the Azure DevOps Blog and the project repository.

This post appeared first on “Microsoft DevOps Blog”. Read the entire article here