Atribu
MCP Server

Error Reference

MCP error codes, what they mean, and how to fix them

When an MCP tool call fails, the response includes isError: true and a structured error object. Your AI tool will typically explain the error and suggest a fix.

Error response format

Error response
{
  "error": {
    "code": "rate_limited",
    "message": "Per-minute rate limit exceeded. Wait 12 seconds.",
    "retryable": true,
    "retry_after": 12,
    "request_id": "01968a3b-..."
  }
}

Some errors include additional fields:

  • action_url -- a link to the Atribu dashboard page where you can fix the issue
  • workspaces -- a list of available workspaces (for workspace_required)
  • profiles -- a list of available profiles (for profile_required)
  • support_hint -- a suggestion to contact support with the request_id

Error codes

Authentication errors

CodeRetryableCauseFix
auth_requiredNoMissing or malformed Authorization headerAdd Authorization: Bearer atb_user_... header
token_expiredNoToken has been revoked or expiredCreate a new token from Developer > MCP Tokens

Scope errors

CodeRetryableCauseFix
workspace_requiredNoUser has multiple workspaces and none was specifiedPass workspace_id -- the error includes a list of your workspaces
profile_requiredNoWorkspace has multiple profiles and none was specifiedPass profile_id -- the error includes a list of profiles
insufficient_scopeNoToken lacks the required scope for this toolCreate a new token with the needed scope

Single-resource inference

If you have exactly one workspace or one profile, it's selected automatically. These errors only occur when there are multiple options.


Rate limit errors

CodeRetryableCauseFix
rate_limitedYesPer-minute or per-period unit cap exceededWait retry_after seconds, then retry

The retry_after field tells you how many seconds to wait. AI tools that support retry will handle this automatically.


Connector errors

CodeRetryableCauseFix
connector_expiredNoA required integration's OAuth token has expiredRe-authorize at the action_url in the error response
connector_requiredNoA required integration is not connectedConnect it at the action_url in the error response

These errors include an action_url that links directly to the integrations page in your Atribu dashboard.


Write-back errors

CodeRetryableCauseFix
writeback_disabledNoWorkspace admin has not enabled MCP write-backAsk a workspace admin to enable it in Settings > Privacy & MCP
idempotency_conflictNoA confirm with this idempotency key was already processedThe prior result is returned -- no action needed
circuit_openYes3+ consecutive failures in the last 30 minutesWait for the cooldown, then investigate the underlying failures

Input errors

CodeRetryableCauseFix
invalid_inputNoInvalid or missing parametersCheck the parameter types and required fields
data_unavailableNoNo data exists for the specified window or entityWiden the date range or verify the entity exists

Server errors

CodeRetryableCauseFix
internal_errorYesUnexpected server errorRetry once. If persistent, contact support with the request_id

Troubleshooting

"I get workspace_required but I only have one workspace"

This can happen if your token was created before a workspace was deleted. Try calling list_workspaces to see which workspaces your token can access, and pass the workspace_id explicitly.

"Data seems stale or empty"

Check the meta.data_as_of field in successful responses. If it's more than a few hours old, your integration may need re-syncing. Go to Settings > Integrations and check the sync status.

"I can't see customer emails"

PII is masked by default. You need all three: mcp:read_pii token scope, include_sensitive: true in the tool call, and workspace PII mode set to full_default. See Privacy & PII.

"send_meta_conversions returns insufficient_scope"

This tool requires the mcp:write token scope, workspace write-back enabled, and workspace admin role. Check all three conditions.

On this page