Stytch MCP Server

Rate limit exceeded - 429 error returned

Stytch enforces rate limits per endpoint. Check error response for Retry-After header. Implement exponential backoff for retries. Review rate limits docs for specific endpoint limits. Contact support for increase requests.

Invalid redirect URL or scheme error

Add redirect URL in Stytch Dashboard under redirect_urls. Use https:// for production (http:// only for localhost loopback). Verify URL exact match (case-sensitive). Check no duplicate redirect URLs configured.

Misconfigured client or redirect URL not allowed

Ensure client has valid redirect_urls in Dashboard. Public clients require proper scheme (https or http loopback only). Localhost restrictions apply to certain clients. Verify client ID matches project.

Authentication failed or project access denied

Verify API keys match environment (test vs live). Check project_id and secret from Stytch Dashboard. Ensure user has project access permissions. Re-generate API keys if compromised. Review project security settings.