Postbase MCP server

@postbasehq/mcp

The Model Context Protocol server for Postbase, the open-source social media scheduler. Add it to Claude, Cursor or any MCP client and let your AI agent draft and schedule posts and threads to X, LinkedIn, Bluesky and Mastodon. (TikTok and YouTube need a video, so schedule those in the app.)

Post everywhere. Even from your AI.

Hosted server (no API key)

Postbase also runs this server for you at https://mcp.postbase.so/mcp, with OAuth sign-in instead of an API key. Add that URL as a custom connector in Claude or ChatGPT, or as a remote MCP server in Cursor, VS Code, Windsurf, Claude Code or Gemini CLI. The MCP config generator prints the exact setup for each one.

Use this npm package when you want an API key instead, or a self-hosted Postbase.

Quick start

1. Create an API key in your Postbase dashboard under Developers.
2. Add the server to your MCP client config (see examples below).
3. Ask your agent: "Schedule this thread for 9am to X and Bluesky."

Example configs

Any MCP client — the minimal config:

{
  "mcpServers": {
    "postbase": {
      "command": "npx",
      "args": ["@postbasehq/mcp"],
      "env": { "POSTBASE_API_KEY": "pb_live_your_key_here" }
    }
  }
}

Claude Desktop — add the same block to your config file:

• macOS: ~/Library/Application Support/Claude/claudedesktopconfig.json
• Windows: %APPDATA%\Claude\claudedesktopconfig.json

Then restart Claude Desktop.

Cursor — add it to ~/.cursor/mcp.json (or Settings → MCP):

{
  "mcpServers": {
    "postbase": {
      "command": "npx",
      "args": ["@postbasehq/mcp"],
      "env": { "POSTBASE_API_KEY": "pb_live_your_key_here" }
    }
  }
}

Local development — point at a Postbase instance running on your machine:

{
  "mcpServers": {
    "postbase": {
      "command": "npx",
      "args": ["@postbasehq/mcp"],
      "env": {
        "POSTBASE_API_KEY": "pb_live_your_key_here",
        "POSTBASE_API_URL": "http://localhost:3000/api/v1"
      }
    }
  }
}

Tools

Shortened. The full README is on GitHub.