Which infrastructure and devops MCP servers support the current spec revision?

2 infrastructure and devops MCP servers have verified support for the current revision (2026-07-28). The rest are on earlier revisions or unverified.

Infrastructure and DevOps MCP Servers

Q: Which infrastructure and devops MCP servers are cataloged?

8 infrastructure and devops MCP servers are cataloged, each with verified publisher, access, and spec-revision facts.

8 infrastructure and devops MCP servers are cataloged, 2 with verified current-spec support.

MCP servers that operate infrastructure: container platforms, CI/CD, deployment and hosting providers, monitoring, and observability tooling.

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.
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.
coolify - Spec Support Unverified
Distributed as npm:@masonator/coolify-mcp. Spec revision support not yet verified.
Dynatrace-mcp - Spec Support Unverified
Distributed as npm:@dynatrace-oss/dynatrace-mcp-server. Spec revision support not yet verified.
gitlab-mcp - Spec Support Unverified
Community MCP server (by independent developer zereight) fronting the GitLab API: projects, merge requests, issues, pipelines, wiki, releases. Requires a GitLab personal access token by default, with OAuth modes for self-hosted remote deployments. Not published by GitLab, which operates its own official MCP server. No surface names a supported MCP revision.
Hostinger API MCP Server - Spec Support Unverified
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.
kubernetes-mcp-server - Spec Support Unverified
Distributed as npm:kubernetes-mcp-server. Spec revision support not yet verified.
Sentry MCP Server - Spec Support Unverified
Sentry's first-party MCP server for error monitoring and issue data, hosted at mcp.sentry.dev with OAuth, plus a work-in-progress local stdio transport using a Sentry user auth token. A 2026-08-07 probe confirmed the OAuth requirement first-hand; no surface names a supported MCP revision, so spec support is unverified.