MCP server
Beeive runs an MCP server. MCP (Model Context Protocol) is the standard way AI assistants connect to outside tools. Once you connect it, your assistant can see your channels and schedule posts when you ask in plain language:
“Write a short LinkedIn post announcing our new pricing and schedule it for Monday at 9am.”
“Turn this blog link into a thread for X and a caption for Instagram, and save both as drafts.”
“What’s scheduled for next week?”
The assistant uses your connected Beeive channels. It can create drafts, schedule posts, upload images from a link and change post settings. It cannot delete posts: you always do that yourself in the Beeive app.
Server address
Section titled “Server address”| Server URL | https://app.beeive.com/mcp |
| Transport | Streamable HTTP |
| Authentication | Your Beeive API key, or signing in with Beeive (OAuth) |
Three ways to authenticate
Section titled “Three ways to authenticate”Which one you use depends on your client. The step-by-step guide tells you which to pick for each app.
| Method | URL | Use it for |
|---|---|---|
| API key in a header | https://app.beeive.com/mcp with Authorization: Bearer YOUR_API_KEY |
Claude Code, Cursor, VS Code, Windsurf, Codex, Gemini CLI, Amp, Warp |
| API key in the URL | https://app.beeive.com/mcp/YOUR_API_KEY |
Apps that only accept a URL, such as Claude and ChatGPT custom connectors |
| Sign in with Beeive | https://app.beeive.com/mcp-oauth |
Apps that support OAuth. You approve access in the browser and never paste a key |
Before you start
Section titled “Before you start”- You need a paid Beeive plan. MCP access isn’t included on the Free plan.
- Connect at least one channel in the Beeive app first. The assistant can only post to channels that are already connected.
- Your API key is under Settings → Developers → Access.