MCP ServerAgents

The FoPost MCP Server

One npm package turns your FoPost workspace into a set of MCP tools. Any client that supports local MCP servers can schedule posts, check deliveries, and repurpose content with your approval at every step.

Get your API key All agents

mcpServers

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

Standard MCP

Stdio transport, no custom protocol. If your client lists MCP servers, this one fits.

14 tools

Posts, deliveries, accounts, workspaces, and three AI helpers.

Scoped API key

One key per workspace, limited to the scopes you grant.

Install

Add it to the client you already use

Create an API key in the dashboard, paste the mcpServers block into your client’s config, and restart. The server runs locally over stdio and only talks to the API with the key you gave it.

See per-client setup

Terminal

# Runs with no install step
FOPOST_API_KEY=your-api-key npx -y @fopost/mcp

Runs via npx

No global install. The package is fetched on first run and cached.

One config block

The same JSON works in Claude Desktop, Cursor, Windsurf, and others.

Key stays local

The key lives in your client config and is sent only to the API.

Tools

Everything the dashboard can do with posts

The tool set covers the full post lifecycle: schedule, edit, cancel, delete, and list, plus delivery status per network. Account and workspace tools let the client discover what it can post to before it tries.

Browse the tools

Tools

list_posts        get_post           schedule_post
edit_post         cancel_post        delete_post
list_post_deliveries               list_accounts
get_account_health                 list_workspaces
generate_caption  rewrite_for_platforms
repurpose_url     get_ai_credits

Post lifecycle

Create, change, cancel, and remove posts from any client.

Delivery status

See which network received a post and which did not.

AI helpers

Caption, per-network rewrite, and URL repurposing use your AI credits.

Safety

Built for agents that ask first

The server never publishes on its own. It only acts inside a tool call your client sent, and most clients show that call before it runs. Scopes on the API key limit what the tools can reach.

Get your API key

A month of scheduled posts on the publishing calendar

No autonomous publishing

A tool call is required for every write. Reads never change anything.

Workspace isolation

A key reaches one workspace. Client accounts never mix.

Revoke any time

Rotate or delete the key in the dashboard and the server stops instantly.

MCP Server questions, answered

Which clients are supported?

Any client that runs local MCP servers over stdio: Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Gemini CLI, OpenClaw, and others.

Is there a remote or hosted MCP endpoint?

Not yet. The server runs locally via npx. Clients that require a remote URL are not supported today.

What does it cost?

The package is open source and free. It uses your FoPost plan; only the three AI tools consume AI credits.

Which scopes does the key need?

posts, accounts, workspaces, and deliveries cover scheduling and checks. Add publish to let it post, and ai for the AI tools.

Can it read analytics?

Not through MCP today. Analytics are available in the dashboard and through the REST API with the analytics scope.

Where is the source?

The package is published on npm as @fopost/mcp under the MIT license, with the repository linked from the package page.

Run FoPost from MCP Server

Starting is free and the MCP server is included. Create a key, add the server, and schedule your first post from your agent.

Get your API key