Postfast MCP Server

PostFast MCP Server

MCP server for the PostFast API — schedule and manage social media posts via AI tools like Claude, Cursor, VS Code, and more.

Hosted connector (no install)

Prefer not to run anything locally? Connect to the hosted endpoint and authenticate with OAuth — no npx, no API key to manage:

https://mcp.postfa.st/mcp

Add it as a remote/streamable-HTTP MCP server in any client that supports OAuth (e.g. ChatGPT, Claude). You'll be prompted to sign in to PostFast and authorize access on first use.

Want to run the server yourself instead? Use the npx + API-key setup in Quick Start below.

Quick Start

1. Get your API key

Log in to PostFast, go to API in the sidebar, and generate a key.

2. Install

Choose your preferred method:

Claude Desktop (recommended)

Download the extension from the Claude Desktop extension directory or install manually:

1. Add to claude_desktop_config.json:

{
  "mcpServers": {
    "postfast": {
      "command": "npx",
      "args": ["-y", "postfast-mcp"],
      "env": {
        "POSTFAST_API_KEY": "your-api-key-here"
      }
    }
  }
}

1. Restart Claude Desktop.

Claude Code

Via plugin (pending marketplace approval):

/plugin install postfast@claude-plugins-official

After installing, set your API key — pick one of these:

# Option A: Add to your shell profile (~/.zshrc or ~/.bashrc)
export POSTFAST_API_KEY="your-api-key-here"

# Option B: Add to ~/.claude/settings.local.json
# { "env": { "POSTFAST_API_KEY": "your-api-key-here" } }

Then restart Claude Code.

Via manual config:

Add to your project's .mcp.json or ~/.claude/.mcp.json (global):

{
  "mcpServers": {
    "postfast": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "postfast-mcp"],
      "env": {
        "POSTFAST_API_KEY": "your-api-key-here"
      }
    }
  }
}

Cursor / VS Code / Windsurf / Other MCP clients

Add to your MCP config (.mcp.json, mcp.json, or the tool's settings UI):

{
  "mcpServers": {
    "postfast": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "postfast-mcp"],
      "env": {
        "POSTFAST_API_KEY": "your-api-key-here"
      }
    }
  }
}

3. Use it

Ask your AI assistant things like:

• "List my connected social accounts"
• "Schedule a post to Instagram for tomorrow at 9am"
• "Show me all scheduled posts for this week"
• "Upload this image and create a LinkedIn post with it"
• "Create a Facebook reel with this video"
• "Show me analytics for my Instagram posts this month"

Available Tools

Social Inbox (comments)

Comments on your posts — TikTok, Instagram, Facebook Pages, and Threads — in one inbox (an account's inboxCapable flag says what is live today). Comments only (no direct messages), from connect onward (no history backfill). Reply capability is always server-computed per conversation (canReply, maxReplyLength, windowState, disabledReason) — render from those fields, never platform assumptions.

Supported Platforms

Facebook, Instagram, X (Twitter), TikTok, LinkedIn, YouTube, BlueSky, Threads, Pinterest, Telegram, Google Business Profile

Platform-Specific Controls

When creating posts, you can pass platform-specific settings via the controls parameter:

Media Upload

The upload_media tool handles the full flow in a single call:

1. Detects content type from file extension
2. Gets a signed upload URL from PostFast
3. Uploads the file
4. Returns a key and type ready to use in create_posts

Supported formats: JPEG, PNG, GIF, WebP, MP4, WebM, MOV

You can also use get_upload_urls directly if you need more control over the upload process.

Environment Variables

Testing

Verify everything works with the MCP Inspector:

POSTFAST_API_KEY=your-key npx @modelcontextprotocol/inspector npx postfast-mcp

API Docs

Full REST API documentation: postfa.st/docs

Development

npm install
npm run build
node dist/stdio/index.js

Tools are authored once in src/core (the catalog — schemas, descriptions, annotations, per-binding availability) and exposed to consumers as postfast-mcp/core; src/stdio binds the catalog to the public REST API. Releases: PRs add a .changeset/*.md; npm run version folds them into the bump + changelog, and pushing the vX.Y.Z tag publishes npm + MCP Registry + the MCPB release from CI (OIDC — no tokens anywhere).

Badges

License

MIT