Microsoft MCP vs Relayer MCP
A side-by-side look at the Microsoft MCP and Relayer MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Microsoft MCP for cloud platforms work over a hosted endpoint; choose Relayer MCP for cloud platforms as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Microsoft MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a remote HTTP/SSE transport.
Choose Relayer MCP when
- You need dedicated capabilities in the Cloud Platforms domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cloud Platforms | Cloud Platforms |
| Quality signal | 47/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3,779 | 3 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Microsoft MCP | View Relayer MCP |
Tools & capabilities
Microsoft MCP tools
No tool names declared yet. Check the project README from the listing page.
Relayer MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Microsoft MCP
{
"mcpServers": {
"microsoft-mcp": {
"url": "https://learn.microsoft.com/azure/ai-foundry/mcp/get-started?view=foundry&tabs=user"
}
}
}
Relayer MCP
{
"mcpServers": {
"xns-cloud-relayer-mcp": {
"command": "npx",
"args": [
"-y",
"@xns-cloud/relayer-mcp@latest"
]
}
}
}
Frequently asked questions
Microsoft MCP is categorized under Cloud Platforms and uses a remote HTTP/SSE transport. Relayer MCP belongs to Cloud Platforms and uses a local stdio subprocess. Pick Microsoft MCP for cloud platforms work and Relayer MCP for cloud platforms.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Microsoft MCP has no declared pricing — check the project's own site. Relayer MCP has no declared pricing — check the project's own site. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add microsoft-mcp and xns-cloud-relayer-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Microsoft MCP has a quality signal of 47/100 (Fair) with 0 views, 0 installs and 3,779 GitHub stars. Relayer MCP has 55/100 (Good) with 0 views, 0 installs and 3 GitHub stars.