PostEveryPlatform

com.posteveryplatformPublished by posteveryplatform.comOfficial publisherv1.0.0Updated Nov 1, 2026

Draft and schedule social posts to 12 platforms, with owner approval on by default.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server that lets an assistant draft and schedule social media posts across 12 platforms, with owner approval on by default.

What you can do
  • Draft social media posts for 12 connected platforms.
  • Schedule posts for later publishing.
  • Route drafts through owner approval, which is enabled by default.
  • Connect over a hosted remote endpoint with OAuth sign-in.
When to use it
Useful when you want an assistant to prepare and queue social media content across several platforms without switching between each network's own composer, and when you want a human approval step before anything is published.
Requirements
A remote MCP client that supports streamable HTTP, network access to the provider's hosted endpoint, and an OAuth sign-in to a PostEveryPlatform account. No environment variables or headers are declared.
Before you install
The server can publish or schedule content on connected social accounts, which is outward-facing and hard to undo once posted. Approval is on by default, so keep it enabled unless you intend unattended publishing. Sign-in is via OAuth, granting the server access to your account.

Installation

In SourceWeft

  1. Open PostEveryPlatform 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/com.posteveryplatform%2Fposteveryplatform/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": {
    "posteveryplatform": {
      "type": "http",
      "url": "https://posteveryplatform.com/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.0LatestNov 1, 2026

Score

83% 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
  • 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.