How to Connect to Microsoft Remote MCP Servers
Choose the right Microsoft MCP endpoint, configure it in popular clients, authenticate Azure access, and troubleshoot remote MCP connections.
Microsoft remote MCP servers are not one service. The correct connection depends on what you need: public Microsoft documentation, Microsoft product and Azure release updates, or tools that can interact with Azure resources.
Use these endpoints for the corresponding jobs:
| Task | Server | Endpoint | Authentication |
|---|---|---|---|
| Search Microsoft documentation and code samples | Microsoft Learn MCP | https://learn.microsoft.com/api/mcp |
None for the public service |
| Query Microsoft AI at Work Roadmap and Azure Updates | Microsoft Release Communications MCP | https://www.microsoft.com/releasecommunications/mcp |
None or licensing according to Microsoft’s guide; API Terms of Use apply |
| Work with Azure resources | Azure MCP Server | Use the host or deployment route in the Azure MCP documentation | Microsoft Entra ID and Azure RBAC |
Learn MCP and Release Communications MCP are public remote services using Streamable HTTP. Azure MCP Server is a separate resource-management integration with identity and permission requirements. Do not replace an Azure MCP Server configuration with either public documentation endpoint.
1. Select the endpoint for your task
Microsoft Learn MCP
Use Learn MCP when an agent needs official Microsoft documentation or code-sample search. Microsoft documents the endpoint as https://learn.microsoft.com/api/mcp, with no authentication required. The content is public documentation, not training or user profile information. Microsoft says the knowledge service refreshes incrementally after content changes and performs a full refresh daily. A browser request is not a valid protocol test; opening the endpoint directly can return HTTP 405.
Microsoft Release Communications MCP
Use this endpoint for Microsoft AI at Work Roadmap and Azure Updates data: https://www.microsoft.com/releasecommunications/mcp. Microsoft’s guide says no authentication or licensing is required for the public service, while Microsoft API Terms of Use apply. Update and roadmap tools return up to 50 items per request, with pagination and filtering for larger result sets.
Azure MCP Server
Use Azure MCP Server when the agent must inspect or operate Azure services and resources. Microsoft documents connections through supported editors, GitHub Copilot tools, Docker, Python, and .NET. Authentication uses Microsoft Entra ID, and the tools available to an agent follow the Azure RBAC permissions of its identity. Choose the connection method from the current Azure MCP Server documentation; package-manager installation is optional for some approaches.
2. Confirm that your client supports remote MCP
A remote MCP server is an HTTP service reached over the network. A local MCP server normally communicates with a client over standard input/output. Learn MCP and Release Communications MCP describe Streamable HTTP. Some host-specific connectors may label a connection as SSE, so follow the current instructions for the client and version you use. Azure API Management describes Streamable HTTP endpoints commonly ending in /mcp and the older HTTP+SSE pattern using /sse and /messages; HTTP+SSE is deprecated from protocol version 2024-11-05.
Before configuring anything, check:
- The client supports remote MCP and Streamable HTTP.
- Your network permits outbound HTTPS to the selected endpoint.
- You know whether the selected service expects no credentials or Azure identity credentials.
- Your client version’s configuration schema and activation steps are current.
3. Add a public Microsoft server to an MCP client
The exact file name and activation flow vary by host. Microsoft’s Release Communications guide provides this generic HTTP entry:
{
"servers": {
"MRC-MCP-Server": {
"type": "http",
"url": "https://www.microsoft.com/releasecommunications/mcp"
}
}
}For Microsoft Learn, use the same shape with the Learn URL:
{
"servers": {
"Microsoft-Learn": {
"type": "http",
"url": "https://learn.microsoft.com/api/mcp"
}
}
}Use the server name only as a local label. The URL determines which Microsoft service you reach.
VS Code
Microsoft’s MRC guide supports a user-level mcp.json or a workspace .vscode/mcp.json. Add the HTTP server entry using the schema supported by your VS Code release, save the file, then use the MCP controls to start or enable the server. A workspace configuration is useful when a team wants the same server definition checked into a project; a user configuration avoids adding it to source control.
Visual Studio
The guide documents a .mcp.json configuration for Visual Studio. Add the HTTP URL, save the file, and enable the server from the MCP or agent tooling UI.
GitHub Copilot CLI
Use the CLI’s MCP add command described by Microsoft’s guide, then inspect the registered servers and enable the one you need. The command syntax and flags can change with the CLI release, so run the version’s built-in help if the example in the current guide differs.
Claude Code
Claude Code supports adding a remote HTTP MCP server with its MCP command. Follow the current Claude Code documentation for whether the server is saved at user or project scope, then verify that the server appears in the MCP list.
Cursor
Add the server in Cursor’s MCP settings using an HTTP server entry and the selected endpoint. Refresh the MCP list and enable the server before asking an agent to search Microsoft content.
Codex
Microsoft’s MRC guide gives this Codex command:
codex mcp add mrc-mcp --url https://www.microsoft.com/releasecommunications/mcpFor Learn MCP, use the corresponding URL:
codex mcp add microsoft-learn --url https://learn.microsoft.com/api/mcpAfter adding either server, list the configured MCP servers with your Codex version’s MCP command, start a new session if required, and ask a narrow question such as “Which Azure features became Generally Available this quarter?” or “Find the official Microsoft documentation for managed identities.”
4. Verify the connection with a useful request
- Open the client’s MCP or tools panel and confirm the server is enabled.
- Ask for a task that matches the server’s data scope.
- Check that the response cites or links Microsoft content when the client supports source display.
- Try a second query with a known product or feature to distinguish a working connection from an empty search.
Examples:
- Learn MCP: “Find the current Microsoft documentation and code sample for Azure Blob Storage user delegation SAS.”
- MRC MCP: “What’s the status of Feature ID 526798?”
- MRC MCP: “Which Azure features became Generally Available this quarter?”
Do not use a normal browser tab as the verification step. Microsoft warns that manually opening Learn and MRC MCP URLs may produce HTTP 405 because the endpoint expects MCP protocol requests.
5. Connect to Azure MCP Server
Azure MCP Server follows a different setup path from the two public endpoints. Select one of Microsoft’s documented integrations: a supported code editor, GitHub Copilot CLI, SDK or cloud agent, Docker, Python, or .NET.
- Choose the host or deployment method in the current Azure MCP Server guide.
- Install the optional package or container only when that route requires it.
- Sign in with Microsoft Entra ID using the identity your client or process will actually run as.
- Grant only the Azure RBAC roles required for the requested operations.
- Add the server using the configuration and command shown for that host.
- Test with a read-only request before allowing create, update, or delete operations.
For a local server, standard input/output is normally used between the host and the process. For a remote or self-hosted deployment, protect the HTTPS endpoint and apply identity and gateway controls. Microsoft describes Azure API Management as an option for exposing or governing MCP services with policies, monitoring, rate limits, and audit controls.
6. Authentication and permissions
| Connection | Credentials | Permission boundary |
|---|---|---|
| Learn MCP | None | Public Microsoft documentation and code samples |
| Release Communications MCP | None according to the public guide | Public roadmap and release information; Microsoft API Terms apply |
| Azure MCP Server | Microsoft Entra ID | Azure RBAC permissions of the signed-in identity |
| Self-hosted or gateway-protected MCP | Server-specific identity, often enforced by a gateway | Gateway policy plus server and caller permissions |
Never assume “public” means that every Microsoft MCP service is unauthenticated. Scope that statement only to the documented Learn and MRC public endpoints. Azure hosting, API Management, and self-hosted deployments can have their own costs and controls.
7. Secure a remote Azure MCP deployment
- Connect only to trusted, inventoried endpoints.
- Validate Entra ID tokens and reject invalid audience, issuer, or signature values.
- Require valid TLS certificates and fail closed on certificate errors.
- Apply rate limits, audit logging, and monitoring at the gateway when appropriate.
- Give the server and each caller least-privilege Azure RBAC roles.
- Review tool descriptions and outputs because they enter the agent’s context and can influence its behavior.
- Prefer Microsoft’s maintained Azure MCP Server for Azure services, and review updates before enabling new tools.
8. Troubleshooting
HTTP 405 in a browser
Cause: The endpoint expects MCP protocol requests rather than a normal browser GET. Fix: Configure it in an MCP-compatible client and run a tool request.
“Server disconnected” or no tools appear
Cause: The server is disabled, the configuration schema is wrong, or the client has not refreshed its MCP registry. Fix: Check the server entry, confirm the URL, restart or refresh the host, and inspect its MCP logs.
Connection timeout or DNS error
Cause: Firewall, proxy, DNS, or network policy blocks outbound HTTPS. Fix: Test name resolution and HTTPS access from the same machine or container as the client, then allow the specific Microsoft hostname if policy permits.
401 or 403 from Azure MCP Server
Cause: The Entra ID token is missing, expired, issued for the wrong audience, or mapped to an identity without the required Azure RBAC role. Fix: Sign in again, verify the tenant and subscription, inspect the identity used by the process, and grant the narrowest required role.
Tools work but return empty results
Cause: The question does not match the server’s scope, filters are too narrow, or a paginated response was not followed. Fix: Ask a known-scope question, remove restrictive filters, and request the next page where the service supports pagination.
Wrong transport setting
Cause: The client entry says SSE or stdio while the endpoint expects Streamable HTTP, or the reverse. Fix: Use the transport/type documented for your client version and the selected endpoint. Host-specific labels can differ from the protocol terminology.
Agent can see tools it should not use
Cause: The Azure identity has broader RBAC permissions than the task requires, or too many connectors are enabled. Fix: reduce roles and enabled tools, and review the client’s connector limits. Azure SRE Agent documentation currently describes a limit of up to 80 tools across connectors; verify that limit in the current documentation.
9. Performance, freshness, and operating cost
Microsoft Learn says its public service is free and refreshed incrementally, with a full refresh daily. MRC data is also described as refreshing daily. MRC tools return at most 50 updates or 50 roadmap items per request, so use filters and pagination instead of requesting an unbounded history.
Remote calls add network latency and depend on the endpoint, client, proxy, and model. Keep prompts focused, request only the fields needed, and cache stable documentation results in your application when Microsoft’s terms and your freshness requirements allow it. For Azure operations, measure the complete path: token acquisition, MCP request, tool execution, and Azure API response.
The public Learn and MRC services are described as free and unauthenticated. That does not make Azure resources, API Management, containers, network egress, or self-hosted infrastructure free. Budget and monitor those components separately.
10. When to use each server
| Need | Recommended server | Why |
|---|---|---|
| Explain an official Microsoft API | Learn MCP | Searches public documentation and code samples |
| Check roadmap or Azure release status | Release Communications MCP | Provides roadmap and release update tools |
| Read an Azure resource or change configuration | Azure MCP Server | Uses Azure identity and RBAC for resource operations |
| Expose a governed organizational endpoint | Self-hosted MCP behind Azure API Management | Allows gateway policies, monitoring, and access controls |
Or skip the browser setup
If your actual goal is to capture the result of an MCP-powered page or any public URL as an image or PDF, ScreenshotNeo provides a single HTTP request instead of maintaining browser automation. Cookie and consent banners, newsletter popups, and chat widgets are removed before capture. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers identify the page verdict and billing status. ScreenshotNeo also includes an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
See the ScreenshotNeo API documentation for all options.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo supports full-page and element captures, device presets, custom viewports, retina scale, dark mode, PDF paper and page options, custom CSS and JavaScript, clicks, waits, blocked resources, headers, cookies, user agents, timezone, geolocation, transparent backgrounds, resizing, TTL caching, signed links, asynchronous jobs, webhooks, bulk capture, usage reporting, and an OpenAPI specification. It accepts parameter names used by other screenshot APIs, which helps when switching.
The Free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 shots; every feature is available on every plan. Create a free ScreenshotNeo account.
FAQ
Do I need an API key for Microsoft Learn MCP?
No. Microsoft documents the public Learn MCP server as requiring no authentication.
Is Release Communications MCP the same as Azure MCP Server?
No. Release Communications provides roadmap and release information. Azure MCP Server provides tools for Azure resources and uses Entra ID and RBAC.
Can I test an MCP endpoint with curl?
A plain browser-style GET or curl request is not a complete MCP client test. Use an MCP-compatible host that implements the endpoint’s transport and request format.
Should I use local stdio or remote HTTP?
Use remote HTTP for a service available over the network and local stdio for a process running beside the client. Apply authentication and gateway controls to remote organizational deployments.
Can a Microsoft MCP server modify my Azure resources?
The public Learn and MRC servers are information services. Azure MCP Server can expose resource operations according to the connected identity’s Azure RBAC permissions, so test with read-only access and grant only required roles.
