Skip to main content
Glama
PostMCP MCP Server

PostMCP MCP Server

Official

PostMCP AI Model Context Protocol (MCP) Server

npm version License: MIT MCP Compatible

Official PostMCP AI Model Context Protocol (MCP) Server. Connect your social media publishing pipelines directly into AI assistants, desktop applications, IDE workflows, and web environments like Claude Desktop, Claude.ai, Cursor, and ChatGPT Custom GPTs.

Supported platforms include LinkedIn, X (Twitter), Facebook, Instagram, Threads, Bluesky, and YouTube Shorts.


šŸš€ Features & Capabilities

  • šŸ¤– 20 Built-in Tools: Workspaces, connected accounts and their token health, the post queue, pre-flight checks, create/schedule/reschedule/publish/retry/delete, per-post and per-profile analytics, media uploads, image generation, and batching.

  • šŸ–¼ļø Carousels & galleries: Pass mediaUrls to publish a carousel on Instagram and Threads, a multi-photo post on Facebook and LinkedIn, or a four-image gallery on X and Bluesky - one call, every network's ceiling checked up front.

  • ⚔ Dual Transport Modes: Native Stdio mode (for local desktop apps & IDEs) and Streamable HTTP mode (for web services, Claude.ai, and remote connectors).

  • šŸ”‘ Flexible Authentication: Auto-detects API key from environment variables (POSTMCPAI_API_KEY), URL query parameters (?apikey=YOUR_KEY), or HTTP authorization headers (x-api-key, Bearer token).

  • šŸ—‚ļø Multi-Workspace Aware: The API key carries its own workspace, so a bare key is enough. To act on another one, every tool takes an optional workspaceId, also settable per connection (?projectId=..., x-project-id) or per process (POSTMCPAI_PROJECT_ID).

  • šŸ¤– ChatGPT Actions Compatible: Includes built-in OpenAPI 3.0 specification generator (/openapi.json) and REST endpoints (/api/tools/:name) for ChatGPT Custom GPT integration.

  • šŸ”’ OAuth with PKCE and RFC 9728: Per-user consent, persistent encrypted grants, rotating tokens and DCR for ChatGPT/Codex. Requires the production settings in OAUTH.md; API-key clients remain supported.

  • 🧩 Installable plugin: Account onboarding, publishing, scheduling and analytics workflows. See PLUGIN.md and run npm run package:plugin.


Related MCP server: YaparAI Enterprise MCP Server

šŸ“ Repository Architecture

mcp-server/
ā”œā”€ā”€ bin/
│   └── cli.js            # Executable CLI entry point (Stdio / HTTP mode runner)
ā”œā”€ā”€ src/
│   ā”œā”€ā”€ config.js         # Centralized configuration & environment loader
│   ā”œā”€ā”€ client.js         # Backend API client, API key & workspace extraction
│   ā”œā”€ā”€ platforms.js      # Platform limits, credit pricing & post cost helper
│   ā”œā”€ā”€ tools/
│   │   ā”œā”€ā”€ definitions.js# MCP tool JSON schemas & parameter specifications
│   │   ā”œā”€ā”€ handlers.js   # MCP tool execution handlers
│   │   └── index.js      # Tool definitions aggregator
│   ā”œā”€ā”€ server.js         # MCP Server instance factory
│   ā”œā”€ā”€ routes/
│   │   ā”œā”€ā”€ oauth.js      # OAuth 2.0 & RFC 9728 discovery endpoints
│   │   ā”œā”€ā”€ openapi.js    # OpenAPI 3.0 schema & ChatGPT REST endpoints
│   │   ā”œā”€ā”€ mcpHttp.js    # MCP Streamable HTTP transport (/mcp)
│   │   └── health.js     # Health check & system metadata endpoints
│   ā”œā”€ā”€ app.js            # Express application factory
│   └── index.js          # Main library entry point
ā”œā”€ā”€ index.js              # Executable wrapper script
ā”œā”€ā”€ package.json
└── README.md

āš™ļø Environment Configuration

Environment Variable

Description

Default Value

POSTMCPAI_API_KEY

Required. Your secret API key from the PostMCP AI dashboard.

None

POSTMCPAI_API_URL

Backend API root. Only set for a self-hosted or local backend.

https://api.postmcpai.com

POSTMCPAI_PROJECT_ID

Optional. Overrides the workspace the API key is bound to. Overridden in turn by a call's workspaceId.

The workspace the API key was issued from

PORT

Setting this launches the server in Remote Streamable HTTP Mode.

None (Defaults to Stdio Mode)


šŸ› ļø MCP Tools Reference

Every tool below also accepts an optional workspaceId (from list_workspaces) to act on a specific workspace.

