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, Pinterest, X (Twitter), Bluesky, and Telegram — all through natural language.
Social media scheduler for Instagram, Facebook, YouTube, TikTok, LinkedIn, X, Bluesky, and Telegram.
2026-11-08
ดาว
—
เครื่องมือ
—
อัปไทม์
—
Features
Multi-platform posting — Schedule posts to 10 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
Connect social accounts from the chat — Get a secure link to connect or reconnect an account without opening the PostPulse app
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
Pinterest
Pin
Image, Video, Carousel (2–5 images)
Board
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.
npx -y @smithery/cli install post-pulse/mcp-server --client claude
Self-Hosted
If you prefer to run the server yourself:
Clone the repository:
git clone https://github.com/PostPulse/mcp-server-postpulse.git
cd mcp-server-postpulse
Install dependencies and build:
npm install
npm run build
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, needsReauthorization). A new user has no accounts yet: the result is [] plus a hint to use connect_account. Accounts with needsReauthorization: true must be reconnected with connect_account before posting; the result names them in a second text block.
connect_account
Get a secure PostPulse link that connects (or reconnects) a social media account to PostPulse directly from the chat. The user opens the link in any browser and lands on a PostPulse page that shows which PostPulse account (masked email) the social account will be attached to. After Continue and approving access on the platform, the page says "Account connected — return to your chat". The tool does not wait for completion: once the user says they are done, call list_accounts to confirm the account.
Reconnect an existing account (from list_accounts, usually one with needsReauthorization: true). The platform is taken from the account
Behaviour:
For a new connection the tool first checks that the user may add an account (plan or credits). If not, it returns the reason and a link to billing.
The link is single-use, tied to the user's PostPulse account and valid for 24 hours; the platform consent starts only when the user clicks Continue on the page. It must not be shared: whoever completes it attaches their social account to this PostPulse account.
If too many links are requested in a short time, the tool asks to wait a few minutes and try again.
A new Facebook connection creates one FACEBOOK_PAGE account per picked Page: post to it directly, without list_chats. For TELEGRAM and for a reconnected FACEBOOK account, call list_chats afterwards to pick the channel or Page.
Clients that support URL-mode elicitation additionally get a native "open this link" dialog; the link is always in the text result as well.
Errors that happen in the browser (account limit, account already used by another PostPulse user, expired link) are shown on the page, not returned by the tool.
list_chats
List publishing destinations for accounts that have sub-destinations. Facebook accounts publish to Pages, Telegram accounts publish to channels or chats, and Pinterest accounts publish to boards. Call this before scheduling posts to these platforms — use the returned id as the facebookPageId, telegramChannelId or pinterestBoardId in schedule_post.
Only supports accounts whose platform is FACEBOOK, TELEGRAM or PINTEREST. Other platforms, including FACEBOOK_PAGE (an account that is one Page), do not have sub-destinations and should be posted to directly.
Parameters:
Name
Type
Required
Description
accountId
number
Yes
Account ID obtained from list_accounts
Returns: JSON array of destination objects (id, title, type, platform).
upload_media
Upload media files (images, videos) for use in scheduled posts. Supports two modes: importing from a public URL (with automatic processing) or uploading binary data directly as base64. Returns a media key to reference in schedule_post.
Parameters:
Name
Type
Required
Description
mediaUrl
string
No
Public URL of the media file to import
mediaData
string
No
Base64-encoded media file content
mediaType
string
No
MIME type (e.g., image/jpeg, video/mp4). Required when using mediaData
mediaName
string
No
Filename for the uploaded media
Either mediaUrl or both mediaData and mediaType must be provided.
schedule_post
Schedule a social media post to one or more connected accounts. Supports platform-specific options like publication type (feed, reel, story), video titles, and topic tags. Posts are scheduled for a future time using ISO-8601 timestamps.
Facebook Page ID from list_chats. Required when platform is FACEBOOK
telegramChannelId
string
Yes (Telegram)
Telegram Channel/Chat ID from list_chats. Required when platform is TELEGRAM
pinterestBoardId
string
Yes (Pinterest)
Pinterest Board ID from list_chats. Required when platform is PINTEREST
publicationType
string
No
FEED, REELS, or STORY (Instagram/Facebook, defaults to FEED)
title
string
No
Video title (YouTube, TikTok) or Pin title (Pinterest, up to 100 characters)
topicTag
string
No
Topic tag (Threads)
link
string
No
Destination URL opened when the Pin is clicked (Pinterest)
altText
string
No
Alt text for the Pin image (Pinterest)
boardSectionId
string
No
Section within the board (Pinterest)
Resources
postpulse://accounts
An MCP resource providing the list of all connected social media accounts. Returns the same data as the list_accounts tool in JSON format, including needsReauthorization.
Authentication
This server uses OAuth 2.0 with Auth0. OAuth metadata is discoverable at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server.
No existing PostPulse account is needed: signing in through the MCP client (with Google or a passwordless email code) creates the PostPulse account on first use. The user then connects social accounts with connect_account.
Dynamic Client Registration (DCR)
MCP clients that support OAuth can register automatically via Dynamic Client Registration (RFC 7591). The server advertises a registration_endpoint in its OAuth metadata, so compliant clients (such as Claude Desktop, Cursor, etc.) will handle the entire OAuth flow — registration, authorization, and token exchange — without any manual setup from the user.
Pre-Registered Client Credentials
If you already have client credentials created through the PostPulse Developer Portal, you can configure your MCP client to use them directly instead of DCR. Pass your client_id and client_secret in the OAuth authorization code flow against the PostPulse authorization server.
HTTP Endpoints
Path
Purpose
POST /, POST /sse
MCP Streamable HTTP transport (initialize + messages), Bearer token required
GET /, GET /sse with Mcp-Session-Id
SSE stream for an existing session
GET /, GET /sse with Accept: text/html
Minimal landing page for browsers and crawlers (links to the setup guide and API docs). Any other Accept without a session still gets 400
GET /health
Health check (ok)
GET /robots.txt
User-agent: * / Disallow: / — the host is not a website
GET /.well-known/*
OAuth metadata and the Smithery server card
anything else
404 ({"error":"Not found"} or plain text for HTML clients)
Every response carries X-Robots-Tag: noindex, nofollow so search engines never index this host.
Example Workflow
A typical interaction with the PostPulse MCP server:
List accounts to find connected social media profiles
Connect an account (if the platform is missing) with connect_account
Upload media (optional) to prepare images or videos
Schedule a post with content, media, and a future publish time
User: "Schedule an Instagram reel for tomorrow at 9am with the video at https://example.com/video.mp4 and caption 'Check this out!'"
First run (new user)
User: "Post 'Hello LinkedIn!' to my LinkedIn tomorrow at 10:00 UTC"
Assistant: list_accounts → [] ("No social accounts are connected yet")
connect_account(platform: LINKEDIN) → link
"Open this link, check the PostPulse account on the page, approve access on LinkedIn, then tell me when you are done."
User: "Done"
Assistant: list_accounts → [{ id: 123, platform: LINKEDIN, ... }]
schedule_post(accountId: 123, platform: LINKEDIN, content: "Hello LinkedIn!", scheduledTime: ...)