Troubleshooting

OAuth registration or sign-in fails

1. 1Use the exact endpoint shown here, including /api/mcp. Hosted web connectors need a public HTTPS URL, not localhost.
2. 2Use automatic OAuth registration. Do not supply a made-up Client ID or paste a bearer key into an OAuth Client ID field.
3. 3Confirm the account on the consent screen matches this app. If authorization expired or was revoked, reconnect through the client.
4. 4If the error persists, contact support with the client name, time, and error reference. Do not send passwords, keys, login links, or tokens.

The agent says it cannot save

Check that the connection is enabled in this specific chat and the five tools are visible. Installing the skill is not enough. Refresh/restart the client after connection changes, then start a new conversation. If your workspace hides custom connectors, ask its administrator or use a supported alternative.

It says saved, but nothing appears

Look for a successful store_object result. Confirm the same Simple Agent Store account is used by the agent and the viewer, then refresh Objects. A key's quick-install or built-in test does not prove a separate agent is connected. Check tool errors for quota limits or invalid fields before retrying; do not generate duplicate keys blindly.

Results are missing or incomplete

For all notes, use list_objects with the correct kind/labels and follow every cursor. For search, try shorter words that occur in the saved text. Check filters and any expiry (TTL); expired objects are excluded. Search is lexical, not semantic. Retrieve the matched key with get_object before quoting its full contents.

Rate or storage limits

A rate-limit response means pause and retry later; do not loop aggressively. A storage-limit response means the write failed—inspect your plan and existing objects in Billing and Objects. Do not delete data automatically to make space.