Reading

Tool Name

Description

Required

Optional

get_user_info

Authenticated user: plan, credit balance, active workspace and role.

—

workspaceId

list_workspaces

Every workspace the user belongs to, with ids, roles, and connected platforms.

—

—

get_connected_accounts

Connected social profiles with the profileId needed to target them.

—

workspaceId

get_account_health

Connections whose token expired or is close to it and need reconnecting.

—

workspaceId

get_profile_analytics

A connected profile's followers, following, post count and views from its network. Stored reading is free; refresh reads the network now for 1 credit.

platform, profileId

refresh

list_posts

Post queue, newest first, with per-profile delivery status, pagination and counts.

—

status, page, limit, all

get_post

One post in full: which profiles received it, live URLs, and per-profile errors.

id

—

get_post_analytics

Views, likes, comments, shares, saves and clicks per profile, plus the raw platform metrics. Stored reading is free; refresh reads the networks now for 1 credit.

id

refresh

Writing

Tool Name

Description

Required

Optional

preflight_post

Dry run: character limits, unconnected profiles, missing media, carousel ceilings, credit cost. Publishes nothing.

content

targetAccounts, platforms, mediaUrl, mediaUrls

create_post

Draft, schedule, or immediately publish a post to named profiles. Each profile becomes its own post with its own id. Several mediaUrls publish as a carousel.

content

targetAccounts, variants, platforms, publishImmediately, scheduleDate, scheduleTime, timezone, mediaUrl, mediaUrls, youtube

publish_post_now

Publish an existing post immediately; also retries a failed post, skipping delivered profiles.

id

—

update_post

Update content, target profiles, schedule, media, or status. mediaUrls replaces the whole attachment set.

id

content, targetAccounts, platforms, scheduleDate, scheduleTime, timezone, mediaUrl, mediaUrls, youtube, status

reschedule_post

Move a post to a new slot, keeping copy and targets. Re-arms failed and draft posts.

id, scheduleDate, scheduleTime

timezone

reset_stuck_post

Release a post stuck mid-publish so it can be retried. Delivered profiles keep their state.

id

force

delete_post

Cancel and delete a scheduled or failed post.

id

—

generate_image

Generate a post image and return its hosted URL for mediaUrl. Costs 20 credits; paid plans only.

prompt

styleImageUrl

create_media_upload_url

Authorize a direct image/video upload; returns a signed PUT URL and the future public URL.

fileName, contentType, fileSize

workspaceId

complete_media_upload

Register a successfully uploaded file in the media library and return mediaUrl.

url, key, fileName, contentType, fileSize

workspaceId

import_media_from_url

Copy a public image/video into storage and the media library; returns mediaUrl.

url

workspaceId

Media uploads

For a local file, the MCP client needs an HTTP upload capability:

  1. Call create_media_upload_url with fileName, contentType (MIME type), and fileSize (bytes). For example: { "fileName": "launch.png", "contentType": "image/png", "fileSize": 245760 }.

  2. PUT the raw file bytes to the returned uploadUrl with the returned headers. Do not send your PostMCP API key to storage. The URL expires after expiresIn seconds (normally 900); request another if it expires. The file is not uploaded merely by creating the URL.

  3. After the PUT succeeds, call complete_media_upload with the returned publicUrl as url, the returned key, and the same file metadata. Use the same workspaceId on both tools. This registers the file; it does not transfer or verify the bytes.

  4. Use the returned mediaUrl in create_post or update_post, or collect several URLs in mediaUrls for a carousel.

For an existing public file, call import_media_from_url with { "url": "https://example.com/launch.png" }. The backend downloads it and returns the stored mediaUrl in one call. The URL must serve the file directly without authentication; private-network URLs are rejected by the backend.

Storage supports PNG, JPEG, GIF, WebP, AVIF, HEIC, MP4, MOV, WebM and M4V, with a 25 MiB image ceiling and a 512 MiB video ceiling. Individual social platforms have stricter publishing requirements; use preflight_post before publishing. File bytes and base64 never travel through the MCP JSON request. If library registration fails after storage succeeds, the result includes librarySaved: false and a warning while preserving the usable mediaUrl.

Batching

Tool Name

Description

Required

Optional

multicall

Run up to 20 of the tools above in one request, in order. Tool names are validated before anything executes, so a typo cannot leave half a batch written. Cannot nest.

calls

stopOnError, workspaceId

