Pricing
Plans are based on enforced capacity: integrations, active tools, monthly calls, per-minute throughput, and redacted response payload size.
For evaluating one MCP surface before production use.
$0forever
Evaluation and small experiments
Highlights
For production OpenAPI and database MCP workflows.
$9.99per month
or $69.99 per year
Production MCP workloads
Highlights
For higher-volume teams with multiple MCP surfaces.
$199.99per month
or $499.99 per year
Higher-volume teams
Highlights
The table shows what changes by plan. OpenAPI publishing, Database to MCP, Gateway Chat testing, redacted logs, and usage analytics are available across plans.
| Category | Free | Pro | Team |
|---|---|---|---|
Enforced capacity These are the limits the platform enforces today. They apply across OpenAPI and database MCP surfaces in the account. | — | — | — |
Max integrations How many MCP integrations you can publish under one account. | 1 | 10 | 50 |
Active tools / integration Maximum number of published tools you can keep active in a single MCP surface. | 3 | 50 | 200 |
Tool calls / month Monthly allowance for executed MCP tool calls. | 1,000 | 50,000 | 200,000 |
Tool calls / minute Per-minute throughput limit before rate limiting applies. | 30 | 120 | 300 |
Redacted response payload stored Maximum redacted response payload size retained for inspection and export. | 8KB | 32KB | 128KB |
These are included in every plan so evaluation and paid usage follow the same Gateway model.
| Feature | Free | Pro | Team |
|---|---|---|---|
Rate limit Per-minute throughput enforcement for MCP tool calls. | Included 30 req/min | Included 120 req/min | Included 300 req/min |
Monthly quota Per-account monthly tool call allowance. | Included 1,000 calls/month | Included 50,000 calls/month | Included 200,000 calls/month |
Request logging Redacted request arguments are stored for inspection. | Included Redacted request args | Included Redacted request args | Included Redacted request args |
Response logging Redacted responses are stored with plan-defined payload limits. | Included Redacted, up to 8KB | Included Redacted, up to 32KB | Included Redacted, up to 128KB |
Usage dashboard Total calls, success rate, latency and call volume. | Included Summary + hourly/day charts | Included Summary + hourly/day charts | Included Summary + hourly/day charts |
Tool analytics Per-tool success and p50/p95/p99 latency breakdown. | Included Per-tool success and latency percentiles | Included Per-tool success and latency percentiles | Included Per-tool success and latency percentiles |
Response export Copy and download redacted response payloads from usage. | Included Copy and JSON download | Included Copy and JSON download | Included Copy and JSON download |
What counts as a tool call?
A tool call is one executed MCP tools/call request routed through the Gateway. Listing tools with tools/list is used for discovery; the quota is meant to measure actual tool execution traffic.
Are OpenAPI to MCP and Database to MCP included?
Yes. Plan capacity applies to published MCP surfaces from OpenAPI integrations and database scopes. The same account limits, rate limits, redacted logs, and usage analytics apply.
What happens when quota or rate limits are reached?
The Gateway blocks additional execution before forwarding the call to the upstream API or database executor. This protects the source system and makes the limit visible in usage flows.
Do MCP clients need upstream API keys or database credentials?
No in the recommended setup. MCP clients authenticate to the Gateway, while upstream API credentials and database connection strings stay server-side.
Can I upgrade later?
Yes. Start with Free to validate one surface, then move to Pro or Team when traffic, integration count, or active tool count grows.
Can I use Gateway Chat on these plans?
Yes. Gateway Chat can be used to test published MCP surfaces before connecting external clients such as Claude, Cursor, or VS Code.
