The Kadenzo MCP server is used to connect Kadenzo's social media management capabilities to AI agents. It wraps the public API of Kadenzo Studio into Model Context Protocol (MCP) tools, enabling MCP-enabled AI clients (such as Claude Desktop, Cursor, ChatGPT, Codex) to directly schedule, manage, and analyze social posts, rather than just drafting content.
Purpose: to enable AI agents to perform social media operations tasks across 11 social networks, including Instagram, TikTok, X, LinkedIn, YouTube, Facebook, Pinterest, Threads, Bluesky, Mastodon, and Telegram.
Main capabilities:
- Schedule and manage social posts;
- Generate post content (including the generate capability according to the official description);
- Analyze post performance;
- Operate through natural language instructions, such as "list my connected accounts", "schedule this post to be published to X and Bluesky at 9 AM tomorrow", "how are my recent Instagram posts performing?"
How to use:
- Generate an API key in Kadenzo: Settings → API keys (studio.kadenzo.app/dashboard/settings?section=api). The API is only available on paid plans.
- Add the server to the MCP client. Claude Desktop uses claude_desktop_config.json, and Cursor uses ~/.cursor/mcp.json.
- Restart the client, then issue the above natural language instructions to the agent.
Technical details and limitations:
- Posts are schedule-only mode; a future scheduled_for time must be provided, and they will be automatically published at that time.
- Requires Node 18+ (uses the built-in fetch / FormData).
- The API base address can be overridden via KADENZO_API_BASE; the default value is https://studio.kadenzo.app/api/v1。
- More information and the full API reference:https://studio.kadenzo.app/developers and https://kadenzo.app。
Applicable scenarios: suitable for operations staff or developers who want to automate the scheduling, publishing, and analysis of multi-platform social media through AI agents.
Limitations: the API requires a paid plan; posts can only be scheduled, not published immediately; the specific supported client configuration details are subject to the official documentation.
