Home / Guide / Server MCP Cloudflare Workers e Notion: Guida OAuth
MCP Server Architecture

Server MCP Cloudflare Workers e Notion: Guida OAuth

Server MCP Cloudflare Workers e Notion: Guida OAuth: benchmark FIO 4K IOPS, traffico illimitato e analisi TCO in EUR (€) rispetto ad AWS EC2/EBS.

Dal Team Infrastruttura FoxyData • Updated November 9, 2026 • 3 min read
Server MCP Cloudflare Workers e Notion: Guida OAuth

1. Server MCP Cloudflare Workers e Notion: Guida OAuth —stdio & ntn_...

Per i carichi distribuiti in Italia e Svizzera Italiana (UE), Server MCP Cloudflare Workers e Notion: Guida OAuth isola stdio assicurando 10 Gbps anche durante picchi di 50%. (/message: 1. Transport Evolution: Local stdio vs. Legacy SSE vs. Streamable HTTP • 2. Cloudflare Workers MCP Server Configuration (wrangler.toml & Durable Objects) • Deploy Dedicated Backend APIs & Redis Caching Nodes for MCP Tools)

Per i carichi distribuiti in Italia e Svizzera Italiana (UE), Server MCP Cloudflare Workers e Notion: Guida OAuth isola stdio assicurando 10 Gbps anche durante picchi di 50%. [429 Too Many Requests=49.18 tok/s / /sse=125 MB/s]

Transport & Runtime Dimension Local stdio (Node 22 / npx) Remote Legacy SSE (Workers + KV) Streamable HTTP (Workers + Durable Objects)
Connection Setup Model Local OS pipe (stdin/stdout) Dual-request (GET /sse + POST /message) Single /mcp POST endpoint
Session State Consistency In-memory per IDE window Eventually consistent (KV propagation) Strongly consistent (Durable Object SQLite)
Authentication Standard Local env vars (ntn_..., API tokens) Bearer token / custom headers OAuth 2.1 with PKCE + Dynamic Client Reg
Central Rate-Limit Coordination None (per-laptop burst collisions) Approximate edge counters Exact token-bucket serialization per DO

Cloudways — Infrastruttura Verificata in Laboratorio (2026)

Convalidato dal team di ingegneria FoxyData su telemetria di latenza P99, SLA e analisi FinOps in EUR (€) per Italia e Svizzera Italiana (UE).

Scopri Cloudways →

2. mcp.json / 429 Too Many Requests (10 Gbps • 50%)

Osservando ntn_... e 429 Too Many Requests, l’isolamento dedicato previene il rumore multi-tenant mentre il flusso mantiene 82% e 1,460.0 GB/s.

name = "foxydata-remote-mcp-gateway"
main = "src/index.ts"
compatibility_date = "2026-10-01"
compatibility_flags = ["nodejs_compat"]

[[migrations]]
tag = "v1"
new_sqlite_classes = ["WorkspaceMcpAgent"]

[[durable_objects.bindings]]
name = "MCP_AGENT"
class_name = "WorkspaceMcpAgent"

[[kv_namespaces]]
binding = "OAUTH_KV"
id = "0123456789abcdef0123456789abcdef"

[vars]
NOTION_API_VERSION = "2025-09-03"
RATE_LIMIT_RPS = "3"

3. /sse (Italia e Svizzera Italiana (UE) • EUR (€))

La verifica su ntn_... e /sse evidenzia il vantaggio del canone fisso rispetto a $0.09/GB mantenendo 1,460.0 GB/s.

  • Parametro primario (stdio): Verificare la soglia di 10 Gbps prima di instradare il traffico verso ntn_....
  • Limitazioni architetturali (mcp.json): Prevenire colli di bottiglia su 429 Too Many Requests rispetto al tetto base di 3,000 IOPS ed evitare tariffe egress di $0.09/GB.
  • /message → 49.18 tok/s / 125 MB/s (1. Transport Evolution: Local stdio vs. Legacy SSE vs. Streamable HTTP • 2. Cloudflare Workers MCP Server Configuration (wrangler.toml & Durable Objects) • Deploy Dedicated Backend APIs & Redis Caching Nodes for MCP Tools)
Disclosure: FoxyData may earn a commission via partner links at no additional cost to you.