Postmcp MCP Server vs SocialRainbow

A side-by-side look at the Postmcp MCP Server and SocialRainbow MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Postmcp MCP Server logoPostmcp MCP ServerSocial Media · Local subprocess (stdio)Publish and schedule posts to LinkedIn, X, Facebook, Instagram, Threads, Bluesky and YouTube Shorts.61GoodAuth: not declared
S
SocialRainbowSocial Media
Draft, validate, publish, schedule, and manage social posts across connected accounts.37FairAuth: not declared

Verdict: choose Postmcp MCP Server for social media work as a local process; choose SocialRainbow for social media. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Postmcp MCP Server logoChoose 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.
Explore Postmcp MCP Server

S
Choose SocialRainbow when

  • You need dedicated capabilities in the Social Media domain.
Explore SocialRainbow

Feature & specification comparison

Rows where the two servers differ are marked.

SpecPostmcp MCP Server logoPostmcp MCP Server
S
SocialRainbow
CategorySocial MediaSocial Media
Quality signal61/100 · Good37/100 · Fair
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsPOSTMCPAI_API_KEYPOSTMCPAI_API_URLPOSTMCPAI_PROJECT_IDPORTNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars0—
Directory activity 2 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools16Not listed

Tools & capabilities

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

SocialRainbow tools

No tool names declared yet. Check the project README from 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.

Postmcp MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "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"
      }
    }
  }
}

SocialRainbow

No confirmed install command for SocialRainbow yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Postmcp MCP Server is categorized under Social Media and uses a local stdio subprocess. SocialRainbow belongs to Social Media and uses an install path we have not confirmed yet. Pick Postmcp MCP Server for social media work and SocialRainbow 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. SocialRainbow has no confirmed install command yet — follow its own setup instructions.

Postmcp MCP Server has no declared pricing — check the project's own site. SocialRainbow 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 postmcp-mcp-server and socialrainbow as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Postmcp MCP Server has a quality signal of 61/100 (Good) with 2 views, 0 installs and 0 GitHub stars. SocialRainbow has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.