.Anthropic will support stateless remote MCP servers with “just HTTP” as transport. We’re quite excited about this! So we gave a “lightning talk” at an MCP meetup hosted by Paul Butler Cloudflare Developers yesterday.

It matters because the effort to turn existing REST APIs into more LLM-friendly MCP servers will get that much easier: - No new endpoints required (no /sse) - More options to deploy (serverless)

(Talk slides are here.)

Looking forward to connecting with you! #eddymeme #CryptoNews #TopNews

Hey does every tcp connection have reconnecting sockets so after your opening message there’s a disconnect and TLS wrapper for security? You made it sound like api calls just flying around unprotected. Also could save on compute just delete the poll[] information keep the reconnecting tcp assert

@AnthropicAI @paulgb @CloudflareDev i was a little frustrated with that the skinhead guy often failed taking pictures of the screen. I hope he found this post.

@AnthropicAI @paulgb @CloudflareDev I've been running over websockets on serverless workers on Cloudflare for my users and it definitely works too completely agree though, stateless remote MCP will make it much more simpler

@AnthropicAI @paulgb @CloudflareDev Come through:

@AnthropicAI @paulgb @CloudflareDev @KingBootoshi

@AnthropicAI @paulgb @CloudflareDev @grok eli5

@AnthropicAI @paulgb @CloudflareDev http as transport? smart move. integrating new ai into legacy systems often feels like herding cats—stateless mcp servers could tame the chaos. incremental steps > full rewrites. curious how you handle versioning across services without coupling everything too tight?

@AnthropicAI @paulgb @CloudflareDev Is it Vercel’s triangle? 🤔