MCP
MCP server
Let Claude, Cursor, ChatGPT and other AI assistants schedule and manage your posts.
The Model Context Protocol lets an AI assistant use tools. CreatorHyve's MCP server gives an assistant tools to see your connected accounts, write and schedule posts, upload media, read results and analytics, and (with your approval and a daily limit) spend credits on AI images and AutoFlows.
Server address: https://creatorhyve.com/api/mcp (Streamable HTTP).
Two ways to sign in
| Method | Use it with | How |
|---|---|---|
| API key | Claude Code, Cursor, scripts, anything that lets you set a header | Create a key with the MCP access permission and pass it as Authorization: Bearer ch_live_.... |
| Sign in (OAuth) | Claude.ai, Claude Desktop, ChatGPT and other connector-style clients | Add the server address as a custom connector, sign in to CreatorHyve and press Allow. No key to copy. |
Both need the Scale plan. Pages for each client: Claude Code, Claude.ai and Claude Desktop, Cursor, ChatGPT.
What assistants can and cannot do
- They cannot publish immediately.
create_postsaves a draft or schedules for a future time, so you can still review. - They only get the tools their permissions allow (a read-only key sees no write tools).
- Tools that spend credits (AI images, AutoFlows) stop at your daily limit for assistants, which defaults to 2 credits. Change it under Settings, then Developer, then AI assistants. Set 0 to block spending.
- Deleting is limited to drafts and not-yet-publishing scheduled posts.
- Every tool call is logged (tool name, result, time, credits; never the content) and shown under Recent activity in the same settings card.
- You can disconnect a signed-in assistant at any time; its access ends immediately.
Treat an assistant like a colleague with your dashboard open. Text it reads from the web or from other apps can try to steer it. Keep the daily credit limit low, leave AutoFlows in review mode, and check the drafts.
Tools
See the full tool list. Start every task with list_social_accounts.