1Social vs Postforme MCP Pro
A side-by-side look at the 1Social and Postforme MCP Pro MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose 1Social for social media work as a local process; choose Postforme MCP Pro 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 1Social when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_accounts, preview_post, publish_post.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 49/100 · Fair | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | POSTFORME_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 10 | 22 |
| Full listing | View 1Social | View Postforme MCP Pro |
Tools & capabilities
1Social tools 10
list_accountsConnected accounts, what each network accepts, current plan, remaining quota. Call it first — channel ids come from here.preview_postFree dry run: per-network limits, media requirements, threading behaviour, quota cost. Nothing is published.publish_postPublishes now, or schedules up to 30 days ahead. Returns a per-network receipt. Takes an `idempotencyKey`.list_postsPosts with their delivery outcome per network — delivered, failed with a reason, cancelled, or `unknown` — plus stored engagement metrics.update_postEdits a post that has not been sent yet. The networks have no edit endpoint, so it withdraws and replaces.cancel_postUnschedules a post and releases the quota it reserved.delete_postDeletes from 1Social and attempts removal from each network. See [What deletion can and cannot do](#what-deletion-can-and-cannot-do).retry_deliveryRetries one failed network, leaving the successful ones alone. Refused for permanent failures.upload_mediaPre-signed upload target, for clients that cannot attach a file to a tool call.confirm_deliveryRecords **your** answer about a delivery whose outcome was unknown: is the post live on that network or not?
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
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.
1Social
{
"mcpServers": {
"1social": {
"command": "npx",
"args": [
"-y",
"@lobehub/market-cli"
]
}
}
}
Postforme MCP Pro
{
"mcpServers": {
"helbertparanhos-postforme-mcp-pro": {
"command": "npx",
"args": [
"-y",
"postforme-mcp-pro"
],
"env": {
"POSTFORME_API_KEY": "YOUR_POSTFORME_API_KEY_HERE"
}
}
}
}
Frequently asked questions
1Social is categorized under Social Media and uses a local stdio subprocess. Postforme MCP Pro belongs to Social Media and uses a local stdio subprocess. Pick 1Social for social media work and Postforme MCP Pro 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.
1Social has no declared pricing — check the project's own site. Postforme MCP Pro is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. 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 1social and helbertparanhos-postforme-mcp-pro as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, 1Social has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Postforme MCP Pro has 61/100 (Good) with 5 views, 0 installs and 1 GitHub stars.