Confirm the endpoint first. ChatGPT uses https://mcp.stackyapper.dev. Claude, Codex, and most other AI clients use https://mcp.stackyapper.dev/mcp.

Workspaces with a verified custom access domain must use the origin the portal shows on the AI clients page instead of mcp.stackyapper.dev; the same path rules apply.

ChatGPT shows this error when connector setup fails, most often because /mcp was appended to the URL. ChatGPT must use the root URL https://mcp.stackyapper.dev; with /mcp appended it receives the full generic tool surface, and the oversized response makes setup fail. Remove the path and create the connector again.

Try the cheapest fix first: complete a fresh sign-in in the same client and check that the expected workspace is shown on the Stackyapper consent page. If the loop continues, remove the Stackyapper connection from the AI client, add it again, and authorize from scratch.

Stackyapper OAuth authorization is long-lived (see the note on the Claude page), but a user or workspace administrator can revoke it sooner. If authorization is requested unexpectedly, confirm that access was not revoked and then complete a fresh sign-in. Routine Stackyapper deployments should reconnect automatically and should not require reauthorization.

The two most common cases:

For every other status — Ready to configure, Admin setup required, Approval required, Platform setup required — see App status and ownership for what the label means and who can act on it.

Seeing only a handful of stackyapper_ tools is expected. Most AI clients receive a small set of router and workflow tools and discover the full authorized catalog on demand — see What your AI client sees. Ask the client to search Stackyapper for the operation you need before concluding anything is missing.

If a search finds no permitted operation, the user may genuinely lack an app or tool grant. Ask a workspace administrator to check Apps and Users & Groups in the portal.

AI client sessions pin their tool catalog when they connect, and Stackyapper does not push catalog updates into a live session. After an administrator changes app or tool grants, start a new conversation or disconnect and reconnect the client, then retry. Tools discovered through stackyapper_search_tools always reflect current access.

Stackyapper hides pages that the current role cannot use. Owners manage billing, identity, and domains. Owners and administrators manage shared apps, access, and Audit. See Roles and page access.

Check the active workspace, app availability, group and direct user grants, explicit restrictions, and confirmation requirements. Do not grant an entire app until you identify the exact missing tool.

Check whether the app now needs attention, whether the provider is experiencing an outage, and whether the provider account or tenant scope changed. Use the Audit timestamp to correlate the attempt.

Stackyapper requires confirmation for approved risk classes. Review the proposed operation carefully. The confirmation is bound to that operation.

Revoke the API client immediately. Create a replacement, store it only in the intended client's secret store, and verify the replacement in Audit.