Skip to main content

Limits

The limits are per account and shared by all its MCP connections.
  • Requests to the MCP server: up to 60 a minute, or your plan’s API rate limit if it is lower. They count apart from your API calls, so a busy agent never blocks your CLI, SDKs or bots. Over it, or while the account is over its API rate limit, the MCP server answers 429 RATE_LIMITED.
  • Tool calls: a budget per minute that grows with your plan.
  • Tools that work inside your applications or on the edge network (files, logs, metrics, network analytics, snapshots, databases and deletions) also have tighter limits of their own.
  • Every tool call counts, including calls refused for a resource or for a scope that depends on the arguments (such as restart on set_env_vars).
  • Commits follow one pace per account and per application, shared with the API, the CLI and the dashboard. A commit sent too soon answers RATE_LIMITED.
A tool over a limit answers TOOL_RATE_LIMITED, described below, with the time to wait.

Zips and files

  • Zip: upload_application and commit_application take a zip of up to 1 MB, sent as base64, and up to 100 MB once unpacked. The dashboard and the CLI take zips of up to 100 MB: use them for a larger project.
  • Files: commit_application takes up to 50 text files, up to 128 KB each and 512 KB in all. They can’t be hidden files, .env files, private keys or the configuration file, which changes through edit_config_file.

TOOL_RATE_LIMITED

A tool over a limit doesn’t run. The answer is a regular tool result marked isError: true, not an HTTP error, so the connection keeps working. retry_after_seconds says when the tool can run again:
When the per-minute tool budget is what was reached, every tool waits; otherwise only that tool does. Calling the same tool again before the wait ends answers TOOL_EXECUTION_FAILED, which tells the client to stop: wait a few minutes or use the dashboard.

Errors

HTTP errors

These come back as the HTTP status of the request, with a JSON body carrying code.

While connecting

Tool results

These come back inside a tool result, as code, next to a summary the client reads. A tool your key can’t use, or one that doesn’t exist, answers the JSON-RPC error -32602 Unknown tool. Check the key’s scopes. Other codes come from the tool itself, and the summary explains them.