PostPulse MCP Server

An MCP (Model Context Protocol) server that connects AI assistants to PostPulse — a social media management platform. Schedule posts, upload media, and manage accounts across Instagram, Facebook, YouTube, TikTok, Threads, LinkedIn, X (Twitter), Bluesky, and Telegram — all through natural language.

Features

• Multi-platform posting — Schedule posts to 9 social media platforms from a single interface
• Media management — Upload images and videos via URL or binary data for use in posts
• Account management — List and manage all connected social media accounts
• OAuth 2.0 authentication — Secure access via Auth0-based token verification
• Streamable HTTP transport — Modern MCP transport protocol for reliable communication

Supported Platforms

Platform	Placements	Content Types	Requirements
Instagram	Feed, Reels, Stories	Image, Video	Business Account
Facebook	Feed, Reels, Stories	Image, Video	Page
YouTube	Video, Shorts	Video	Channel
TikTok	Video, Carousel	Image, Video	Account
Threads	Post	Image, Video	Account
LinkedIn	Post	Image, Video	Personal Account
X (Twitter)	Post	Image, Video	Account
Bluesky	Post	Image	Account
Telegram	Message	Text, Image, Video	Channel/Chat

Quick Start

Hosted Server (Recommended)

PostPulse runs a hosted MCP server at https://mcp.post-pulse.com — no setup required. Point your MCP client to this URL and authenticate via OAuth.

Example MCP client configuration:

{
  "mcpServers": {
    "postpulse": {
      "url": "https://mcp.post-pulse.com"
    }
  }
}

Install via Smithery

You can also install through Smithery:

npx -y @smithery/cli install post-pulse/mcp-server --client claude

Self-Hosted

If you prefer to run the server yourself:

1. Clone the repository:

git clone https://github.com/PostPulse/mcp-server-postpulse.git
cd mcp-server-postpulse

2. Install dependencies and build:

npm install
npm run build

3. Start the server:

npm start

Or with Docker:

docker build -t mcp-server-postpulse .
docker run -p 3000:3000 mcp-server-postpulse

Environment Variables

Variable	Default	Description
HOST	0.0.0.0	Server bind address
PORT	3000	Server port
PUBLIC_URL	—	Public-facing URL (for OAuth metadata discovery)
POSTPULSE_AUTH_ISSUER	https://auth.post-pulse.com/	Auth0 issuer URL
POSTPULSE_AUTH_JWKS_URI	https://auth.post-pulse.com/.well-known/jwks.json	JWKS endpoint
POSTPULSE_AUDIENCE	https://api.post-pulse.com	API audience
POSTPULSE_API_URL	https://api.post-pulse.com	PostPulse API base URL
REDIS_URL	—	Redis connection URL for session/event persistence (required)

Tools

list_accounts

List all connected social media accounts with their IDs, platforms, usernames, and display names. Use this as the first step to discover available accounts before scheduling posts or accessing chats.

Parameters: None

Returns: JSON array of account objects (id, platform, username, name).

list_chats

List publishing destinations for accounts that have sub-destinations. Facebook accounts publish to Pages, and Telegram accounts publish to channels or chats. Call this before scheduling posts to either platform — use the returned id as the facebookPageId or telegramChannelId in schedule_post.

Only supports FACEBOOK and TELEGRAM. Other platforms do not have sub-destinations and should be posted to directly.

Parameters: | Name | Type | Required | Description | |--

... View full README on GitHub