Postmcp MCP Server logo

Postmcp MCP Server

Publishes, schedules, manages, and analyzes social posts across seven platforms through MCP tools.

Install Postmcp MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "postmcp-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@postmcpai/server"
      ],
      "env": {
        "POSTMCPAI_API_KEY": "YOUR_VALUE_HERE",
        "POSTMCPAI_API_URL": "YOUR_VALUE_HERE",
        "POSTMCPAI_PROJECT_ID": "YOUR_VALUE_HERE",
        "PORT": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 16 tools correctly (5d ago).

Overview

postmcp-mcp-server MCP server connects AI assistants and developer workflows to PostMCP AI for social publishing. It supports LinkedIn, X, Facebook, Instagram, Threads, Bluesky, and YouTube Shorts through stdio or Streamable HTTP. Tools cover workspace and account discovery, validation, publishing, scheduling, media handling, retries, deletion, and analytics. Reach for it when an agent needs to manage multi-platform publishing without implementing each platform workflow separately.

Use cases

  • Publish one post across connected social profiles
  • Schedule and reschedule campaign content
  • Validate media, limits, targets, and credit costs before publishing
  • Inspect delivery status and refresh post analytics
  • Upload or import media for social posts

Key features

  • Publishing and scheduling across seven social platforms
  • Preflight validation for limits, media, targets, and cost
  • Post, profile, workspace, and account-health tools
  • Carousel and multi-image publishing with mediaUrls
  • Stdio and Streamable HTTP transport modes
  • OpenAPI and REST endpoints for ChatGPT Custom GPTs

Tools16

What Postmcp MCP Server lets your agent do. Expand a tool for its parameters.

Verified live~4.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 40d

What it can do

From the 16 tools this server returned when we ran it.

Can delete or modify data · 1Handles credentials · 3Makes network requests · 6Read-only tools · 15
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age45 days
Maintainers1

Observed 2026-10-18 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · @postmcpai/server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads145Package downloads in the last 30 days.
Last commit22d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed16Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Postmcp MCP Server works

What postmcp-mcp-server MCP server does

The postmcp-mcp-server MCP server exposes PostMCP AI's social media publishing API to MCP-compatible clients. It can work with LinkedIn, X, Facebook, Instagram, Threads, Bluesky, and YouTube Shorts. Agents can inspect workspaces and connected profiles, check account token health, validate a post before publishing, create drafts, publish immediately, schedule content, reschedule or retry posts, and delete scheduled or failed posts.

The server also provides profile and post analytics, including stored metrics and optional refreshed network data. Media workflows cover generated images, direct uploads, and importing public image or video URLs. Multiple media URLs can be used for platform-specific carousels, galleries, or multi-photo posts.

How it works

The postmcp-mcp-server MCP server uses the PostMCP AI backend and supports two transport modes. Without a PORT setting, it runs in stdio mode for local desktop applications and IDEs. Setting PORT starts remote Streamable HTTP mode, which is intended for web services, Claude.ai, and remote connectors.

Authentication can come from the POSTMCPAI_API_KEY environment variable, an apikey URL query parameter, or HTTP API-key and bearer-token headers. The API key identifies a workspace by default. Tools accept an optional workspaceId when an account needs to act on another workspace, and a connection-level or process-level project identifier can also be configured.

Each profile targeted by a publishing operation receives its own post record and status. The preflight_post tool checks content limits, media requirements, target connections, carousel limits, and estimated credit cost without publishing anything. Existing posts can then be published, updated, rescheduled, retried, reset when stuck, or removed.

Setup and configuration

Provide a PostMCP AI API key through POSTMCPAI_API_KEY. The backend URL defaults to https://api.postmcpai.com; POSTMCPAI_API_URL is available for a self-hosted or local backend. POSTMCPAI_PROJECT_ID can override the workspace associated with the key, although a tool-level workspaceId takes precedence. Set PORT to use remote Streamable HTTP mode; otherwise the default is stdio.

The repository also includes OpenAPI generation at /openapi.json and REST tool routes under /api/tools/:name for ChatGPT Custom GPT integrations. OAuth with PKCE and RFC 9728 is available for deployments using the documented production OAuth settings, while API-key clients remain supported.

For local media, request a signed upload URL, send the raw file bytes to that URL, then register the upload with complete_media_upload. The signed URL normally expires after 900 seconds. Public files can instead be copied into the media library with import_media_from_url.

Tools and capabilities

The tool set includes:

  • Workspace, user, connected-account, and token-health inspection.
  • Post queue listing, full post details, per-profile delivery status, and analytics.
  • Preflight validation plus create, update, publish, schedule, reschedule, retry, reset, and delete operations.
  • Image generation, signed media uploads, upload completion, and public-URL imports.
  • Per-profile and per-post analytics, with optional live refreshes that consume credits.
  • Workspace-aware operations and multi-image publishing through mediaUrls.

Limitations and notes

A valid PostMCP AI API key is required for the standard configuration. Image generation is limited to paid plans and costs 20 credits. Refreshing profile or post analytics costs one credit, while reading stored analytics is free. Local file uploads require the MCP client to support an HTTP upload step; creating an upload URL alone does not transfer or verify the file. Media URLs must meet the destination platform's requirements, and the preflight tool should be used to identify platform-specific limits before publishing.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Postmcp MCP Server

postmcp-mcp-server is an MCP server that connects AI clients to PostMCP AI for publishing on LinkedIn, X, Facebook, Instagram, Threads, Bluesky, and YouTube Shorts. Its main tools manage workspaces and accounts, validate and schedule posts, publish or retry content, handle media, and retrieve post or profile analytics.

Configure the server with a PostMCP AI API key and choose stdio or Streamable HTTP mode.

Yes, postmcp-mcp-server is listed as supporting Cursor. It also supports Claude Desktop and can run through stdio for local desktop and IDE workflows or Streamable HTTP for remote connections.

Request a signed URL with create_media_upload_url, PUT the raw file to that URL, then call complete_media_upload with the returned metadata. Use the resulting media URL in create_post or update_post; public files can instead be imported with import_media_from_url.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPostmcp MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/postmcp-mcp-server?style=directory)](https://allmcps.com/mcp/postmcp-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/postmcp-mcp-server"><img src="https://allmcps.com/api/badge/postmcp-mcp-server?style=directory" alt="Postmcp MCP Server on AllMCPs" /></a>