Platform Pillar
MCP Gateway
The Squidward MCP Gateway sits between AI clients — Cursor, Claude, and others — and the Model Context Protocol servers they call. Instead of connecting directly to providers, AI clients connect to Squidward, which authenticates the request, checks it against policy, and forwards it only if approved.
What the gateway does
Policy enforcement
Every MCP call is evaluated against your organization's security policies in real time, before it reaches a provider.
Sub-100ms decisioning
Policy checks are designed to add minimal latency, so governed calls stay fast enough for interactive AI workflows.
Full visibility
Every tool invocation is logged with identity, policy decision, and outcome for audit and analytics.
One gateway, many providers
Cursor, Claude, and other AI clients connect to a single Squidward endpoint that fans out to every connected provider MCP.
How it fits together
AI client → Squidward Gateway (policy + DLP + audit) → Provider MCP (GitHub, Vercel, Supabase, and more). Provider credentials never leave Squidward; AI clients authenticate with their own scoped tokens.
Configure your AI tools
Step-by-step setup for Cursor, Claude, and the CLI.