Use the MCP server through Azure API Management

Overview

The Office Versions MCP server is exposed publicly as a native Azure API Management MCP server. APIM is the front door for the endpoint, adding subscription-key authentication, rate limiting, and observability. The server exposes the Office 365 / Windows version data as Model Context Protocol tools that any MCP-compatible client (GitHub Copilot, Claude, ChatGPT, MCP Inspector, ...) can discover and call.

Tip: tools are discoverable at runtime via the tools/list JSON-RPC method — no separate schema download is required.

Public endpoint

The MCP server is reachable at the following APIM URL (Streamable HTTP transport):

https://api.office365versions.com/office-mcp/api/mcp

POST — JSON-RPC 2.0 endpoint implementing the Model Context Protocol (initialize, tools/list, tools/call). Protocol version 2025-06-18.
Requests must include the header Accept: application/json, text/event-stream.

Authentication

Every request must include a subscription key in the Ocp-Apim-Subscription-Key header. Use the public MCP key below:

Ocp-Apim-Subscription-Key: ef386cc43d4b40278c78fb648b9cbc59

Rate limits: up to 50 requests per day per client IP address, with a short-term burst limit of 20 requests per minute. Exceeding the limits returns HTTP 429 Too Many Requests.

Available tools

The server exposes the following MCP tools (call them with tools/call):

get_m365_apps_releases — all Microsoft 365 Apps releases across all update channels.
get_m365_latest_by_channel — latest Microsoft 365 Apps release for a channel (arg: channel).
get_m365_by_channel — Microsoft 365 Apps releases for a channel (arg: channel).
get_windows_latest_versions — latest versions for all Windows client and server editions.
get_windows_edition_latest — latest release for a specific Windows edition (arg: edition).
get_windows_all_releases — all Windows client and server releases.
compare_windows_versions — compare two Windows versions (args: version1, version2).
get_windows_servers_summary — summary of all Windows Server versions.
get_windows11_releases — all Windows 11 releases.
get_windows10_releases — all Windows 10 releases.

Example calls

List the available tools via JSON-RPC:

curl -X POST https://api.office365versions.com/office-mcp/api/mcp \
  -H "Ocp-Apim-Subscription-Key: ef386cc43d4b40278c78fb648b9cbc59" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Call a tool (get the latest Windows versions):

curl -X POST https://api.office365versions.com/office-mcp/api/mcp \
  -H "Ocp-Apim-Subscription-Key: ef386cc43d4b40278c78fb648b9cbc59" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_windows_latest_versions","arguments":{}}}'

Security and operational notes

Access is protected by APIM subscription keys; unauthenticated requests return HTTP 401.
The 50/day-per-IP quota and 20/min burst limit are enforced by an APIM product policy.
Tools are generated natively by APIM from the Office Versions REST API operations — no custom MCP backend to maintain.
Monitor APIM analytics to confirm that MCP tool invocations are routed and rate-limited correctly.