Skip to content
PostFastHelp

Does PostFast have an API and an MCP server, and which plans include them?

Yes to both, and every plan includes them, including the 7-day free trial. Schedule posts from your own code, from n8n, Make or Zapier, or from Claude, ChatGPT, and Cursor.

Updated 2026-10-042 min read

The REST API and the MCP server are included on every plan, including the 7-day trial. There is no per-seat and no per-request add-on.

Get your API key

  1. Open API in the sidebar. It takes you to your workspace's API tab.
  2. Click Generate API Key.
  3. Copy the key immediately. It is shown only once.

Each workspace has one active API key, and only workspace admins can generate it. Regenerating invalidates the old key straight away.

Send the key in the pf-api-key request header. The base URL is https://api.postfa.st/.

REST API

  • POST /social-posts creates and schedules up to 15 posts per request. Every platform-specific option is a field on the request: Instagram publish type, TikTok settings, YouTube title and privacy, the Pinterest board, LinkedIn documents, Google Business Profile post types, and more.
  • GET /social-posts can filter by account: pass socialMediaIds with the account ids from GET /social-media/my-social-accounts.
  • POST /social-posts/bulk-delete deletes up to 100 posts in one request. Deleting removes posts from PostFast only, so an already-published post stays live on the social platform.
  • Media: up to 250 MB per video, 10 MB per image, and 60 MB per document.
  • scheduledAt must be in the future and within 1 year.
  • Rate limits: each endpoint has its own limits per API key (per minute, per 5 minutes, per hour and per day). Going over one returns HTTP 429 with a Retry-After header that says how many seconds to wait. The limits for every endpoint are listed in the API reference at postfa.st/docs.

Full reference: postfa.st/docs. There is also a Markdown twin at postfa.st/docs.md for pasting into an AI assistant.

No-code options live at postfa.st/api-integrations: an n8n node, Make, and Zapier.

MCP server for AI assistants

Two ways to connect, same account, same 11 platforms. Twenty-two tools are common to both, and the difference is transport, not plan.

Local, over stdio - for Claude Code, Cursor, VS Code, Windsurf, Zed, JetBrains, and any MCP client. Add npx -y postfast-mcp with your API key to the client's MCP configuration. It exposes 24 tools: accounts and posts (list, create, delete, analytics, follower history), media upload, Pinterest boards, YouTube playlists, Google Business Profile locations, TikTok sounds, places for geotags, connect links, and 10 Social Inbox tools (list, reply, private reply, hide/delete, assign, mark read, set status).

Hosted, over OAuth - for ChatGPT and the Claude app, where there is no local process to run. Add the connector URL https://mcp.postfa.st/mcp. It signs in over OAuth instead of an API key and exposes 26 tools: the same core set, minus the local signed-upload-URL tool, plus approve_posts, list_workspaces, and upload_from_url.

To check either one is wired up, run MCP Inspector and confirm the tool list appears.

Was this article helpful?

Related articles