Troubleshooting
Error messages
Section titled “Error messages”| Message | Cause | Fix |
|---|---|---|
Missing Authorization header |
You used https://app.beeive.com/mcp without the header. |
Add the header Authorization: Bearer YOUR_API_KEY. If your app can’t send headers, use https://app.beeive.com/mcp/YOUR_API_KEY instead. |
Invalid API Key |
The key in the URL is wrong, or was rotated. | Copy the current key from Settings → Developers → Access and update the URL. |
Invalid API Key or OAuth token |
The key in the header is wrong or was rotated, or an OAuth approval was revoked. | Update the key, or reconnect and approve access again. |
Common problems
Section titled “Common problems”The assistant says it has no channels. Connect your channels in the Beeive app first. The assistant only sees channels that are already connected. If a channel shows a red ! in Beeive, it needs reconnecting before it can be used.
A post was rejected. Each network has its own rules. For example, YouTube needs a video, and some networks limit how many images a post can have. The assistant checks these rules before posting and usually fixes the post itself. If it keeps failing, ask it which rule the post breaks.
My app only supports the older SSE transport.
Use https://app.beeive.com/sse/YOUR_API_KEY. Prefer Streamable HTTP
(/mcp) whenever your app supports it.
I changed my API key and everything stopped working. Rotating a key disconnects every app that used the old one. Update the key in each app’s config, then restart the app.
Remove access
Section titled “Remove access”- API key connections: rotate your key under Settings → Developers → Access. Every app using the old key loses access immediately.
- Sign-in (OAuth) connections: revoke the app under Settings → Approved Apps.