CursorAgents

FoPost for Cursor

Register the FoPost MCP server in Cursor and its agent can turn a merged PR into posts for every connected account. It shows each tool call before running it, so nothing goes live without you.

Get your API key All agents

.cursor/mcp.json

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

Project or global

Put the config in .cursor/mcp.json for one repo or in your user settings for all of them.

Approval first

Cursor shows the tool call and waits. The server never publishes on its own.

14 tools

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

Setup

One JSON file, then it is part of the agent

Create an API key in the FoPost dashboard, add the mcpServers block to .cursor/mcp.json, and confirm the server shows green under Settings > MCP. The agent can then list accounts and schedule posts.

Set up Cursor

Agent chat

> List my connected accounts.

Cursor: list_accounts → LinkedIn, X, Bluesky, Mastodon
in workspace "Product". All healthy.

Scoped key

Give the agent only the scopes it needs. Revoke from the dashboard.

Workspace per key

The agent sees one workspace, never another client’s accounts.

Status check

Settings > MCP shows whether the server connected and which tools loaded.

Ship and announce

From diff to announcement in one chat

Cursor already has the changes in context. Ask it to write a release post per network and schedule them. It uses rewrite_for_platforms for the variants and schedule_post for the times, then reports the post ids.

Try it on your next release

rewrite_for_platforms

A thread for one network and a paragraph for another, from one draft.

repurpose_url

Point it at the changelog page and get a series of posts.

schedule_post

Named times or the next open slot in your queue.

Verify

Confirm it landed before you close the tab

Ask the agent whether the release post delivered everywhere. It reads deliveries per network and flags accounts that need a reconnect, without switching to a browser.

Get your API key

Agent chat

> Did the release post go out?

Cursor: list_post_deliveries → 4 of 4 delivered.
Links: x.com/... linkedin.com/... bsky.app/... mastodon.social/...

list_posts

Recent posts with status, by account or label.

get_account_health

Tokens that need attention before the next post.

get_ai_credits

Balance check before a large rewrite.

Cursor questions, answered

Where does the config go?

Project scope: .cursor/mcp.json in the repo. Global scope: ~/.cursor/mcp.json. Both use the same mcpServers block.

Does it work in Composer and Chat?

MCP tools are available to the agent mode. Check Settings > MCP to confirm the server is connected.

Will it post without asking?

No. Cursor shows the tool call for approval and the server only acts inside an approved call.

Should I commit the key?

No. Keep the key out of the repo by using your global config or an environment variable your shell provides.

Does it use my AI credits?

Only the three AI tools do. Scheduling, listing, and delivery checks are free of credits.

Can I manage several workspaces?

Add a server entry per workspace with its own key. Each entry only reaches its own workspace.

Run FoPost from Cursor

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