Postraid MCP server

Postraid MCP

From product brief to a reviewed social-content library.

Postraid helps founders, creators and growth marketers turn product context into social content. Start with a website or product brief, explore reactions, memes and carousels, then keep the ideas that fit the brand. The application combines a content library, creative review and publishing calendar so approved work has a place to go next.

Website · MCP repository · Agent skill · npm package

What this connector does

This package connects a local stdio MCP client to the hosted Postraid MCP server. Hosted tools run on Cloudflare; the local package bridges the connection and opens browser-based OAuth. You do not need to deploy a Worker or paste a product password into your assistant.

The MCP reads the user’s own workspace, not team workspaces. Its posts are saved content pieces, not a delivery ledger proving that a social post went live. Draft creation does not generate backgrounds, render media, schedule, publish or spend credits. Replace placeholder backgrounds and review the result in the product. Reach, sales and viral performance are not guaranteed.

Example workflow

1. Choose the owned brand and inspect existing content to avoid repeating the same idea.
2. Prepare a title, one to ten slides and hashtags that match the supplied product brief.
3. Save the requested carousel draft, return its editor link, and review copy and backgrounds in Postraid before scheduling.

Things to ask your assistant

List my brands, then show the saved content for the brand I select.

Review this saved carousel and suggest a clearer opening based on my product brief.

Save these five slides as an editable carousel draft. Return its editor link without generating media or publishing.

Connect a remote MCP client

1. Open the client’s custom MCP or connector settings.
2. Enter https://mcp.postraid.com/mcp as the remote server URL.
3. Complete Postraid sign-in in your browser and review the permissions on the consent screen.
4. Return to the client and load the available tools.

Use a client that supports Streamable HTTP MCP and OAuth. Custom-connector availability depends on the client and your account. A public repository or npm release does not mean the integration has been approved for a client’s marketplace.

Claude Desktop and other stdio clients

Requires Node.js 22 or newer and an existing Postraid account. Add this entry to your client’s MCP configuration:

{
  "mcpServers": {
    "postraid": {
      "command": "npx",
      "args": [
        "-y",
        "postraid-mcp"
      ]
    }
  }
}

You can also run npx -y postraid-mcp from a terminal to start the bridge. It speaks MCP over stdio; it is not an interactive chat interface. For desktop clients that support MCPB extensions, download the .mcpb file from Postraid releases.

Permissions and account access

Requested scopes: profile:read content:read drafts:write. Older profile-only connections need to reconnect and explicitly approve the additional permissions before content tools are available.

Only approve a connection you intended to start. If sign-in opens a new tab, finish it, return to the consent screen and refresh. Manage or revoke connected apps.

Shortened. The full README is on GitHub.