PostPulse

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.

该来源不提供完整文件导出（国内平台多为平台内托管），仅存元数据与原链

接入信息

传输形态: http
鉴权方式: 鉴权未知
端点: https://post-pulse-mcp.run.tools

鉴权方式未标注，请核对官方文档后再接入——不要直接使用以下片段

{
  "mcpServers": {
    "PostPulse": {
      "url": "https://post-pulse-mcp.run.tools"
    }
  }
}

能力清单

工具	说明
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 this first to discover available accounts before using schedule_post or list_chats.
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 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_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 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_post	Schedule 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.

纠错与举报（发现条目失效、署名有误或涉及侵权？）

提交举报 / 纠错

侵权举报经核验成立后，我们会即时下线该条目并删除已存的内容副本。