Postforme MCP Pro

What helbertparanhos/postforme-mcp-pro MCP server does

The helbertparanhos/postforme-mcp-pro MCP server connects MCP clients to the Post for Me API. It provides typed operations for nine social platforms: Instagram, Facebook, TikTok, YouTube, X, LinkedIn, Pinterest, Bluesky, and Threads. The available operations cover account connections, post creation, scheduling, drafts, editing, deletion, media handling, previews, analytics, and webhook management.

Posts can target multiple connected accounts. The server includes direct operations such as create_post, publish_now, schedule_post, and create_draft, so an agent can choose between immediate publishing, ISO-8601 scheduling, or saving content without publishing. Account tools can list and retrieve connected accounts, start an OAuth connection flow, update account details, and disconnect accounts.

How it works

The server makes authenticated requests to the Post for Me API using a bearer API key. Most API operations are represented by individual MCP tools with typed inputs. The upload_media shortcut accepts a local file path or remote URL, performs the upload flow, and returns a media_url that can be attached to a post. For clients that need the explicit two-step process, create_media_upload_url returns a signed upload URL.

Post previews can show how content renders for different platforms before publication. After publishing, list_post_results and get_post_result expose per-platform outcomes, while list_account_feeds provides recent feed and engagement data for an account. The postforme_raw tool can call a /v1/... endpoint with a method, path, parameters, and body, extending coverage to endpoints that do not have dedicated tools.

Setup and configuration

The package can be run from npm with npx -y postforme-mcp-pro, or built locally after installing dependencies with npm and running the project build. The required POSTFORME_API_KEY identifies the Post for Me account. POSTFORME_BASE_URL can override the default https://api.postforme.dev endpoint.

Optional settings include POSTFORME_READONLY=true, which blocks write tools and allows read operations plus GET use of postforme_raw. POSTFORME_DISABLE_RAW=true removes the raw endpoint tool. POSTFORME_TIMEOUT_MS controls the request timeout, and POSTFORME_MAX_RETRIES controls retries for rate limits, server errors, and network failures. The documented defaults are 60,000 milliseconds and three retries.

The README provides local configurations for Claude Desktop and Cursor. Both invoke the built server with Node.js and pass POSTFORME_API_KEY through the process environment.

Tools and capabilities

• Manage social accounts and OAuth connection URLs.
• Publish immediately, schedule posts, create drafts, reschedule, edit, and delete.
• Preview platform-specific rendering and inspect publish results.
• Upload local files or remote media URLs.
• Read account feeds and engagement metrics.
• Create, list, update, retrieve, and delete webhooks.
• Use postforme_raw for direct /v1/... API requests.

The server also models platform-specific configuration options, including examples such as Instagram Reels, X polls, TikTok privacy, and YouTube visibility.

Limitations and notes

A Post for Me API key is required. The server's social actions depend on connected accounts and the capabilities of the Post for Me API. Readonly mode is useful for analytics or inspection sessions, but it prevents publishing and other write operations. The raw tool can be disabled independently. Media uploads use remote-fetch protections described by the project, including public-unicast IP validation, no redirects, and a size limit.