Troubleshooting
Fixes for the common problems when connecting Zernio to an AI assistant or the CLI, from sign-in errors to accounts that need reconnecting.
The assistant says "No accounts connected"
Sign-in worked, but no social account is connected yet. Connect one in the Zernio app, then ask again.
Claude says "Couldn't reach the MCP server"
Remove the connector and add it again. Claude remembers a failed sign-in until you re-add it.
"Couldn't register with Zernio's sign-in service"
Usually a temporary hiccup. Remove the server or connector and add it again.
Still failing? Check status.zernio.com.
401 Unauthorized
Your sign-in expired or was revoked.
- Assistant: remove the server and add it again to sign in fresh.
- CLI: run
zernio auth:login.
Changes don't show up
After editing your assistant's MCP settings, quit and reopen it completely.
A post failed
Ask your assistant "Why did my last post fail?" or run zernio posts:get <id>.
The most common cause is an account that needs reconnecting. Reconnect it in the Zernio app, then ask the assistant to retry.
It picked the wrong account
Name the account in your request ("post from @acme"). With several accounts on one platform, the assistant asks instead of guessing.