MCP errors and troubleshooting

Eekaam returns structured tool errors with a request ID. Keep that request ID when contacting support; it connects the client-visible failure to the activity log.

Tool is missing

The connection does not have the tool's required scope. This is expected permission-aware discovery, not a server outage. Reconnect and approve the needed permission.

Permission was not granted

The token lacks the named scope. Reconnect the integration; retrying the same call will not expand access.

Confirmation required, expired or already used

Call the matching preview again, show the new summary, obtain approval and use the new token. Never cache confirmation tokens.

File changed since it was read

The if_match hash is stale. Read the theme file again, reapply the intended edit to the new content, preview again if the live theme is affected, and then write.

OAuth or connection loop

Confirm the server URL is https://api.eekaam.com/mcp, allow browser redirects and cookies for the approval step, then remove the failed connection and add it again. Do not substitute the dashboard URL.

Safe retry guidance

Read-only and idempotent tools may be retried after a transient transport failure. Do not blindly retry non-idempotent creates; search for the expected record first. MCP annotations expose the idempotency hint for clients that automate retry behavior.