Postify

com.usepostifyPublished by usepostify.comOfficial publisherv1.0.1Updated Oct 30, 2026

Schedule, publish, and analyze social posts across 11 platforms from any MCP client.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationData & Analytics

Overview

AI-generated overview

Postify is a remote MCP server that lets an assistant schedule, publish and analyze social media posts across 11 platforms.

What you can do
  • Schedule social posts for future publishing across 11 platforms
  • Publish posts to connected social accounts
  • Analyze post performance across platforms
  • Manage social publishing from any MCP client
When to use it
Useful when you want an assistant to draft, queue and publish social media content and review how it performed, instead of switching between platform dashboards.
Requirements
Remote endpoint at app.usepostify.com over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared. Social accounts must be connected to a Postify account.
Before you install
The server can publish content publicly to connected social accounts, so review drafts before letting an assistant post. Access is granted through OAuth to your Postify account; check which accounts and permissions you authorize.

Installation

In SourceWeft

  1. Open Postify 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.usepostify%2Fpostify/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": {
    "postify": {
      "type": "http",
      "url": "https://app.usepostify.com/api/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

2
  1. v1.0.1LatestOct 30, 2026
  2. v1.0.0Sep 16, 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.