Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The Azure MCP Server enables AI agents and clients to interact with Azure resources using natural language commands. This article explains its features, benefits, and how it helps developers build and deploy apps to Azure.
It implements the Model Context Protocol (MCP) and supports a wide range of tools, languages, and frameworks to help you build and deploy apps to Azure.
Key features
- MCP support: The Azure MCP Server implements the Model Context Protocol, making it compatible with MCP clients such as GitHub Copilot agent mode, the OpenAI Agents SDK, and Semantic Kernel.
- Entra ID authentication: The server uses Entra ID through the Azure Identity library, following Azure authentication best practices.
- Service and tool integration: The server supports Azure services and tools, including the Azure CLI, Azure Developer CLI (azd), and a broad set of Azure resources.
Supported code editors and tools
You can connect to the Azure MCP Server from popular code editors and tools, including:
Supported languages and frameworks
The Azure MCP Server supports multiple languages and frameworks, such as:
Concepts
The Model Context Protocol (MCP) is an open protocol designed to manage how language models interact with external tools, memory, and context in a safe, structured, and stateful way. MCP defines a client-server architecture with several components:
- Hosts: Apps that use MCP clients to connect to and consume data from MCP servers.
- Clients: Components of MCP hosts that manage connections and retrieve data from MCP servers.
- Servers: Programs that provide features like data resources, tools for performing actions, and prompts to guide interactions.
For example, Visual Studio Code is considered a host, and GitHub Copilot agent mode in Visual Studio Code acts as an MCP client that connects to MCP servers. You can also build custom intelligent apps that host their own MCP client to connect to MCP servers.
The Azure MCP Server implements a set of tools per the Model Context Protocol. AI agents and other types of clients use these tools to interact with Azure resources.
How-to guides
You can find step-by-step instructions for common tasks, including:
- Connect GitHub Copilot coding agent to Azure MCP Server
- Deploy a self-hosted Azure MCP Server (Microsoft Foundry)
- Deploy a self-hosted Azure MCP Server (Copilot Studio)
Tools and best practices
The Azure MCP Server offers a wide range of tools for Azure development. For best practices and tool reference, see Tools overview.
Scenarios for using the Azure MCP Server
The most common scenario is connecting to the Azure MCP Server from an existing client, such as GitHub Copilot agent mode in Visual Studio Code or a custom intelligent app. The client can use all available tools to access and interact with Azure resources using natural language. For example, you can use GitHub Copilot agent mode with the Azure MCP Server to list Azure storage accounts or run KQL queries on Azure databases. To learn how to connect to Azure MCP Server from an existing client, see Get started using the Azure MCP Server.
In advanced scenarios, you might create your own MCP servers to offer custom tools, resources, and prompts for specific tasks involving Azure resources. If you're building an MCP server that needs to connect with Azure, you can use the Azure MCP Server tools from your MCP server.
The MCP server uses your Azure user credentials or managed identity to ensure authorized access. Access is secured through Azure Role-Based Access Control (RBAC), providing fine-grained permissions for approved users. The local MCP server is intended strictly for developer use within your organization. Don't use these tools for external applications or scenarios outside the approved development environment.