Comparison
Squidward vs. Traditional API Gateways
Traditional API gateways route and rate-limit HTTP traffic. Squidward is purpose-built for the Model Context Protocol, where the request is a structured tool call made by an AI agent rather than a generic HTTP request.
| Capability | Traditional API Gateway | Squidward |
|---|---|---|
| Protocol awareness | Generic HTTP/REST routing | Native understanding of MCP tool calls, parameters, and responses |
| Identity model | API keys or OAuth for services | Per-user, per-agent, and non-human identity entitlements |
| Policy granularity | Route- and rate-limit-based rules | Tool-level allow/deny/redact/quarantine/require-approval policies |
| Data protection | Not typically content-aware | DLP scanning of tool inputs and outputs |
| Audit trail | Request logs, limited semantic context | Full policy-decision context on every MCP call |
When you need both
Squidward is not a replacement for your existing API gateway or edge proxy — it complements it. Your API gateway continues to handle general HTTP traffic, TLS termination, and rate limiting, while Squidward specifically governs the MCP tool calls that AI agents make on top of that infrastructure.
See the gateway in detail
Learn how the MCP Gateway enforces policy on every call.