MCP.so
ログイン

PostPulse MCP Server

@PostPulse

基本情報

PostPulse MCP Server について

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

PostPulse MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

PostPulse MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンでサーバーのエンドポイントに接続し、ツール一覧を取得できます。

概要

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

よくある質問

1

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.

2

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.

3

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.

4

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.

5

Are there any runtime requirements for self-hosting?

You need Node.js, npm, and a Redis URL for session/event persistence. The Docker alternative bundles the server into a container.

コメント

「メディアとデザイン」の他のコンテンツ