PostFlow

app.postflowPublished by postflow.appOfficial publisherv1.0.0Updated Oct 25, 2026

Schedule, publish and manage social media posts across platforms.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

PostFlow is a remote MCP server that lets an assistant schedule, publish and manage social media posts across platforms.

What you can do
Schedule social media posts for future publishing across connected platforms. Publish posts and manage existing posts through the assistant. The manifest lists no individual tools, so the exact set of actions is not documented here.
When to use it
Useful when you want an assistant to help plan, schedule or manage social media content across several platforms without switching between each platform's own tools.
Requirements
A remote endpoint at api.postflow.app reached over streamable HTTP, with OAuth sign-in required. A PostFlow account and connected social media platforms are implied but not documented.
Before you install
OAuth grants the server access to your PostFlow account, and actions may publish or change public social media content. Review what the assistant is about to post before confirming, since publishing is visible to third parties.

Installation

In SourceWeft

  1. Open PostFlow in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.postflow%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "postflow": {
      "type": "http",
      "url": "https://api.postflow.app/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 25, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.