This article provides step-by-step instructions for setting up and using a secure MCP (Model Context Protocol) server with Azure API Management. The solution creates a secure gateway that implements the MCP Authorization specification, allowing for authenticated access to AI models and tools.
Before deploying the MCP server, ensure you have:
Registered the required Azure resource provider:
# Using Azure CLI
az provider register --namespace Microsoft.App --wait
# Using Azure PowerShell
Register-AzResourceProvider -ProviderNamespace Microsoft.App
# Check registration status after some time
(Get-AzResourceProvider -ProviderNamespace Microsoft.App).RegistrationState
Installed the Azure Developer CLI (azd) from https://aka.ms/azd
Deploy all required Azure resources (API Management service, Function App, and supporting infrastructure) with a single command:
azd up
This command will:
Install and launch the MCP Inspector tool:
npx @modelcontextprotocol/inspector
Open the MCP Inspector web app by CTRL-clicking the URL displayed in the terminal (typically http://127.0.0.1:6274/#resources)
Configure the connection:
SSE
https://<apim-servicename-from-azd-output>.azure-api.net/mcp/sse
Click Connect to establish a connection to your MCP server
Click List Tools to see available tools
Select a tool and click Run Tool to test its functionality
The deployed solution includes:
The MCP server implements the following security measures:
The MCP server exposes two main endpoints:
Used for establishing real-time communication:
GET https://<apim-servicename>.azure-api.net/mcp/sse
This endpoint requires a valid encrypted session token in the Authorization header.
Used for sending MCP protocol messages:
POST https://<apim-servicename>.azure-api.net/mcp/message
This endpoint handles tool invocations and other MCP protocol messages. It also requires proper authorization.
Both endpoints enforce a comprehensive security policy that validates and decrypts session keys, performs token validation, and ensures proper backend authentication.
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "remote-mcp-apim-functions-python" '{"command":"npx","args":["@modelcontextprotocol/client"],"transport":"sse","url":"https://{apim-servicename}.azure-api.net/mcp/sse"}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"mcpServers": {
"remote-mcp-apim-functions-python": {
"command": "npx",
"args": [
"@modelcontextprotocol/client"
],
"transport": "sse",
"url": "https://{apim-servicename}.azure-api.net/mcp/sse"
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
2. Add this to your configuration file:
{
"mcpServers": {
"remote-mcp-apim-functions-python": {
"command": "npx",
"args": [
"@modelcontextprotocol/client"
],
"transport": "sse",
"url": "https://{apim-servicename}.azure-api.net/mcp/sse"
}
}
}
3. Restart Claude Desktop for the changes to take effect