Add the MCP server
In Cursor or Claude Desktop MCP settings run npx -y postifys-mcp with POSTIFYS_API_KEY.
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.
MCP is a thin tool layer. Postifys keeps OAuth tokens; the agent only calls production HTTP with your API key.
In Cursor or Claude Desktop MCP settings run npx -y postifys-mcp with POSTIFYS_API_KEY.
Call postifys_list_connections, then upload media to get a public serve_url.
Use postifys_publish (async), then postifys_get_post_status until terminal. Or schedule via Content Queue tools.
Same production routes as the n8n node, plus native Content Queue tools that n8n does not ship yet.
serve_urlmediaJobIdConnect accounts in the Postifys dashboard, then pass the returned account ids into postifys_publish.
Image, Reel, Stories, and text feed posts. Use page id from connections.
Professional image / Reel / Stories. FEED is mapped to REEL. Media required.
Video upload with privacy (private / unlisted / public). Title + video URL required.
Image Pins only. boardId required. Video Pins are not claimed.
Member profiles only — Company Pages are not supported.
May land in creator inbox. Direct Post needs approval, consent, and music confirmation.
Create an API key in Settings with scopes connections, media, publish, and status. OAuth stays on Postifys — MCP never stores social tokens.
POSTIFYS_API_KEYPOSTIFYS_SERVER_URL (default https://postifys.com){
"command": "npx",
"args": ["-y", "postifys-mcp"],
"env": {
"POSTIFYS_API_KEY": "pfs_...",
"POSTIFYS_SERVER_URL": "https://postifys.com"
}
}
{
"mcpServers": {
"postifys": {
"command": "npx",
"args": ["-y", "postifys-mcp"],
"env": {
"POSTIFYS_API_KEY": "pfs_..."
}
}
}
}
GET https://postifys.com/api/key/test
Authorization: Bearer YOUR_API_KEY
Keep publish idempotent and always poll async jobs. Content Queue intervals are at least 15 minutes on production.
Pick the exact account id for the platform. Never guess page or channel ids.
postifys_media_upload for Drive/Dropbox/remote URLs. Wait for serve_url.
postifys_publish returns postId. Call postifys_get_post_status until published or failed.
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.
Both are free client packages over the same Postifys API. Choose based on how you automate.
Best for Cursor / Claude agents. Interactive tool calls, Content Queue tools included, stdio via npx.
Best for durable workflows, schedules, and visual graphs. Install from Community Nodes.
Same keys, connections, media proxy, publish workers, and billing entitlement on postifys.com.
Short answers for setup, limits, and billing.
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.
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.
No. Call postifys_media_upload first. The tool rejects raw Drive/Dropbox URLs on publish and asks for a serve_url.
v1 is local stdio (npx postifys-mcp). A hosted Streamable HTTP endpoint may come later for cloud agents; not required for Cursor Desktop today.
Same API as n8n — pick MCP for agents or the community node for workflows.