MCP Server

@fopost/mcp exposes FoPost as a set of tools any MCP-aware assistant can call: Claude Desktop, Claude Code, Cursor, Continue, and anything else that speaks the Model Context Protocol. It runs over stdio and needs no install step: npx -y @fopost/mcp is the whole invocation. Needs Node 18 or newer.

Source and issues: github.com/fopost/fopost-mcp. MIT licensed.

Set it up

First, create an API key at Settings → API Keys in the dashboard with the scopes you need. posts, accounts, and workspaces cover most of it; add ai only if you want the assistant to spend credits.

The server reads two environment variables, once at startup:

Claude Desktop

Edit claude_desktop_config.json, at ~/Library/Application Support/Claude/ on macOS or %APPDATA%\Claude\ on Windows:

{
  "mcpServers": {
    "fopost": {
      "command": "npx",
      "args": ["-y", "@fopost/mcp"],
      "env": {
        "FOPOST_API_KEY": "your-api-key"
      }
    }
  }
}

Restart the app and the tools appear.

Claude Code

claude mcp add fopost --env FOPOST_API_KEY=your-api-key -- npx -y @fopost/mcp

Cursor, Continue, and others

Same command, npx -y @fopost/mcp, with FOPOST_API_KEY in the environment.

The tools

Fourteen tools across posts, accounts, and AI: listing, scheduling, publishing, delivery status, account health, captions, and the credit balance. Each one is a thin wrapper over the same REST API the dashboard uses.

What it can and cannot do

The server is your API key wearing a different interface. It inherits the key's scopes and its workspace binding exactly, so an assistant cannot reach a workspace you did not grant, and a tool whose scope the key lacks answers 403.

Give the key the narrowest scopes that do the job (a key without ai cannot spend a single credit), and remember that every call is one attempt: the server adds no retries, so a rate-limited request surfaces to the assistant as an error it has to handle.

Next