{
  "calls": [
    { "id": "img", "tool": "generate_image", "arguments": { "prompt": "launch banner" } },
    {
      "tool": "create_post",
      "arguments": {
        "content": "We shipped it šŸš€",
        "targetAccounts": [
          { "platform": "linkedin", "profileId": "lin_7741903" },
          { "platform": "twitter", "profileId": "tw_1293847", "content": "We shipped it šŸš€" }
        ],
        "scheduleDate": "2026-09-01",
        "scheduleTime": "10:00",
        "timezone": "Asia/Kolkata"
      }
    }
  ],
  "stopOnError": true
}

The reply carries one entry per call — { id, tool, ok, result } or { id, tool, ok: false, error } — plus counts and, when a failure stopped the batch, the calls that were skipped.

Carousels

mediaUrls is the ordered attachment set. One URL is an ordinary media post; two or more publish as a multi-media post on every network but YouTube, with the first URL as the cover:

Platform

Items per post

Video in a set of several?

Lands as

Instagram

2–10

yes

Carousel

Threads

2–20

yes

Carousel

Facebook

up to 10

no

Multi-photo post

LinkedIn

up to 20

no

Multi-image post

X / Twitter

up to 4

no

Gallery on one tweet

Bluesky

up to 4

no

Gallery on one post

YouTube

1

—

One video per upload

{
  "content": "Five things we learned shipping v2 šŸ‘‰",
  "targetAccounts": [
    { "platform": "instagram", "profileId": "17841400000000" },
    { "platform": "threads", "profileId": "9988776655" },
    { "platform": "twitter", "profileId": "tw_1293847",
      "mediaUrls": ["https://cdn.example.com/v2/1.png", "https://cdn.example.com/v2/2.png", "https://cdn.example.com/v2/3.png", "https://cdn.example.com/v2/4.png"] }
  ],
  "mediaUrls": [
    "https://cdn.example.com/v2/1.png",
    "https://cdn.example.com/v2/2.png",
    "https://cdn.example.com/v2/3.png",
    "https://cdn.example.com/v2/4.png",
    "https://cdn.example.com/v2/5.png"
  ],
  "scheduleDate": "2026-09-01",
  "scheduleTime": "10:00",
  "timezone": "Asia/Kolkata"
}
  • Only Instagram and Threads mix video into a carousel; everywhere else a set of several must be images only, and a video goes out on its own.

  • create_post refuses a set a target will not take before any credits are spent, naming the profile and the rule. preflight_post with the same mediaUrls reports the same thing plus a mediaSetLimits map, so check first when one carousel goes to several networks.

  • A profile can carry its own mediaUrls on its targetAccounts entry (or in variants as { "twitter": { "mediaUrls": [...] } }), replacing the shared set - the way to give X and Bluesky a four-slide cut of a longer carousel.

  • Every slide is copied into PostMCP's own storage at write time, like a single attachment, so a host that expires the links later does not break the scheduled post. One slide failing at publish time fails that profile's post rather than publishing a shorter carousel; publish_post_now retries it.

  • update_post with mediaUrls replaces the whole set (add, remove or reorder slides); an empty array removes all media. Every post returned by list_posts / get_post carries mediaUrls alongside mediaUrl.

Notes for clients

  • Target profiles, not platforms. targetAccounts sends only to the profiles named; platforms fans out to every connected profile on each platform.

  • One post per profile. create_post stores a separate post per targeted profile, so each can be edited, retried or cancelled on its own. Give per-profile copy through targetAccounts[].content or the variants map.

  • Always pass timezone when a wall-clock time matters. The backend defaults to UTC, so a 9:00 IST post scheduled without a zone goes out at 14:30 IST.

  • Credits are charged per profile delivered to (X/Twitter costs 5, others 1), plus a one-off 50-credit surcharge when the copy contains a link. preflight_post reports this before you commit.

  • Analytics are read on request, never in the background. list_posts and get_connected_accounts carry what the last reading stored, free. get_post_analytics (one post, every network it went to) and get_profile_analytics (one connected profile: followers, posts, views) with refresh: true read the network now for 1 credit each; without it, the stored reading is free. engagements is likes + comments + shares on every network, so it compares across platforms. A null means the network does not report that metric (Bluesky has no views), an error naming reconnect means the account predates the insights permission and its owner must reconnect it, and unavailable: true means the network never answers for that kind of post (LinkedIn personal profiles).


šŸ’» Client Integration Guides

1. Claude Desktop App (Stdio Mode)

Add the configuration below to your Claude Desktop config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "postmcpai": {
      "command": "npx",
      "args": ["-y", "@postmcpai/server"],
      "env": {
        "POSTMCPAI_API_KEY": "pmcp_sec_your_secret_api_key_here"
      }
    }
  }
}

