The Search Atlas MCP follows the same rate limits and system constraints as the underlying Search Atlas API. This means all requests made through MCP are subject to standard API limits, including request throttling and usage constraints.
🧠 How Rate Limits Work
MCP does not introduce its own rate limiting system. Instead, it relies on the existing Search Atlas API limits.
👉 Every request made through your AI assistant is processed as an API call.
👉 If too many requests are made in a short period of time, the system may temporarily block additional requests.
You can view your current quota and usage status from Avatar → Billing → Plans & Top-ups (Total Quota) in your Search Atlas dashboard. For specific rate and quota thresholds applicable to your plan, refer to the Search Atlas API limits reference documentation.
⚙️ Step-by-Step: What Happens When You Hit a Rate Limit
Step 1
You send multiple requests through your AI assistant
Example:
- Running multiple audits
- Generating large batches of content
- Executing repeated tool calls
Step 2
The MCP forwards requests to the Search Atlas API
Step 3
The API evaluates request volume
Step 4
If the limit is exceeded:
- The request is rejected
- A rate limit error is returned (commonly a 429 error)
- A 429 error can result from two distinct causes: (1) request-frequency rate limiting, or (2) plan quota exhaustion. Check your quota dashboard when you receive a 429 to determine which condition applies.
🚦 429 vs. ACCESS_DENIED: Understanding the Difference
A 429 error and an ACCESS_DENIED error are not the same and should be troubleshooted differently:
- 429 (rate limit / quota exhausted): Returned when your request frequency is too high or your plan quota has been exhausted.
- ACCESS_DENIED: Returned when the specific MCP endpoint you are calling is not publicly enabled for your account. Some MCP endpoints are not yet publicly available for general use, so ACCESS_DENIED does not necessarily mean you have exceeded your plan quota.
If you see ACCESS_DENIED despite your dashboard showing available quota, the endpoint you are calling may not be publicly enabled for MCP. Contact support to confirm whether the specific MCP tool is available on your plan.
⚠️ Common Scenarios That Trigger Rate Limits
- Rapid repeated requests
- Large batch operations executed too quickly
- High-frequency automation tasks
⚙️ Step-by-Step: How to Resolve Rate Limit Errors
Step 1
Stop sending new requests
Step 2
Wait at least 60 seconds before retrying. For persistent 429 errors related to quota exhaustion, the limit typically resets at the start of your next billing cycle.
Step 3
Retry the request
Step 4
If needed, reduce request frequency
🛠️ Unexpected Quota or Limit Issues
If you believe your quota usage is being over-reported or you are hitting limits unexpectedly early in a billing cycle, contact support — in some cases backend counter drift or billing-sync defects can cause incorrect quota readings that require an engineer to correct.
Additionally, if your account shows a limit of 0 or is unexpectedly fully blocked despite low actual usage, this may be a plan/quota calculation defect. In that case, contact support rather than simply waiting or reducing request frequency.
🔁 Best Practices
To avoid hitting rate limits:
- Space out large operations
- Avoid sending repeated requests in rapid succession
- Break large workflows into smaller steps
⚠️ Important Notes
-
Rate limits apply equally to MCP and direct API usage
-
Limits are enforced automatically by the system
-
MCP does not override or bypass these limitsRate limits apply equally to MCP and direct API usage
-
Limits are enforced automatically by the system
-
MCP does not override or bypass these limits
MCP uses the same infrastructure and protections as the Search Atlas API, including rate limits. By pacing your requests and structuring workflows efficiently, you can avoid interruptions and maintain smooth execution when working through your AI assistant.