Kadenzo MCP vs Posterly
A side-by-side look at the Kadenzo MCP and Posterly MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kadenzo MCP for social media work as a local process; choose Posterly for social media as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Kadenzo MCP when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
KADENZO_API_KEY. - You want tools like
list_accounts, schedule_post, list_posts.
Choose Posterly when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
POSTERLY_API_KEY. - You want tools like
get_agent_signup_info, start_signup, get_signup_session.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 61/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | KADENZO_API_KEY | POSTERLY_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 6 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 23 | 67 |
| Full listing | View Kadenzo MCP | View Posterly |
Tools & capabilities
Kadenzo MCP tools 23
list_accountsList the social accounts connected to this Kadenzo workspace — returns each account id, platform, and username. Use the ids as account_ids when scheduling.schedule_postSchedule a social post to one or more connected accounts for a FUTURE time (it publishes automatically). Set validate_only=true to check accounts/limits/timing without scheduling.list_postsList your posts, newest first. Optionally filter by status (comma-separated, e.g. "pending,posted") and paginate with limit (1-100) and offset.get_postGet one post: roll-up status, per-channel outcome, and any options/thread that were set on it.update_postEdit a post that has not published yet — change content, accounts, time, media, options, or thread.cancel_postCancel a scheduled post before it publishes. Already-published posts cannot be cancelled.upload_mediaUpload a local image or video file and get a hosted URL to use in media_urls when scheduling.get_account_analyticsRecent posts and their engagement metrics for one connected account (likes, comments, views, etc.). The reliable analytics surface.get_post_analyticsPer-channel engagement metrics for a specific post you scheduled (best-effort; use get_account_analytics for the full picture).generate_contentGenerate post copy for a platform from a topic — great for a "generate then schedule" flow. Returns a caption/post/description you can feed into schedule_post. Platform must be one of: instagram, tiktok, snapchat, facebook, youtube.get_best_timesPersonalized best posting times for one connected account, computed from its own engagement history. Requires the Professional plan or higher. Hours are UTC; shift to the poster’s timezone. Use it to pick scheduled_for.list_mentionsYour social-listening mentions — who is talking about the keywords you track (reddit/bluesky/youtube/hackernews/…), newest first. Filter by platform, since (ISO), or unread.- +11 more on the listing page
Posterly tools 67
get_agent_signup_infoExplain how to use posterly MCP for agent-led signup before an API key exists, including the safe human-in-the-browser boundaries.start_signupStart the public posterly paid signup flow for a user before posterly API access exists. Returns a signup poll URL, a browser Checkout fallback URL, and, when enabled, a prepaid PaymentIntent the agent can pay with a Link Agent Wallet virtual card (credential_type: card). The user still sets a password and approves social OAuth in the browser. Never ask for card numbers, a posterly password, or social passwords in chat.get_signup_sessionPoll a public posterly signup session created by start_signup. Use this to narrate payment (Link virtual card or browser Checkout), password setup, and agent access status before a posterly API key is installed. Keep updates user-facing; do not narrate raw HTTP, curl, or API plumbing.whoamiWho you are and how posterly is connected. view=identity (default): the authenticated user, API key scopes, workspaces, and onboarding next step. ALWAYS call this at the start of a session; if onboarding.completed is false, walk the remaining onboarding steps IN THIS conversation (about you, connect, brand voice, first post) and do not send the user to /onboarding-v2 or the dashboard composer wizard. view=status: MCP server version, latest npm version, endpoint and API key health, and update guidance; works before POSTERLY_API_KEY is configured.list_accountsConnected social accounts and what posterly has learned about them. view=accounts (default): connected accounts, optionally one workspace_id or one account_id; Instagram rows identify direct-login versus Meta-linked connections and whether native media tags/collaborators are available, so check this before Instagram user_tags or collaborators. view=learned_voice (account_id): the voice learned from the account's real published captions (summary, traits, style guidelines, habits); read-only, never overwrites the saved brand profile. view=performance_profile (account_id): 90-day coaching stats, engagement-rate trend, and summary (Pro plan or higher; platforms without per-post analytics never get one). view=connect_session (session_id): poll a session from create_connect_session and keep the user updated in plain language; stop when status is connected, failed, cancelled, or expired.disconnect_accountDisconnect a connected social account from posterly. DESTRUCTIVE and IRREVERSIBLE: removes the account connection, emits account.disconnected webhooks, and may transfer Instagram scheduled posts to a replacement account. REQUIRED BEFORE CALLING: Call `list_accounts` first, show the user the exact platform, username, account ID, and workspace that will be disconnected, then get explicit confirmation. Pass confirm=true only after that confirmation.connect_accountConnect a credential-based social account (telegram, bluesky, discord, wordpress, devto, hashnode, lemmy) directly, without a browser session. Call list_platforms with view=connect_link first to discover the exact credential fields the platform needs. Prefer scoped secrets: app passwords (Bluesky, WordPress), bot tokens (Telegram), webhook URLs (Discord), and API tokens (Dev.to, Hashnode) over primary passwords. Warn the user that any credential they share passes through this conversation. For OAuth platforms (Instagram, X, LinkedIn, ...) use create_connect_session instead.create_connect_sessionCreate a short-lived posterly dashboard handoff session for connecting a social account. Send the secure connection URL to the user, then poll list_accounts with view=connect_session to narrate progress. Do not ask for social media passwords or OAuth codes; posterly handles those browser steps.create_api_keyCreate a new posterly API key for the authenticated user. SECRET-CREATING WRITE: only use after explicit user confirmation. The new key can only request scopes already present on the calling dashboard-created API key; OAuth and managed assistant tokens cannot mint keys. Team management (members:read, members:write) and client portal sign-in link permissions are never copied or granted here: a person turns them on in /dashboard/api.delete_api_keyRevoke a posterly API key owned by the authenticated user. DESTRUCTIVE: call whoami or use a known key ID, show the user the exact key ID/prefix/name if available, and get explicit confirmation before calling. Cannot revoke the key currently authenticating this request, OAuth-issued keys, or managed assistant keys.list_workspace_membersList the people in a workspace: members (with role, status, brand access and API access) and pending invites, plus seats in use. API access says whether a teammate can use this workspace's API plan from their own keys and AI apps; owners and admins also see each member's key count, connected AI apps and last use. Needs an API key with the Manage team permission. Any workspace member can list; brand-limited teammates only see brand ids they can access.manage_workspace_memberInvite, update, or remove a workspace colleague. This SENDS EMAILS and CHANGES WHO CAN ACCESS the workspace. Needs an API key with the Manage team permission, and the caller must be a workspace owner or admin. ALWAYS preview first: call without confirm, show the preview to the user, and only call again with confirm: true plus the returned preview_id after the user explicitly approves. action=invite: email and role required (publisher, editor or viewer), optional brand_ids and resend; always sends a pending invite email, never adds anyone instantly. action=update: member_id or invite_id (from list_workspace_members) plus role and/or brand_ids; or member_id plus api_access (true or false, on its own) to turn API and AI app access on or off for that teammate, which lets them use the workspace API plan from their own keys and AI apps (off by default; you cannot change your own; only the owner can change it for an admin; turning it off stops their keys, AI app connections and webhooks for this workspace). action=remove: member_id (removes the teammate and revokes their API keys for this workspace) or invite_id (cancels a pending invite). Admin seats can only be granted in the posterly dashboard. The workspace owner is emailed about every change.- +55 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Kadenzo MCP
{
"mcpServers": {
"kadenzo-kadenzo-mcp": {
"command": "npx",
"args": [
"-y",
"kadenzo-mcp"
],
"env": {
"KADENZO_API_KEY": "YOUR_KADENZO_API_KEY_HERE"
}
}
}
}
Posterly
{
"mcpServers": {
"posterly-2": {
"command": "npx",
"args": [
"-y",
"posterly-mcp-server@latest"
],
"env": {
"POSTERLY_API_KEY": "YOUR_POSTERLY_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Kadenzo MCP is categorized under Social Media and uses a local stdio subprocess. Posterly belongs to Social Media and uses a local stdio subprocess. Pick Kadenzo MCP for social media work and Posterly for social media.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Kadenzo MCP is listed as a paid service. Auth: api key required. Posterly has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add kadenzo-kadenzo-mcp and posterly-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kadenzo MCP has a quality signal of 61/100 (Good) with 6 views, 0 installs and 0 GitHub stars. Posterly has 63/100 (Good) with 1 views, 0 installs and 0 GitHub stars.