Rate limits - Mobbin Docs

The Mobbin API and MCP server use rate limiting to ensure fair usage and maintain service stability.

Limits

	Scope	Limit
MCP	Per user	60 requests per 60 seconds
MCP Deep Search	Per user	500 deep-mode `search_screens` calls per day, resets 00:00 UTC
API	Per workspace	60 requests per 60 seconds

Exceeding the limit

When you exceed the rate limit, the server returns:

HTTP status 429 Too Many Requests
A Retry-After header indicating how many seconds to wait before retrying

The daily Deep Search limit works differently. The search_screens tool returns an error result that says when the limit resets, instead of a 429. Standard mode searches keep working.

Best practices

Respect Retry-After: When you receive a 429, wait the indicated time before retrying.
Use exponential backoff: If retries continue to fail, increase wait time exponentially with jitter.

​Limits

​Exceeding the limit

​Best practices

Limits

Exceeding the limit

Best practices