Troubleshooting the Doover connector

• Use your normal Doover login. It's the same email and password as the Doover app. You can't create a new Doover account from the sign-in page; if you don't have one, contact support@doover.com.
• Check the address. It must be exactly https://mcp.doover.com/. A typo gives a "couldn't reach the server" error.
• Pop-up blocked? Allow pop-ups for claude.ai or chatgpt.com, then try Connect again.
• Still stuck? Remove Doover from your assistant and add it again. This starts a fresh sign-in.

You belong to more than one Doover organisation, so the assistant needs to know which one to use. Tell it, for example:

Use the Acme Water organisation.

Or ask "Which Doover organisations do I belong to?" and pick one. You may need to choose again in a new conversation.

• Check you're in the right organisation (see above).
• The assistant sees what your Doover account can see. If a device is in a group you haven't been given access to, ask your Doover administrator.
• Try the device's exact name as it appears in the Doover app.

• Changes only run after you approve them. Check whether an approval prompt is waiting in the chat.
• Your Doover role may not allow that change. The assistant reports the reason Doover gave.
• If you set the action to Blocked in your assistant's connector settings, change it to Needs approval.

The assistant reads the same data as the Doover app. If the app also shows old data, the device may be offline; ask "When did this device last report?"

• Claude Team or Enterprise: only an Owner can add connectors. Ask them, or use Request on the Doover connector. See Set up Doover for your whole team.
• Claude Free: you can add one custom connector. Remove another one first.
• ChatGPT: custom servers aren't available on every plan, and workspace admins can turn them off. Doover isn't in ChatGPT's plugin directory yet, so ask your admin, or use Claude instead.

Email support@doover.com and tell us:

• which assistant you use (Claude or ChatGPT) and on what (web, desktop or mobile)
• what you asked and what happened
• roughly when it happened, so we can find it in our logs