Metabase

Metabase MCP Server for Cloudflare Workers

Rate Limits & Quotas

Understand the rate limits and quotas for Metabase API access.

Requests / Minute

Requests / Day

Important Notes

•Metabase is an open-source business intelligence and analytics platform
•Metabase does not implement built-in API rate limits in its core product
•Rate limiting depends on the deployment environment and server configuration
•Self-hosted instances: No native API rate limits; can be configured via reverse proxy (nginx, Apache)
•Metabase Cloud: Rate limits may apply but are not publicly documented
•For rate limiting, administrators should implement restrictions at the application server or reverse proxy level

1.
Implement exponential backoff
When you receive a 429 error, wait before retrying with increasing delays.
2.
Cache responses when possible
Store frequently accessed data locally to reduce API calls.
3.
Use batch operations
Combine multiple operations into single requests where supported.
4.
Monitor your usage
Use the Primrose dashboard to track your API usage and set alerts.

Rate Limit Errors

What happens when you exceed limits

{
  "error": {
    "code": "rate_limit_exceeded",
    "message": "Too many requests",
    "retry_after": 60
  }
}

When rate limited, the response includes a retry_after value indicating how many seconds to wait before retrying.