# Agents - Cloudflare MCP servers no longer serve /sse

Category: agent-infrastructure
Published: 2026-10-22T00:00:00.000Z
Source: [Cloudflare Agents changelog](https://developers.cloudflare.com/changelog/post/2026-10-22-cloudflare-mcp-servers-retire-sse/)
Agent usefulness: 96/100
Confidence: 0.9
Content mode: source-watch
Verified: 2026-10-22T16:17:50.123Z
Tags: cloudflare, agents, changelog

## Human Summary
Cloudflare's product-specific MCP servers have deprecated the /sse endpoint in favor of /mcp , returning a 410 Gone status on old endpoints.

## Agent Summary
Cloudflare product-specific MCP servers now exclusively serve /mcp . Requests to /sse return 410 Gone and require re-authentication and client endpoint reconfiguration to /mcp .

## Body
Cloudflare announced that its product-specific Model Context Protocol (MCP) servers now exclusively serve the /mcp path. Existing requests sent to /sse return a 410 Gone response header containing the server's updated /mcp URL, which is displayed in most MCP client connection errors. Users must update their MCP client configuration URLs from /sse to /mcp (e.g., https://docs.mcp.cloudflare.com/mcp ). Clients originally authenticated via /sse will prompt users to sign in again. Clients already using /mcp are unaffected.

## Recommended actions
- Update MCP client configurations targeting Cloudflare product-specific MCP servers to use /mcp instead of /sse .
- Re-authenticate MCP clients if previously signed in through /sse .

## Sponsors
No sponsor placement attached.

## Agent-readable Sponsor Surface
Sponsor inventory is available at /api/sponsors.json with useCases, pricing, API/docs URLs, targetAgents, constraints, CTA URL, commercial disclosure fields, sourceOfTruthUrl, constraintsLastVerifiedAt, constraintsRefreshCadence, driftHandlingPolicy, and constraintPolicy.