Getting started
Use the docs for the canonical setup instructions. This page is for the few problems that usually stop a first connection.
Start here
Read the canonical connection and workflow docs, or use the interactive setup at
/connect. To give the machine-readable runbook to your MCP client or agent, use
https://asogenic.com/setup. That machine-readable guide
contains the endpoint, authentication options, config example, credential placement, and
first verification call in one place.
Common connection problems
- The MCP client can't see the ASOgenic tools
- Open the section for that exact client in interactive setup. Confirm the
endpoint ends in
/mcp, complete OAuth in that same product, enable ASOgenic for the new conversation, and callasogenic_auth_status. Do not substitute another client's CLI command. asc_configured: false- The MCP connection is authenticated, but Apple access is not configured. Open the exact
next_action.urlreturned byasogenic_auth_status. Enter the key in the signed-in ASOgenic dashboard, then return to the agent and retry. Never send the key through chat or an MCP tool. - Authentication succeeded, but action discovery failed
- Refresh/reconnect ASOgenic in the affected product, ensure it is enabled for the current chat, and start a new conversation. ChatGPT Plugins, Codex CLI, Claude connectors, and Cursor do not share one live session.
- A consent URL returns 404
- Close the old tab and begin a fresh OAuth action from the affected client. Consent URLs are short-lived and single-use.
- Tools fail with 401
- For an interactive client, reconnect OAuth in that product. For an unattended job using a platform key, rotate or create the key on the dashboard.
RATE_LIMITED- A short-term burst cap, not your monthly quota. Wait a few seconds and continue.
Not covered here? Email [email protected].