Posterly vs Postmcp MCP Server
A side-by-side look at the Posterly and Postmcp MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Posterly for social media work as a local process; choose Postmcp MCP Server 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 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.
Choose Postmcp MCP Server when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
POSTMCPAI_API_KEY, POSTMCPAI_API_URL, POSTMCPAI_PROJECT_ID, PORT. - You want tools like
get_user_info, list_workspaces, get_connected_accounts.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 63/100 · Good | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | POSTERLY_API_KEY | POSTMCPAI_API_KEYPOSTMCPAI_API_URLPOSTMCPAI_PROJECT_IDPORT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 67 | 16 |
| Full listing | View Posterly | View Postmcp MCP Server |
Tools & capabilities
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
Postmcp MCP Server tools 16
get_user_infoRetrieve details of the logged-in user including subscription plan, credit balance, AI token count, the active workspace, and the caller's role in it.list_workspacesList every workspace (project) the user belongs to, with the id to pass as workspaceId, the caller's role, and which one is the default. Call this first whenever the user mentions a client, brand, or workspace by name.get_connected_accountsList every connected social profile in the workspace with the profileId needed to target it. Call this before creating a post so the post reaches the intended profile rather than every account on a platform.get_account_healthReport connections whose access token has expired or is about to, and which therefore need the user to reconnect. Check this before scheduling anything far out - a post scheduled onto a dead connection fails silently at publish time.list_brandingsList the workspace's brand kits: tone of voice, audience, keywords, and reference style images. Use one to keep drafted copy on-brand, and pass its id to generate_image for on-brand visuals.list_postsRetrieve scheduled, published, draft, and failed posts, newest first, with per-profile delivery status. Every profile that received a post carries `url`, the link to the live copy - give the user that link when they ask where a post went. Returns pagination plus counts per status.get_postFetch a single post by id, including per-profile delivery status, the live URL of each published copy, and the error for any profile that failed.preflight_postDry-run a post before creating it: checks copy against each platform's character limit, flags profiles that are not connected or need reconnecting, warns when a platform requires media, reports each target's video limit when a video is attached, and reports the credit cost against the workspace balance. Costs nothing and publishes nothing. Run this before create_post whenever the copy is long, carries a link, or targets several platforms.create_postSchedule or immediately publish a post to specific connected social profiles. Prefer targetAccounts so the post lands only on the profiles you name. Every targeted profile becomes its own post with its own id, so each can be edited, retried or cancelled on its own - the response lists them all. With publishImmediately, each delivered profile comes back with a `url` to the live copy; pass those on to the user.publish_post_nowBroadcast an existing scheduled post immediately to its platforms. Also the way to retry a failed post: profiles that already received it are skipped, so only the stragglers go out. The returned post carries a `url` per delivered profile - report those links rather than only saying it published.delete_postCancel and delete a scheduled or failed post from the database.update_postUpdate the fields (content, target profiles, schedule date/time) of an existing post. To move a post to a different slot without touching anything else, use reschedule_post.- +4 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.
Posterly
{
"mcpServers": {
"posterly-2": {
"command": "npx",
"args": [
"-y",
"posterly-mcp-server@latest"
],
"env": {
"POSTERLY_API_KEY": "YOUR_POSTERLY_API_KEY_HERE"
}
}
}
}
Postmcp MCP Server
{
"mcpServers": {
"postmcp-mcp-server": {
"command": "npx",
"args": [
"-y",
"@postmcpai/server"
],
"env": {
"POSTMCPAI_API_KEY": "YOUR_POSTMCPAI_API_KEY_HERE",
"POSTMCPAI_API_URL": "YOUR_POSTMCPAI_API_URL_HERE",
"POSTMCPAI_PROJECT_ID": "YOUR_POSTMCPAI_PROJECT_ID_HERE",
"PORT": "YOUR_PORT_HERE"
}
}
}
}
Frequently asked questions
Posterly is categorized under Social Media and uses a local stdio subprocess. Postmcp MCP Server belongs to Social Media and uses a local stdio subprocess. Pick Posterly for social media work and Postmcp MCP Server 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.
Posterly has no declared pricing — check the project's own site. Postmcp MCP Server 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 posterly-2 and postmcp-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Posterly has a quality signal of 63/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Postmcp MCP Server has 61/100 (Good) with 2 views, 0 installs and 0 GitHub stars.