PostPulse

Name: PostPulse
Author: PostPulse

@PostPulse

About PostPulse

Schedule social media posts, upload media, and manage accounts across Instagram, Facebook, YouTube, TikTok, Threads, LinkedIn, X (Twitter), Bluesky, and Telegram.

#social-media #marketing #content-management #scheduling #automation

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

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

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is PostPulse?

PostPulse is a Model Context Protocol (MCP) server that connects AI assistants to the PostPulse social media management platform. It enables scheduling posts, uploading media, and managing accounts across Instagram, Facebook, YouTube, TikTok, Threads, LinkedIn, X (Twitter), Bluesky, and Telegram through natural language.

How to use PostPulse?

Point your MCP client to the hosted server at https://mcp.post-pulse.com with no additional setup, or self-host by cloning the repository, installing dependencies, and running the server. Authenticate via OAuth 2.0; clients supporting Dynamic Client Registration handle the flow automatically.

Key features of PostPulse

Multi-platform posting to 9 social media platforms
Media management via URL or binary upload
Account listing and management tools
OAuth 2.0 authentication with Auth0
Streamable HTTP transport for reliable communication

Use cases of PostPulse

Schedule social media posts in advance across multiple platforms
Upload and manage media for use in scheduled posts
Discover connected accounts and their publishing destinations
Automate content publishing through AI assistant conversations

FAQ from PostPulse

What platforms does PostPulse support?

Instagram, Facebook, YouTube, TikTok, Threads, LinkedIn, X (Twitter), Bluesky, and Telegram — each with platform-specific placement and content type requirements.

Can I self-host the PostPulse MCP server?

Yes. Clone the repository, run npm install && npm run build && npm start, or use the provided Dockerfile. Environment variables allow configuration of host, port, OAuth issuer, API URL, and Redis connection.

How does authentication work?

PostPulse uses OAuth 2.0 with Auth0. MCP clients can register automatically via Dynamic Client Registration (RFC 7591), or you can use pre-registered client credentials from the PostPulse Developer Portal.

What is the typical workflow?

List accounts with list_accounts, optionally upload media with upload_media, then schedule a post with schedule_post using an ISO-8601 timestamp for future publishing.