Cloud Platforms MCP Servers

11 cloud platforms MCP servers are cataloged, 5 with verified current-spec support.

MCP servers that front cloud hosting and infrastructure platforms: projects, deployments, logs, and platform analytics.

• Amazon Bedrock AgentCore Gateway - Current Spec Verified

  A managed AWS service rather than an installable server: each customer gets a per-tenant gateway endpoint and registers their own tool targets. Support for the 2026-07-28 revision is opt-in per gateway, enabled by calling UpdateGateway with the revision in supportedVersions. No source repository or package exists.

• Azure MCP Server - Current Spec Verified

  Microsoft's first-party Azure MCP server, distributed from the microsoft/mcp monorepo. The CHANGELOG records the migration to the 2026-07-28 stateless protocol in prerelease 3.0.0-beta.29 dated 2026-07-23. No stable 3.0.0 has shipped and no vendor-hosted remote endpoint is published; the README documents self-hosting only.

• CloudBase MCP - Spec Support Unverified

  First-party Tencent CloudBase server, distributed as npm:@cloudbase/cloudbase-mcp and also offered as a Tencent-hosted endpoint at tcb-api.cloud.tencent.com/mcp/v1, which requires an env_id parameter plus Tencent Cloud API key headers and so cannot be probed anonymously. Probed 2026-09-03: a GET answered HTTP 405 with a JSON-RPC error body and an uncredentialed server/discover answered HTTP 403 "Forbidden: Missing credentials", which grounds the endpoint as live and credential-gated without negotiating a revision. No documentation names a supported MCP specification revision; the package pins @modelcontextprotocol/sdk 1.30.0, which records what the artifact bundles rather than what the hosted deployment negotiates.

• Cloudflare MCP servers - Current Spec Verified

  Cloudflare's product-specific MCP servers, sixteen Cloudflare-hosted endpoints on mcp.cloudflare.com subdomains. Each request runs on a fresh stateless server with no protocol session. Historical /sse URLs survive as aliases to the same Streamable HTTP handler but no longer serve the deprecated HTTP+SSE transport. Authorization is OAuth with scope selection; the docs endpoint answers unauthenticated. A 2026-08-07 probe of docs.mcp.cloudflare.com/mcp answered server/discover at 2026-07-28 over streamable-http. Endpoint probe confirmed support for 2026-07-28 via server/discover.

• Firebase MCP Server - Earlier Revision

  Firebase's MCP server ships inside the Firebase CLI (firebase-tools) and runs locally via npx firebase-tools mcp, exposing tools across Firestore, Auth, Storage, Crashlytics, Functions, and other Firebase products using the developer's existing CLI credentials. No vendor documentation surface names a supported MCP revision. Resolved from the published package: firebase-tools 15.28.1 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• Hostinger API MCP Server - Earlier Revision

  Hostinger's first-party MCP server for the Hostinger API, run locally from npm or used via the hosted remote at mcp.hostinger.com, which requires OAuth. No vendor surface names a supported MCP revision; a 2026-08-14 probe of the remote returned an OAuth challenge, so revision behavior is not observable without credentials. Resolved from the published package: hostinger-api-mcp 1.45.3 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• MongoDB MCP Server - Earlier Revision

  MongoDB's first-party MCP server for MongoDB databases and Atlas clusters, run locally via npx mongodb-mcp-server or Docker. Version 2.0.0 (2026-08-04) removed session state and requires explicit connection ids. No vendor documentation surface names a supported MCP revision. Resolved from the published package: mongodb-mcp-server 2.1.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• Mux MCP Server - Earlier Revision

  Mux's official MCP server for its video API. A 2026-08-14 probe of mcp.mux.com rejected 2026-07-28 by name (supported versions 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07) and completed a legacy initialize handshake at 2025-11-25, answering as serverInfo "mux" 14.1.0. Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.

• Netlify MCP Server - Current Spec Verified

  Netlify's first-party MCP server, distributed as the npm package @netlify/mcp and documented for stdio use. Netlify's engineering blog states the server already supports the 2026-07-28 specification. A remote endpoint is named in that blog post but is absent from both the docs and the repository README, so it is not recorded here as a verified endpoint.

• Supabase MCP Server - Earlier Revision

  Supabase's first-party MCP server, hosted at mcp.supabase.com/mcp with OAuth dynamic client registration; feature-group, project-scoping, and read-only flags are documented. A 2026-08-07 probe confirmed the OAuth requirement first-hand; no vendor documentation surface names a supported MCP revision. Resolved from the published package: @supabase/mcp-server-supabase 0.10.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.

• Vercel MCP - Current Spec Verified

  Vercel's first-party hosted MCP server: docs search, project and deployment management, log analysis, and Web Analytics queries. Serves the stateless 2026-07-28 revision and 2025-era clients from the same endpoint, with OAuth authorization.