PostPulse MCP Server

![smithery badge](https://smithery.ai/servers/post-pulse/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

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:

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).

`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 | |---|---|---|---| | accountId | number | Yes | Account ID obtained from list_accounts | | platform | string | Yes | FACEBOOK or TELEGRAM |

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.

Parameters: | Name | Type | Required | Description | |---|---|---|---| | accountId | number | Yes | Account ID from list_accounts | | platform | string | Yes | Target platform: INSTAGRAM, FACEBOOK, TELEGRAM, YOUTUBE, TIKTOK, THREADS, LINKEDIN, X_TWITTER, BLUE_SKY | | content | string | No | Post text/caption | | mediaPaths | string[] | No | Media keys returned by upload_media | | scheduledTime | string | Yes | ISO-8601 timestamp (e.g., 2025-01-15T10:00:00Z) | | facebookPageId | string | Yes (Facebook) | 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 | | publicationType | string | No | FEED, REEL, or STORY (Instagram/Facebook, defaults to FEED) | | title | string | No | Video title (YouTube, TikTok) | | topicTag | string | No | Topic tag (Threads) |

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.

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.

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.

Example Workflow

A typical interaction with the PostPulse MCP server:

List accounts to find connected social media profiles
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!'"

PostPulse