Postifys
MCP for Cursor & Claude

Give agents your Postifys publish tools

Install postifys-mcp, set your API key, and let Cursor or Claude list connections, upload media, publish, poll status, and manage Content Queue — against live postifys.com.

Latest 0.1.0 · 17 tools · Env: POSTIFYS_API_KEY · Free MCP package

How it works

MCP is a thin tool layer. Postifys keeps OAuth tokens; the agent only calls production HTTP with your API key.

Add the MCP server

In Cursor or Claude Desktop MCP settings run npx -y postifys-mcp with POSTIFYS_API_KEY.

Discover accounts

Call postifys_list_connections, then upload media to get a public serve_url.

Publish and poll

Use postifys_publish (async), then postifys_get_post_status until terminal. Or schedule via Content Queue tools.

Honest limits: TikTok may post to inbox depending on approval; LinkedIn is member profiles; Pinterest needs a board. Prefer media upload before publish — not raw Drive URLs. The MCP package is free; publishing needs a Postifys seat ($4 for the first seat, then $2 per extra seat per month after trial).

Tool catalog (17 tools)

Same production routes as the n8n node, plus native Content Queue tools that n8n does not ship yet.

Discovery

  • postifys_pingValidate API key / auth
  • postifys_list_connectionsConnected accounts (filter by platform)
  • postifys_list_pinterest_boardsBoards for Pin publish
  • postifys_tiktok_creator_infoPrivacy / interaction options

Media

  • postifys_media_uploadQueue URL, poll until serve_url
  • postifys_media_statusPoll by mediaJobId

Publish

  • postifys_publishOne tool · six platforms · always async
  • postifys_get_post_statusPoll until published / failed

Content Queue

  • postifys_cq_overviewTables + jobs snapshot
  • postifys_cq_list / create tablesData tables for rows
  • postifys_cq_list / create jobsSchedule ≥ 15 minutes
  • postifys_cq_add_item / import_rowsPending rows without n8n
  • postifys_cq_run_job_nowManual run when destinations ready

Supported platforms

Connect accounts in the Postifys dashboard, then pass the returned account ids into postifys_publish.

Facebook Pages

Image, Reel, Stories, and text feed posts. Use page id from connections.

Instagram

Professional image / Reel / Stories. FEED is mapped to REEL. Media required.

YouTube

Video upload with privacy (private / unlisted / public). Title + video URL required.

Pinterest

Image Pins only. boardId required. Video Pins are not claimed.

LinkedIn

Member profiles only — Company Pages are not supported.

TikTok

May land in creator inbox. Direct Post needs approval, consent, and music confirmation.

Install in Cursor

Create an API key in Settings with scopes connections, media, publish, and status. OAuth stays on Postifys — MCP never stores social tokens.

Cursor · mcpServers.postifys
{
  "command": "npx",
  "args": ["-y", "postifys-mcp"],
  "env": {
    "POSTIFYS_API_KEY": "pfs_...",
    "POSTIFYS_SERVER_URL": "https://postifys.com"
  }
}
Claude Desktop · same shape
{
  "mcpServers": {
    "postifys": {
      "command": "npx",
      "args": ["-y", "postifys-mcp"],
      "env": {
        "POSTIFYS_API_KEY": "pfs_..."
      }
    }
  }
}
Credential validation
GET https://postifys.com/api/key/test
Authorization: Bearer YOUR_API_KEY

Recommended agent workflow

Keep publish idempotent and always poll async jobs. Content Queue intervals are at least 15 minutes on production.

1. List connections

Pick the exact account id for the platform. Never guess page or channel ids.

2. Upload media

postifys_media_upload for Drive/Dropbox/remote URLs. Wait for serve_url.

3. Publish + poll

postifys_publish returns postId. Call postifys_get_post_status until published or failed.

Sample prompts

List my Instagram connections, upload this Drive MP4 via Postifys media, then publish a Reel and poll until terminal.

Create a Content Queue table named agent-drafts, add one pending row with this serve_url, and do not enable the schedule.

Fetch TikTok creator_info for my connected account, then explain whether Direct Post or inbox upload applies.

MCP vs n8n

Both are free client packages over the same Postifys API. Choose based on how you automate.

postifys-mcp

Best for Cursor / Claude agents. Interactive tool calls, Content Queue tools included, stdio via npx.

n8n-nodes-postifys

Best for durable workflows, schedules, and visual graphs. Install from Community Nodes.

Shared backend

Same keys, connections, media proxy, publish workers, and billing entitlement on postifys.com.

FAQ

Short answers for setup, limits, and billing.

Where do I create an API key?

Sign in → Settings. Include scopes connections, media, publish, and status. Session-only routes (billing portal, key CRUD UI, OAuth connect) stay in the dashboard — not MCP tools.

Why did publish return 402?

Publishing requires an entitled Postifys account. Trial is 7 days (card required) for 1 seat, then $4 for the first seat, then $2 per extra seat per month. The MCP package itself remains free on npm.

Can I pass Google Drive links to publish?

No. Call postifys_media_upload first. The tool rejects raw Drive/Dropbox URLs on publish and asks for a serve_url.

Is there a hosted remote MCP URL yet?

v1 is local stdio (npx postifys-mcp). A hosted Streamable HTTP endpoint may come later for cloud agents; not required for Cursor Desktop today.