2. Cursor IDE

  1. Open Cursor Settings -> Features -> MCP.

  2. Click + Add New MCP Server.

  3. Fill in the details:

    • Name: postmcpai

    • Type: command

    • Command: npx -y @postmcpai/server

  4. Under Environment Variables, add:

    • POSTMCPAI_API_KEY = pmcp_sec_your_secret_api_key_here

  5. Click Save.


3. Claude.ai & Remote Web Connectors (Streamable HTTP / SSE Mode)

Host this server on any cloud service (Render, Railway, Fly.io, Vercel) or tunnel your local machine using ngrok.

Launching in HTTP Mode:

export PORT=3000
# Each remote caller supplies its own API key or OAuth token.

npm run start:sse

Connecting to Claude.ai:

  1. Provide your public MCP URL with your API key attached: https://your-hosted-domain.com/mcp?apikey=pmcp_sec_your_secret_api_key_here

  2. Claude.ai will discover tool capabilities via /mcp and authenticate seamlessly.

  3. That URL is all you need: the key is bound to the workspace it was issued from, so tools act on that workspace without being told. To point the same key at a different workspace, append &projectId=YOUR_WORKSPACE_ID (or send an x-project-id header); individual tool calls can still override either with workspaceId.


4. ChatGPT Custom GPTs (REST Actions)

  1. When configuring a Custom GPT Action, specify your server URL (e.g. https://your-hosted-domain.com).

  2. Import the OpenAPI schema directly from: https://your-hosted-domain.com/openapi.json

  3. Set Authentication to API Key (Bearer Authorization or custom x-api-key). This is a GPT Actions integration, not a per-customer OAuth plugin. For the plugin, use OAUTH.md.


5. Programmatic Node.js Library Usage

You can also use @postmcpai/server as a library in your own Node.js backends:

import { createServer, createExpressApp, makeBackendRequest } from "@postmcpai/server";

// Create a standalone MCP Server instance
const mcpServer = createServer(() => process.env.POSTMCPAI_API_KEY);

// Or create an Express app with all remote routes attached
const app = createExpressApp();
app.listen(3000);

🧪 Local Testing & Development

# Clone the repository
git clone https://github.com/postmcp/postmcp-mcp-server.git
cd postmcp-mcp-server

# Install dependencies
npm install

# Start in Stdio Mode
npm start

# Start in HTTP Mode with hot reload
npm run dev

šŸ“„ License

Distributed under the MIT License. Copyright Ā© 2026 PostMCP AI.

Available Tools

7 tools
create_postC

Schedule or publish immediately a post to one or more social media platforms or specific accounts.

Inputs: content (required), mediaUrl, platforms, scheduleDate, +3 more.

delete_postA

Cancel and delete a scheduled or failed post from the database.

Inputs: id (required).

get_connected_accountsA

List all active, connected social media channels and their associated profile usernames.

Inputs: no named parameters.

get_user_infoA

Retrieve details of the logged-in user including subscription plan, credit balance, and AI token count.

Inputs: no named parameters.

list_postsA

Retrieve a list of scheduled, published, and failed social media posts.

Inputs: no named parameters.

publish_post_nowA

Broadcast an existing scheduled post immediately to its platforms.

Inputs: id (required).

update_postB

Update the fields (content, platforms, schedule date/time) of an existing post.

Inputs: id (required), status, content, platforms, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: user info, connected accounts, and post management (list, create, publish, update, delete). The actions are clearly separated, and even create_post vs publish_post_now are distinguished by whether the post is new or existing.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (get_user_info, list_posts, create_post, publish_post_now, delete_post, update_post). The naming is uniform and predictable.

    Tool Count5/5

    Seven tools is well-scoped for a social media post management server. Each tool covers a necessary operation without redundancy or bloat, making the set easy to navigate.

    Completeness5/5

    The tool set provides full CRUD for posts (create, list, update, delete), plus a specialized publish action, and includes user/account context. This covers the core workflow of managing social media posts from scheduling to publication.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Official MCP server for PostEverywhere (posteverywhere.ai/social-media-scheduler). Let Claude, ChatGPT, Cursor or any MCP client schedule and publish posts to 13 platforms: Instagram, TikTok, YouTube, LinkedIn, Facebook, X, Threads, Pinterest, Bluesky, Telegram, Discord, WordPress and Google Business Profile. 40 tools: best-time scheduling, threads, cross-posting, campaigns, analytics.
      33
      289 npm
      7
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage social media accounts and CRM operations, including posting, analytics, inbox management, and customer management.
      22
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants and autonomous agents to connect to social media accounts and manage, generate, schedule, upload media for, and publish content across Facebook Pages, YouTube, TikTok, Instagram, and X, plus maintain a content pipeline.
      14
      MIT