OpenClawAgents

FoPost for OpenClaw

Add the FoPost MCP server to your OpenClaw agent configuration and the agent gains scheduling, delivery, and account tools. Writes only happen inside a tool call, so you keep an approval step in front of publishing.

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

Standard MCP

Stdio server, plain mcpServers config. No custom adapter.

Approval in your loop

Keep a human step before schedule_post. The server never publishes on its own.

14 tools

Posts, deliveries, accounts, workspaces, and AI rewriting.

Setup

One config entry for the whole tool set

Create an API key in the FoPost dashboard, add the mcpServers entry to your OpenClaw agent config, and restart the agent. Ask it to list accounts to confirm the tools loaded.

Set up OpenClaw
Agent run
> List connected accounts.

Agent: list_accounts → LinkedIn, X, Mastodon in
workspace "Main". All healthy.

Scoped key

Give an autonomous agent read scopes first, and add publish only when you trust it.

Workspace per key

One key reaches one workspace, never another client’s.

Verify first

A read call confirms the server before any write.

Automate

Let the agent prepare, and you approve

A scheduled OpenClaw run can gather sources, draft with rewrite_for_platforms or repurpose_url, and queue with schedule_post. Put a confirmation gate on the write tools so the run stops and asks before anything is queued.

Build the workflow
The agent drafting posts for several networks in a saved brand voice

rewrite_for_platforms

Per-network versions from one draft.

repurpose_url

A URL becomes a series of posts.

schedule_post

Named times or the next open slot.

Monitor

Read back what happened

The same agent can check deliveries, account health, and remaining AI credits on a schedule and report to you. Reads never change anything.

Get your API key
Agent run
> Report on yesterday's posts.

Agent: list_post_deliveries → 5 of 6 delivered.
Threads failed: token expired. get_ai_credits → 412 left.

list_posts

Recent posts with status and filters.

get_account_health

Which tokens need a reconnect.

get_ai_credits

Balance before the next run.

OpenClaw questions, answered

Where does the config go?

In the mcpServers section of your OpenClaw agent configuration. Restart the agent after editing.

Can the agent post without a human?

Only if you grant the publish scope and no approval gate. We recommend keeping a confirmation step in front of schedule_post.

Does it need Node?

Yes. The server runs through npx, so a current Node runtime must be available to the agent.

Does it use my AI credits?

Only generate_caption, rewrite_for_platforms, and repurpose_url do. Scheduling and checks are free of credits.

Can it read analytics?

Not through MCP today. Use the REST API with the analytics scope for that.

Can I run several agents?

Yes. Give each agent its own key, ideally its own workspace, so their actions stay separate and revocable.

Run FoPost from OpenClaw

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