Limits and quotas
Three plans are available: Free (100 requests/month, 1 server), Plus ($5/month, unlimited requests), and Pro ($10/month, unlimited requests and servers).
| Plan | Price | Requests | Servers |
|---|---|---|---|
| Free | $0 | 100/month | 1 |
| Plus | $5/month | Unlimited | 1 |
| Pro | $10/month | Unlimited | Unlimited (fair use) |
Usage on every plan is monitored for fair use and abuse. See Fair Use and Abuse Monitoring in the Terms.
Other limits
Section titled “Other limits”These apply to every plan, Free through Pro.
| Limit | Cap | What happens over it |
|---|---|---|
Concurrent mcpwarp up agents |
10 per account | The 11th connection is refused with CONNECTION_LIMIT: too many agent connections for this account (limit 10). The CLI doesn’t exit — it retries every 0-30 seconds and reconnects as soon as another agent closes. |
| Servers per config | 100 per config | Registering more than 100 gets TOO_MANY_SERVICES back and the whole batch is rejected; none of those servers register, and the connection stays open. This is per config, not an account-wide total. |
What counts as a request
Section titled “What counts as a request”One HTTP request an MCP client makes to your public URL counts as one request against your quota.
The usage counter resets at the start of each UTC month.
Over quota
Section titled “Over quota”Quota is enforced as a hard block: once you’re over, requests get 429 with a JSON body:
{ "error": "quota_exceeded", "message": "..." }The CLI surfaces this as:
QUOTA_EXCEEDED ... upgrade your plan at https://web.mcpwarp.io/settings to add more serversUpgrade from Settings > Billing in the dashboard. See Manage your subscription.
Downgrading
Section titled “Downgrading”Downgrading below your current server count doesn’t delete servers — it only blocks creating new ones until you’re back within your plan’s limit. On Free, the 100-requests-per-month cap applies starting from your next request. See Manage your subscription.
See Pricing for plan details.