Postforme MCP Pro vs SocialHive
A side-by-side look at the Postforme MCP Pro and SocialHive MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Postforme MCP Pro for social media work as a local process; choose SocialHive for social media over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Postforme MCP Pro 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:
POSTFORME_API_KEY. - You want tools like
list_social_accounts, get_social_account, create_social_account.
Choose SocialHive when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
list_channels, get_connected_social_accounts, list_posts.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 61/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | POSTFORME_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 22 | 24 |
| Full listing | View Postforme MCP Pro | View SocialHive |
Tools & capabilities
Postforme MCP Pro tools 22
list_social_accountsList connected accounts (filter by platform/username).get_social_accountGet one account by id.create_social_accountConnect an account by supplying credentials.update_social_accountUpdate stored credentials/metadata.create_auth_urlStart the OAuth connect flow (returns a URL).disconnect_social_accountRevoke access for an account.list_account_feedsAnalytics:** recent feed + engagement metrics for an account.create_postCreate a post (publish now, schedule, or draft) across accounts.publish_nowShortcut: publish immediately.schedule_postShortcut: schedule for an ISO-8601 time.create_draftShortcut: save as draft.get_postGet a post by id.- +10 more on the listing page
SocialHive tools 24
list_channelsList the social accounts connected to this workspace with their ids, platform, handle, health, and automationEnabled status. Use channel ids when creating posts.get_connected_social_accountsGet all connected social media accounts (LinkedIn, X, YouTube, Instagram, Facebook, TikTok, Threads) for the workspace with account IDs, platforms, connection status, and automationEnabled status.list_postsList posts in the workspace, newest first. Filter by status (draft, pending_approval, scheduled, published, failed) or free text.get_postGet one post with its body, per-channel variants, status and metrics.list_articlesList long-form articles in the workspace library with their id, title, status, word count, summary, and last updated time.get_articleGet full details and Markdown body of an article in the workspace library by its ID.get_analyticsWorkspace performance for the last N days: impressions, engagements, posts, follower change, top posts and recommended posting slots.list_sourcesList content data sources (RSS feeds, sitemaps, web pages, documents) with counts of unused items.search_source_itemsFetch recent items from one data source (title, url, excerpt). Use them as raw material for posts.list_workflowsList automation workflows with status and last run.list_node_typesCatalog of workflow node types (triggers, sources, AI, control, destinations) with their config schemas. Read before calling propose_workflow.generate_textWrite social copy in the workspace brand voice. Returns one or more variants. Metered (free daily allowance, then 1 credit).- +12 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.
Postforme MCP Pro
{
"mcpServers": {
"helbertparanhos-postforme-mcp-pro": {
"command": "npx",
"args": [
"-y",
"postforme-mcp-pro"
],
"env": {
"POSTFORME_API_KEY": "YOUR_POSTFORME_API_KEY_HERE"
}
}
}
}
SocialHive
{
"mcpServers": {
"socialhive": {
"url": "https://platform.socialhive.pro/api/mcp"
}
}
}
Frequently asked questions
Postforme MCP Pro is categorized under Social Media and uses a local stdio subprocess. SocialHive belongs to Social Media and uses a remote HTTP/SSE transport. Pick Postforme MCP Pro for social media work and SocialHive 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.
Postforme MCP Pro is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. SocialHive 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 helbertparanhos-postforme-mcp-pro and socialhive as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Postforme MCP Pro has a quality signal of 61/100 (Good) with 5 views, 0 installs and 1 GitHub stars. SocialHive has 57/100 (Good) with 0 views, 0 installs and 0 GitHub stars.