Build and ship a remote MCP server on Cloudflare or Vercel

Get a Streamable HTTP server live with auth on either host, with the exact packages and commands. Of 817 reachable endpoints in the directory, 812 speak Streamable HTTP. Verified handshakes took 1,175 ms at the median. First step: Cloudflare: scaffold the remote-mcp-authless template, run npm start, deploy with npx wrangler@latest deploy.

Steps

1. Cloudflare: scaffold the remote-mcp-authless template, run npm start, deploy with npx wrangler@latest deploy.
2. Vercel: install mcp-handler@2.1.1, add app/api/mcp/route.ts, deploy.
3. Add auth: Workers OAuth Provider on Cloudflare, withMcpAuth plus your authorization server on Vercel.
4. Test with the MCP Inspector before connecting a client.

What the sources say

• Cloudflare scaffold: npm create cloudflare@latest -- remote-mcp-server-authless --template=cloudflare/ai/demos/remote-mcp-authless; local endpoint http://localhost:8788/mcp. (developers.cloudflare.com, read 4 November 2026)
• createMcpHandler on Cloudflare is stateless and needs no Durable Object; persist state in KV, D1 or a Durable Object. (developers.cloudflare.com, read 4 November 2026)
• Vercel: npm i mcp-handler@2.1.1 @modelcontextprotocol/server@2 zod@4 on Node.js 20 or later; export the handler as GET and POST. (vercel.com, read 4 November 2026)
• mcp-handler v2 dropped HTTP+SSE and Redis configuration. (vercel.com, read 4 November 2026)
• Test locally with npx @modelcontextprotocol/inspector@latest at http://127.0.0.1:6274 using the Streamable HTTP option. (vercel.com, read 4 November 2026)
• Cloudflare product servers retired /sse on 22 Oct 2026, so new servers should serve /mcp only. (developers.cloudflare.com, dated 22 October 2026, read 4 November 2026)

What the directory sees on the wire

Handshakes with no credentials took 1,175 ms at the median, 2,222 ms at the 90th percentile and 4,442 ms at the slowest, across 263 verified servers.

Host details and evidence: Cloudflare, Vercel and Cloudflare vs Vercel.