Troubleshooting
Beta
Ceros MCP is in beta and is enabled per account. Contact your Ceros Customer Success Manager to join.
| What you see | What to do |
|---|---|
| The connector isn't available for your account | Beta access is not switched on for that account yet. Contact your Ceros Customer Success Manager. |
| The assistant can't find an experience or folder | Check you can open it in Ceros. It only sees what you can access. If you belong to several accounts, name the account. |
| You're asked to sign in or reconnect | Reconnect. This is normal every few weeks. |
| The sign-in can't complete | Your assistant must sign in with a Client ID Metadata Document (CIMD). In Cursor, check you have version 3.29 or later and the auth block from the Cursor setup. |
| The sign-in window shows an error | Close it and select Connect again. If it keeps happening, contact your Ceros Customer Success Manager with the time it happened. |
| An error from Ceros | Try again in a minute. If it keeps happening, reconnect. |
| Flex AI won't start a build | The assistant tells you why: the account is out of credits, you've reached your own monthly limit, or Flex AI is switched off. Your Ceros admin can help with each. |
| A build is taking a long time | Ask for the build's status, or open the Flex link to watch it. You can also ask to stop the build. |
| You're asked to wait before requesting analytics again | The account has used its hourly allowance of analytics requests. The assistant says when to try again; your Ceros dashboards are not affected. |
| No activity is reported | Only published experiences collect analytics. Check the experience is published and the dates are right. |
Getting help
Contact your Ceros Customer Success Manager. Please include which AI assistant you used, what you asked it, roughly when, and the experience name.