MCP Server

FoPost runs a hosted MCP server at https://api.fopost.com/mcp. Point any MCP client that supports remote servers at that URL, sign in to FoPost in the browser, and the tools appear. There is nothing to install and no key to copy.

If your client only runs local servers, use the stdio package instead.

Hosted server

Claude Code

claude mcp add --transport http fopost https://api.fopost.com/mcp

Claude Code opens your browser to sign in the first time you use the server.

Or install the plugin, which adds the same server plus skills for scheduling a week, triaging the inbox, and writing the weekly report:

claude plugin marketplace add fopost/fopost-mcp
claude plugin install fopost@fopost

Claude, ChatGPT, Cursor, and others

Add a custom connector (or remote MCP server) and paste the URL:

https://api.fopost.com/mcp

Clients configured through a JSON file take the URL on its own:

{
  "mcpServers": {
    "fopost": {
      "url": "https://api.fopost.com/mcp"
    }
  }
}

Signing in

The client sends you to a FoPost consent screen. Pick the workspace the assistant works in and approve the permissions it asks for. The connection stays locked to that workspace, and you can cut it off at any time from Settings → Connected Apps.

A client that can send custom headers may skip the sign-in and pass an API key as X-API-Key instead. A key bound to one workspace works in that workspace. A key that is not bound works in your only workspace, or in the one you name with an X-Workspace-Id header.

What the hosted server can do

It serves the same tools as the FoPost Agent: drafting and editing posts, reading the calendar, the inbox, analytics, Radar, and more. Each tool needs the permission that covers it, so a connection without ai cannot spend credits, and one without publish cannot touch the schedule.

Anything that publishes, schedules, or sends waits for your approval. The assistant can propose it; nothing reaches a network until you approve.

Local server (stdio)

@fopost/mcp runs on your machine over stdio and talks to the same REST API the dashboard uses. It 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.

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

Forty-one tools across posts, accounts, AI, the inbox, and ads: listing, scheduling, publishing, delivery status, account health, captions, the credit balance, comments and DMs, reply approvals, boosts, ads, audiences, and leads. Each one is a thin wrapper over the REST API.

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