Skip to main content
Coming Soon — MCP Gateway is under active development. Beta currently supports OpenClaw agents only via the OpenClaw plugin. Check the Roadmap for updates.

​
Overview

The CelerFlow MCP Gateway is a standalone service that federates multiple MCP servers behind a single endpoint. Any agent framework with MCP client support can connect — no plugin installation needed.

​
Architecture

The gateway is deployed on Railway as a stateless Node.js/TypeScript service. All state lives in Supabase, so the gateway scales horizontally.

​
Setup

1

Create an API key

Go to Settings → API Keys in the dashboard. Create a key and copy it immediately — it’s only shown once.
2

Register your MCP servers

In Settings → MCP Servers, register the backend MCP servers you want to expose through the gateway (e.g., Gmail MCP Server, Notion MCP Server).
3

Point your agent to the gateway

Replace your MCP server URLs with the single gateway endpoint:
MCP_SERVER_URL=https://gateway.celerflow.ai/mcp
# Authorization: Bearer cf_key_xxx
The gateway federates all your registered MCP servers and handles tool discovery, policy checks, and tracing.

​
Supported frameworks

FrameworkMCP supportIntegration
LangGraph✅ Native MCP clientPoint to gateway.celerflow.ai
CrewAI✅ crewai-tools[mcp]Point to gateway.celerflow.ai
Strands (AWS)✅ Built on MCPPoint to gateway.celerflow.ai
OpenAI Agents SDK✅ MCP server supportPoint to gateway.celerflow.ai
Mastra✅ Native MCPPoint to gateway.celerflow.ai

​
Framework examples

mcp_config = {
    "server_url": "https://gateway.celerflow.ai/mcp",
    "headers": {"Authorization": "Bearer cf_..."}
}

​
Gateway vs proxy

CelerFlow’s MCP Gateway is not a simple proxy. It’s a federation layer:
FeatureSimple proxyCelerFlow Gateway
Routes toOne upstream serverMultiple registered MCP servers
Tool discoveryPass-throughAggregated from all servers
Policy checks❌✅ Service-level permissions
HITL❌✅ Human approval flow
Tracing❌✅ Full trace recording
ProtocolVariesStreamable HTTP (MCP 2025-03 standard)

​
Limitations

  • Only captures MCP protocol tool calls. Built-in tools (e.g., Claude Code’s file_edit) are not intercepted.
  • HITL confirmations work but require an approval channel (see Human approval).
  • Token usage data requires the agent framework to report it via metadata headers (optional).

​
Rate limits

PlanRequests/min
Pro100
Team500
Enterprise2,000

​
Latency

The gateway adds < 50ms P99 overhead. Policy checks use an in-memory cache (60s TTL), and trace writes are non-blocking.