MCP Automation: Make, Zapier & n8n with Postory

MCP automation can turn a new idea into an X, Threads or Bluesky draft without copying text between apps. First connect your social account to Postory, then connect your automation client to Postory's MCP server. This guide gives each client a safe first call and separates exercised paths from tools only shown in a menu.

Before you connect: accounts and permissions

Create a Postory account, open Accounts, and connect the X, Threads or Bluesky identity your workflow will use. Import its posts if you want to analyze old content; drafting needs no import.

The server URL is https://postory.io/mcp. Each client opens Postory's OAuth consent screen. Review the permissions: draft access is available; publishing and reading imported data are separate choices. Grant only what the workflow needs. Sign in to Postory before starting a Make or Zapier popup; signing in with X inside the popup can break its return to the client.

After authorization, run list_accounts. This read-only call shows platforms, connection states and IDs. Copy the target connection_id from this client's own grant. An ID from another Postory login will not work here. If needs_reconnect is true, reconnect on the Accounts page. If can_publish is false for another reason, follow the returned hint before planning delivery.

Make MCP Client: connect and read first

In a Make scenario, add MCP Client → Call a tool, then create a connection. Choose + New MCP Server, enter the Postory URL, leave the API key field blank and save. Approve the Postory consent screen that opens. These are the connection controls in Make's MCP Client documentation.

Choose list_accounts as Tool Name and run it with no arguments. Add another Call a tool module for get_performance_summary, map the Threads connection_id from the first result and set days to 30. That Threads read succeeded in a real Make module. If the account has no imported data, import it rather than treating an empty result as zero engagement.

For a draft workflow, call create_draft with parts (ordered post text) and that account's connection_id. Inspect the saved draft. Make also offers Execute an action with AI; select only relevant read and draft tools. If you change Tool Name in an existing module, refresh its fields or add a new module to clear old arguments.

Zapier MCP Client: map a result into a draft

In Zapier Apps, add an MCP Client connection. Set Server URL to https://postory.io/mcp, Transport to Streamable HTTP, and OAuth to Yes. Leave Bearer Token empty, continue, then approve access in Postory. Zapier's connection guide names those controls and the Run Read-Only Tool and Run Tool actions.

Start a Zap with Run Read-Only Tool → list_accounts. Select the intended connection. A following Run Tool → create_draft step can map that ID and a parts value built from the trigger's text. When Zapier shows parts as a text field, enter a JSON array such as [{"text":"Your reviewed idea"}]; plain prose is not an array. Test the step, then use list_drafts or get_draft to confirm the text and account. This OAuth, account read and draft sequence was exercised in Zapier. Saving a private draft does not publish it.

n8n MCP Client: run a Threads read

Add the regular MCP Client node to a workflow, set Server Transport to Streamable HTTP, MCP Endpoint URL to the Postory URL and Authentication to OAuth2. In the MCP OAuth2 API credential, leave Use Dynamic Client Registration on, then sign in and approve Postory's permissions. The n8n MCP Client node docs distinguish this workflow node from MCP Client Tool, which attaches tools to an AI Agent.

Select list_accounts and execute the node. Next, select get_performance_summary, set days to 30 and map the Threads ID from the prior output. Use JSON input mode for nested arguments. This OAuth and Threads read succeeded in a clean local n8n test against Postory production. A self-hosted editor needs HTTPS or a literal loopback origin for OAuth. Locally, use the callback's hostname: localhost and 127.0.0.1 are different cookie hosts.

MCP automation from draft to approved publish

A first workflow is source event → list_accounts → create_draft → get_draft. Check the text, platform and unscheduled status. Create a separate draft for each platform; cross-platform bulk creation is unavailable. Make and n8n completed Threads reads; Zapier completed account and draft calls.

To publish from a Make, Zapier or n8n workflow, first enable Manually approve publishing & scheduling in Postory in Postory settings. Then call preflight_publish for the exact draft and account; include scheduled_at if scheduling. It checks platform rules and shows the price and preview; it sends nothing. Give the returned approval_url to a human, who must sign in to Postory and approve that exact delivery. Only then may the workflow call publish_draft or schedule_draft with the confirmation token; the token expires after 10 minutes. If your workflow has no human approval path, stop at the draft. A trigger or tool step alone is not approval. Check delivery status and the public link before reporting a post live. This client-level publish sequence has not been verified in all three automation clients.

Costs, platform limits and common failures

Reading imported data and managing drafts use no Postory credits. Publishing and X imports can cost credits; preflight shows the delivery's exact price. Make, Zapier and n8n have separate plan, operation or AI-provider charges. Check your client plan before a high-volume workflow. Make and Zapier label MCP Client beta, so their controls and pricing can change.

Use the limits returned by list_accounts for the target account. Postory currently allows up to 25,000 characters on X, 500 characters and at most five links on Threads, and 300 graphemes on Bluesky. A draft may save with validation issues, but preflight refuses a delivery until you fix them. If a read returns not_found, run list_accounts again in that same OAuth connection instead of pasting an ID from another client. If a publish step returns a scope error, revisit consent; if the social connection needs reconnection, do that in Postory. Do not assume a client will renew its OAuth token after a day: renewal has not yet been verified for these three clients.

Start automating social drafts with Postory

Explore Postory's live MCP setup guides, connect the social accounts you need, then run the read-only first call in your client. Try Postory free and keep your initial workflow at the draft stage until its mapped account and review step work as intended.