PostPulse

PostPulse is a unified API and integration suite that handles the complexity of social media publishing.

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • List Accounts: List all connected social media accounts (Instagram, Facebook, YouTube, TikTok, Threads, LinkedIn, X/Twitter, Telegram) with their IDs, platforms, usernames, and display names. Call thi
  • List Chats: List publishing destinations (Telegram channels/chats or Facebook Pages) available for a specific account. Required before scheduling posts to Telegram or Facebook — use the returned id as
  • Upload Media: Upload media files (images, videos) for use in scheduled posts. Supports two modes: (1) provide a public mediaUrl to import from the web (the server handles download and processing autom

What data it sees

Do you need an account

No: the server works without sign-in

PostPulse is a unified API and integration suite that handles the complexity of social media publishing. Instead of managing individual platform audits and breaking tokens, developers use PostPulse as their outsourced social-connectivity team.

Integration Paths

1. White-Label (For App Developers)

  • Best for: SaaS founders and mobile app developers who want a "Native" experience.
  • Experience: Your users never leave your UI and require zero PostPulse registration.
  • Branding: 100% your brand. Includes a native OAuth bridge for account connections.

2. Private-Label (For Individual Developers & Automation)

  • Best for: Engineers building custom internal tools or automating personal workflows.
  • Experience: Users connect their own social accounts via the PostPulse interface.
  • Tools Included:
    • Official n8n Node: Drag-and-drop posting workflows.
    • Official Make.com App: Seamless automation with 1000+ other apps.
    • MCP Server (Model Context Protocol): Allow LLMs and AI Agents to post to social media directly from their context.
    • REST API: Standardized endpoints for all 9+ supported platforms.

The Cost of "Manual Integration" (The Alternative)

Building social integrations manually is a major resource drain:

  • Complexity: Reading 9+ sets of disparate, often conflicting API documentation.
  • Audit Hurdles: Passing "Developer App" reviews for Meta, TikTok, and Google (can take months).
  • Maintenance: Managing token refreshes, rate limits, and constant API version changes.
  • PostPulse Solution: We handle all of the above. You integrate once; we maintain it forever.

How to connect

How to connect PostPulse to Claude

The server address to paste into Claude settings:

https://post-pulse-mcp.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect PostPulse to ChatGPT

The server address to paste into ChatGPT settings:

https://post-pulse-mcp.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect PostPulse to Cursor

The server address to paste into Cursor settings:

https://post-pulse-mcp.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (4)

Raw names from tools/list. Only developers need these.

list_accountsList all connected social media accounts (Instagram, Facebook, YouTube, TikTok, Threads, LinkedIn, X/Twitter, Telegram) with their IDs, platforms, usernames, and display names. Call this first to discover available accounts before using schedule_post or list_chats.
list_chatsList publishing destinations (Telegram channels/chats or Facebook Pages) available for a specific account. Required before scheduling posts to Telegram or Facebook — use the returned id as the chatId parameter in schedule_post. Only supports TELEGRAM and FACEBOOK platforms; other platforms do not have sub-destinations and should be posted to directly via schedule_post.
upload_mediaUpload media files (images, videos) for use in scheduled posts. Supports two modes: (1) provide a public mediaUrl to import from the web (the server handles download and processing automatically), or (2) provide base64-encoded mediaData with a mediaType MIME type for direct binary upload. Returns a media key string that you pass to the mediaPaths parameter of schedule_post.
schedule_postSchedule a social media post to a connected account. Supports Instagram (feed, reel, story), Facebook (feed, reel, story), YouTube, TikTok, Threads, LinkedIn, X/Twitter, Bluesky, and Telegram. Requires an accountId from list_accounts, a platform identifier, and a scheduledTime in ISO-8601 format. For Facebook and Telegram, you MUST first call list_chats to get the publishing destination (Page ID or Channel ID) and pass it as facebookPageId or telegramChannelId respectively. Optionally attach media from upload_media via mediaPaths, set publication type, video title, or topic tag depending on the platform.