Postwire MCP

What Perufitlife/postwire-mcp MCP server does

Perufitlife/postwire-mcp MCP server exposes PostWire’s social publishing workflow to MCP-compatible clients. An agent can start with one idea or prompt, request platform-specific drafts, review or edit those drafts, and then publish them through PostWire. Supported destinations listed in the project include TikTok, Instagram, YouTube, X, LinkedIn, Reddit, Facebook, Bluesky, Mastodon, Telegram, and Discord.

The server is designed for cases where the same campaign needs different content formats. Generated output can include separate text, titles, and tags for each platform. The examples describe YouTube titles and tags, short hook-first captions for TikTok, professional LinkedIn formatting, reply-based links for X, and platform-specific hashtag conventions.

How it works

The normal workflow has two stages. First, call generate_posts with a prompt and optional media. The response contains a draft for each requested platform. The agent can then pass those drafts to post_to_social using the per_platform input. A simpler single-text input is also available when identical copy is acceptable.

Publishing happens through PostWire, which manages the connected network accounts. The project documentation says validation occurs before publishing, including checks for missing media, excessive text length, and accounts that have not been connected. Results are returned per platform, and identifiers from those results can be used with get_post_status. TikTok and YouTube may report asynchronous processing states.

Setup and configuration

Install the server in an MCP client with npx -y postwire-mcp. Set the POSTWIRE_API_KEY environment variable to an API key obtained from the PostWire dashboard. Social accounts must also be connected in that dashboard before the server can publish to them.

PostWire’s setup flow uses OAuth for the platforms described as OAuth-based. Bluesky, Mastodon, Telegram, and Discord are listed as using a token or webhook. The server itself communicates with PostWire using the API key rather than requiring each platform credential in the MCP client configuration.

The project documentation includes setup guidance for Claude Desktop, Claude Code, Cursor, VS Code, and Windsurf. list_platforms can be called without an API key, allowing supported networks and required fields to be inspected before account setup.

Tools and capabilities

• generate_posts creates separate drafts for each platform from one prompt and optional media. Draft results may contain text, a title, and tags.
• post_to_social publishes to one or more connected platforms, either with one shared text value or platform-specific drafts.
• get_post_status checks the processing or publishing state of a post created through post_to_social.
• list_platforms reports supported networks and the fields required by each one. This tool works without a key.
• my_account reports the PostWire plan, monthly usage, and connected platforms.

Perufitlife/postwire-mcp MCP server also reflects PostWire’s account-based pricing model. The documented free plan includes one brand and 30 posts per month, while paid plans increase the number of brands and monthly posts. The API and MCP workflow are backed by the same PostWire service.

Limitations and notes

Publishing depends on the relevant account being connected in PostWire and on satisfying each platform’s content requirements. Media-required networks need suitable media, and text exceeding a platform limit is rejected before dispatch. A generated draft is not automatically published; the intended workflow separates generation and review from the publishing call.

The repository documents a REST alternative for clients that do not run MCP, but that endpoint is separate from the MCP client configuration. Perufitlife/postwire-mcp MCP server requires a PostWire API key for account and publishing operations, and the available features depend on the platforms and credentials configured in PostWire.