n8n social media automation: post to every network through MCP
n8n's own social nodes cover a few networks, without queues or video on X. How to connect n8n to a scheduler over MCP, and keep unattended workflows safe.
Short answer
Point n8n's MCP Client node, or the MCP Client Tool inside an AI Agent, at a scheduler's MCP server. For PostDaily that is https://mcp.postdaily.app/key/mcp, with an API key as a Bearer header and the HTTP Streamable transport. n8n can then draft, queue or schedule posts on every network PostDaily publishes to.
n8n's own social nodes, and where they stop
| n8n node | What it posts | What it can't do |
|---|---|---|
| X (Twitter) | Text posts and replies | Upload media; post a thread in one step |
| Text, an article link or an image, as a person or a Page | Video, PDF documents, several images, first comments | |
| Facebook Graph API | Any Graph API call you write yourself | Nothing post-shaped; Instagram means building Meta's upload flow by hand |
| YouTube | Video uploads | Anything but YouTube |
n8n has no built-in node for Instagram, TikTok, Threads, Pinterest, Bluesky or Mastodon. None of its social nodes keeps a queue, checks a post against a network's limits or retries a failed publish; timing comes from the workflow's own Schedule Trigger. A scheduler's MCP server fills those gaps: n8n decides when and what, and the scheduler checks, queues and publishes.
Two ways to use MCP in n8n
- MCP Client (n8n 1.122.0, November 2025): an ordinary workflow step. You pick one tool, such as creating a post, and fill in its fields. Predictable, and no AI model needed.
- MCP Client Tool (n8n 1.88.0, April 2025): plugs into an AI Agent node, which decides which tools to call. Useful when the workflow should write or choose posts itself.
Use the HTTP Streamable transport, n8n's default since 1.114.0. Older versions of the Tool offered only Server-Sent Events, which PostDaily doesn't serve. For chat apps rather than workflows, see how to schedule social media posts with MCP.
Connect n8n to PostDaily
- 1In PostDaily, open Settings → AI agents, choose API key, name it after the workflow, pick an access level and the workspaces it needs, and set an expiry. Copy the key: it is shown once.
- 2In n8n, add an MCP Client node (or an MCP Client Tool under an AI Agent).
- 3Set the transport to HTTP Streamable and the endpoint to https://mcp.postdaily.app/key/mcp.
- 4Choose Bearer Auth and paste the key as the token.
- 5Pick the tool that lists your channels and run the node to check the connection.
Connect with an API key has the same settings for Make and your own scripts.
Three workflows to start with
- New blog post to drafts. An RSS trigger creates a draft for each channel, and someone checks and schedules it in PostDaily. A Drafts only key is enough.
- Spreadsheet to queue. Rows from a sheet go into the queue, up to 50 posts in one call. This needs full access.
- Weekly results digest. A Schedule Trigger reads your analytics every Monday and sends them to Slack or email. A Read only key is enough.
Keep unattended workflows safe
- One key per workflow, so revoking one doesn't break the others, and Settings → AI agents shows which was used last.
- Drafts only for anything that writes without a person watching. PostDaily refuses to publish immediately unless the call confirms a person agreed, but a workflow with full access can send that confirmation itself.
- Send an idempotency key with every write. If n8n retries a step within 24 hours, PostDaily returns the first result instead of creating a second post.
- Let keys expire. Keys last 30 days, 90 days, a year or forever, and changing your password revokes them all. What an AI agent can safely do explains the other controls, and PostDaily for AI agents lists what each access level allows.
n8n social media questions
Can n8n post to Instagram or TikTok?
Not with a built-in node. Through a scheduler's MCP server it can, wherever that scheduler publishes.
Do I need an AI Agent node to use MCP in n8n?
No. Since n8n 1.122.0, the MCP Client node runs as an ordinary workflow step.
Which transport should I choose?
HTTP Streamable. PostDaily doesn't serve the older Server-Sent Events transport.
Can n8n schedule posts for later?
Yes. Either the workflow runs at the time you want, or it hands the post to the scheduler with a time or adds it to a channel's queue.
Last checked against n8n's docs, changelog and node source, and PostDaily's MCP server.
