Troubleshooting MCP

"client_id not recognized"

This error means the Dynamic Client Registration entry has expired or was never stored. Steps to fix:

1. Clear your browser cache and cookies for autousers.ai and mcp.autousers.ai.
2. Remove the connector from your AI client (Settings → Connectors → Remove).
3. Re-add the connector and complete the OAuth flow again.
4. If it persists, try an incognito/private window to rule out a stale cached registration.

"Origin not allowed"

The Autousers MCP server has an allowlist of permitted request origins. Requests from unlisted origins are rejected with this error.

Permitted origins: claude.ai, *.claude.com, app.autousers.ai, mcp.autousers.ai, localhost:* (development).

Token expiry

OAuth access tokens expire after ~15 minutes. Well-behaved MCP clients refresh automatically using the refresh token. If your client does not support token refresh:

• Re-authenticate by removing and re-adding the connector.
• Switch to API key auth for long-running or unattended sessions.

Rate limiting

If you receive 429 responses, you have exceeded the request rate limit for your plan. Wait for the Retry-After interval indicated in the response header, then retry. Autousers run queuing (autousers_run) also requires sufficient free-run pool balance — call usage_get to check.

mcp-remote OAuth loop (stdio clients)

If mcp-remote keeps re-opening the browser on every startup, the token cache may be corrupted. Delete ~/.mcp-remote-cache (or the equivalent on Windows) and re-authenticate.

Reporting issues

File issues or feature requests at https://autousers.ai/contact or email support@autousers.ai.