Free tools Windows power users keep installed
One-click scans. No signup required.
Connecting to a Microsoft remote MCP server starts with choosing the right endpoint. Use Microsoft Learn MCP to search public documentation and code samples, Microsoft Release Communications (MRC) MCP for Azure Updates and the Microsoft AI at Work Roadmap, or Azure MCP Server when an agent must work with Azure resources. The first two are public Streamable HTTP services with no authentication; Azure MCP uses Microsoft Entra ID and Azure RBAC.
Choose the Microsoft MCP server that matches your task
| Task | Service and endpoint | Transport | Authentication and scope |
|---|---|---|---|
| Search official Microsoft documentation or code samples | Microsoft Learn MCP | Remote Streamable HTTP | No authentication; public documentation and samples, not training or profile data |
| Query Azure Updates or Microsoft AI at Work Roadmap | Microsoft Release Communications MCP | Remote Streamable HTTP | No authentication or licensing is required according to Microsoft’s guide; Microsoft API Terms of Use apply |
| Let an agent inspect or operate Azure resources | Azure MCP Server (use the host or deployment route in its documentation) | Remote HTTP or local stdio, depending on deployment | Microsoft Entra ID and Azure RBAC; tools are limited by the signed-in identity’s permissions |
| Expose and govern an MCP service | Azure API Management | Gateway-managed HTTP | Policies can enforce access, rate limits, monitoring and auditing |
Do not substitute a Learn or MRC URL for Azure MCP Server. They answer information questions; Azure MCP is the separate resource-interaction service documented in Microsoft’s Azure MCP Server guidance.
What you need before connecting
- An MCP-compatible host such as VS Code, Visual Studio, GitHub Copilot CLI, Claude Code, Cursor, Codex or another client that supports remote Streamable HTTP.
- The exact endpoint URL for the service you selected.
- For Azure MCP, an Azure identity with only the roles required for the intended operations. Public Learn and MRC endpoints do not require a token.
- Network access to the endpoint, including any corporate proxy, firewall or TLS inspection configuration.
A browser is not an MCP test client. Microsoft notes that opening the Learn or MRC URL directly can return HTTP 405 because the endpoint expects MCP protocol requests; a 405 in that situation does not prove the service is down.
Connect to Microsoft Learn MCP
1. Add the remote server in your client
Use the host’s current remote-server configuration screen or file and set the transport/type to HTTP (often labelled Streamable HTTP). A generic entry is:
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →#1 Best Overall
{
"servers": {
"microsoft-learn": {
"type": "http",
"url": "https://learn.microsoft.com/api/mcp"
}
}
}The property names vary by client. Keep the URL unchanged and do not add an authorization header.
2. Activate and test it
- Save the configuration and restart or refresh the client as its documentation requires.
- Enable the Microsoft Learn server and its tools in the client’s MCP or tool picker.
- Ask a bounded question such as “Find the official C# example for creating an Azure Blob client and link the relevant Learn page.”
- Check that the answer cites Microsoft Learn content rather than inventing a local knowledge result.
Microsoft says the Learn knowledge service refreshes incrementally after content changes and completes a full refresh daily. The overview was last updated 2026-05-22, so confirm current behavior when your deployment depends on a specific page.
Connect to Microsoft Release Communications MCP
Generic HTTP configuration
Microsoft’s published example is:
{
"servers": {
"MRC-MCP-Server": {
"type": "http",
"url": "https://www.microsoft.com/releasecommunications/mcp"
}
}
}Follow the selected client’s current file location and activation steps. Microsoft documents these examples:
Rank #2
- VS Code: put the server in user-level
mcp.jsonor workspace.vscode/mcp.json. - Visual Studio: configure a solution or user
.mcp.jsonas supported by your installed version. - GitHub Copilot CLI: use its
/mcp addcommand and provide the MRC URL. - Claude Code: use the client’s MCP add command, selecting HTTP and the MRC URL.
- Codex: Microsoft documents
codex mcp add mrc-mcp --url https://www.microsoft.com/releasecommunications/mcp. - Cursor: add the equivalent remote HTTP server in Cursor’s MCP settings.
Labels and file schemas can change with client releases; use the current guide for your exact version rather than copying a configuration intended for another host.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsUseful verification prompts
After enabling the server, try a question that requires its data, for example: “Which Azure features became Generally Available this quarter?” or “What’s the status of Feature ID 526798?” The MRC tools return up to 50 updates per request and up to 50 roadmap items per request. Results can have truncated descriptions, so use pagination or filters when the client exposes them.
The service is public and free according to the guide, but Microsoft API Terms of Use still apply, particularly for production or automated use. Release data refreshes daily.
Azure MCP Server: a different connection and security model
Azure MCP Server supplies tools that interact with Azure services and resources. Microsoft documents connections through supported code editors, GitHub Copilot CLI, SDK or cloud-agent integrations, Docker, and Python or .NET applications. NuGet, NPM and PyPI packages are available for some approaches, but package installation is not required for every editor or hosted connection. Select one supported route in the current Azure MCP Server documentation and follow its exact package command and configuration schema.
Authentication and permissions
- Sign in with Microsoft Entra ID using the method required by your host (for example, an editor sign-in, Azure CLI context or workload identity).
- Grant the identity only the Azure RBAC roles needed for the tools it will call.
- Test with a read-only task before enabling write operations.
- Remember that the agent can see whatever the identity can see; MCP does not bypass Azure authorization.
A local Azure MCP process normally communicates over standard input/output. A remote deployment communicates over an HTTP-based MCP transport. Treat a self-hosted endpoint as an internet-facing security boundary, not as a public no-authentication service.
Remote HTTP versus local stdio
Azure API Management describes remote MCP servers as independent processes available through HTTP transports. Streamable HTTP commonly uses a single /mcp endpoint. Older HTTP+SSE deployments may expose /sse and /messages; HTTP+SSE is deprecated from protocol version 2024-11-05. The Learn and MRC services specify Streamable HTTP, although a particular product connector may display a legacy label such as SSE. Follow that connector’s current instructions and do not infer transport solely from a UI label.
Rank #4
Local stdio is appropriate when the process runs on the same developer machine and should not be reachable from the network. Remote HTTP is useful for shared or hosted clients, but it requires endpoint, TLS, identity and monitoring controls.
Secure an organizational or self-hosted Azure MCP deployment
- Protect the endpoint: place it behind Azure API Management or an equivalent gateway when possible.
- Validate identity: verify Entra ID tokens, audience and issuer before forwarding requests.
- Use least privilege: scope both the server identity and each caller’s RBAC permissions.
- Enforce TLS: verify certificates and fail closed on certificate errors; never disable validation to “fix” a connection.
- Control usage: apply rate limits, audit policies and activity monitoring at the gateway.
- Inventory servers: allow only trusted endpoints and review tool definitions, updates and publishers.
- Consider prompt influence: tool descriptions and outputs enter the agent context and can affect its behavior. Review unexpected instructions as untrusted data.
Troubleshoot a failed connection
| Symptom | Likely cause | Fix |
|---|---|---|
| HTTP 405 in a browser | The endpoint expects MCP requests, not a normal GET page | Test from an MCP-compatible host and verify its HTTP/Streamable HTTP setting |
| Server never appears in the tool picker | Wrong configuration file, JSON schema or server not enabled | Validate the file, confirm the client’s documented location, restart or reload the host, then enable the server |
| 401 or 403 from Azure MCP | Missing Entra token, wrong tenant or insufficient RBAC | Refresh the intended identity, check tenant and subscription context, and grant the smallest required role |
| Connection timeout or “disconnected” | Firewall, proxy, DNS or endpoint typo | Check the URL character-for-character, test outbound HTTPS from the host, and review proxy/TLS logs |
| Tools connect but return irrelevant data | Wrong Microsoft service selected | Use Learn for documentation, MRC for roadmap/release data, and Azure MCP for resource operations |
| Works locally but fails for a team | Local credentials or stdio process are not available to remote users | Deploy a governed remote service or provide each user a supported local setup with separate identities |
For Azure SRE Agent connectors, Microsoft specifically recommends checking the endpoint, network access, server-specific authentication, credentials and network configuration when a connector is failed or disconnected. The agent documentation also states a limit of up to 80 tools total across all connectors; this product-specific limit can change.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If your task is generating website images rather than connecting to an MCP knowledge or Azure-resource server, ScreenshotNeo provides a separate screenshot API and MCP server. One GET request returns PNG, JPEG, WebP or PDF. It accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups and chat widgets; each cleanup step can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and response headers identify the page verdict and billing result.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Use the API with the documented options at ScreenshotNeo documentation:
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 also offers an MCP server with take_screenshot, get_page_info and capture_pdf for Claude, Cursor and other MCP clients. Every feature is included on every plan; 1,000 screenshots per month are free without a card, and paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.
Operational limits and freshness
- Learn MCP is free and unauthenticated for public Microsoft content; it is not a gateway to private training or profile information.
- MRC is free and unauthenticated according to its guide, with daily release-data refreshes and the 50-item per-request limits described above.
- Azure MCP, Azure API Management and self-hosted infrastructure can incur normal Azure charges; the public-service statements do not apply to those deployments.
- Endpoint URLs, client support, transports and limits are version-sensitive. Recheck Microsoft’s current page before embedding them in production automation.
Frequently Asked Questions
Can I call Microsoft Learn MCP with a normal REST client?
The endpoint is designed for MCP-compatible clients using Streamable HTTP. A normal browser GET may return 405, so use an MCP host that speaks the protocol.
Do Learn MCP and MRC MCP require an API key?
Microsoft documents both public endpoints as requiring no authentication. Azure MCP Server is different and uses Entra ID and Azure RBAC.
Which server should perform an Azure resource change?
Use Azure MCP Server through a supported host and identity. Learn MCP and MRC MCP provide information and roadmap data, not Azure resource-management authorization.
Is HTTP+SSE still the preferred transport?
Microsoft’s current Learn and MRC descriptions use Streamable HTTP. Azure API Management notes that HTTP+SSE is deprecated from protocol version 2024-11-05, although a host may still expose a legacy label.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
