Tools Reference
Every tool the FoPost MCP server exposes, with parameters and caveats.
Fourteen tools, in three groups. Ids are UUIDs throughout, and every tool returns the API's JSON response as text. The server exposes tools only: no MCP resources or prompts.
Posts
Need the posts scope.
list_posts
List posts in a workspace, newest first.
| Parameter | Required | Notes |
|---|---|---|
workspace_id | Yes | |
status | No | draft, pending_approval, scheduled, published, failed, or cancelled |
limit | No | 1–100, default 20 |
offset | No | Default 0 |
get_post
Fetch one post by id, with content, settings, and delivery records.
schedule_post
Create a post as a draft, scheduled, or published immediately.
| Parameter | Required | Notes |
|---|---|---|
workspace_id | Yes | |
content | Yes | The post body text |
account_ids | Yes | At least one target account |
schedule_at | No | ISO 8601. Omit to save a draft |
publish_now | No | Publishes right after creating |
media_urls | No | Already-uploaded media URLs; attached as images |
labels | No | Label ids |
With publish_now, the server creates the post and then calls the publish endpoint, returning the publish response. Media passed by URL is attached as image media. Video attachments need the API or the dashboard.
edit_post
Update a post's content, schedule_at, or labels; only the fields you pass change. One caveat: passing content replaces the post's content block, which drops any media the post carried. Accounts cannot be changed through this tool.
cancel_post / delete_post
cancel_post stops a scheduled post from publishing; the post stays. delete_post removes it permanently: it cannot be undone, so it is worth an approval step in your MCP client.
list_post_deliveries
Per-account delivery status for a post: queued, publishing, published, or failed, per account.
Accounts and workspaces
Need the accounts scope; list_workspaces needs workspaces.
list_accounts
Connected accounts in a workspace: platform, username, primary flag, connection status. Takes workspace_id.
get_account_health
Token freshness and rate-limit headroom for one account_id. The first tool to reach for when posts are failing: it tells you whether the connection has expired.
list_workspaces
Every workspace the key can reach. No parameters. Usually the first call an assistant makes.
AI
Need the ai scope, and spend AI credits.
generate_caption
Write or improve a caption. All parameters optional: current_caption to improve an existing draft, platforms for tone-aware output, char_limit, workspace_id.
get_ai_credits
The current credit balance, usage this period, and reset date. Free: reading the balance costs nothing.
rewrite_for_platforms and repurpose_url are also registered, but they reach
endpoints that require a dashboard session, so they answer 401 with an API
key. Everything else on this page works.
Errors
A failed call comes back as an error message, not an exception: a 403 names the missing scope, a 402 means the AI credit balance ran out, and a 429 means the key hit its rate limit. The server does not retry, so the assistant sees it immediately.
Next
Related documentation
- MCP Server
Connect Claude, Cursor, or any MCP client to your FoPost workspace.
- Media
Upload files, list the media library, and attach media to a post.
- AI
What an API key can do with AI, and where the rest of the AI features live.