n8n social media scheduling: how it connects#
n8n social media scheduling connects through the built-in MCP Client Tool node — no community package needed. Point it at SkedCast's MCP endpoint, attach it to an AI Agent node, and the workflow can schedule or check posts across every connected account.
1. Add the MCP Client Tool node#
In your workflow, add the MCP Client Tool node (attach it to an AI Agent node so the agent can call SkedCast's tools directly), or the plain MCP Client node for a direct trigger/action step. Both ship natively in n8n since v1.88 — no community node install required.
2. Point it at SkedCast#
Set Server Transport to HTTP Streamable and the MCP Endpoint URL to https://api.skedcast.com/mcp. n8n fetches SkedCast's tool list automatically once connected.
3. Add credentials#
Create a credential for the node — a SkedCast API key as a Bearer token is the simplest path; OAuth2 is also supported if you'd rather authorize interactively.
Known limitations#
| What to know |
|---|
An older, unrelated community package (n8n-nodes-mcp) predates the native nodes — you don't need it; use the built-in MCP Client Tool / MCP Client nodes instead. |
FAQ
- Do I need a community node to connect n8n to SkedCast's MCP server?
- No. n8n has shipped a native MCP Client Tool node since v1.88 (April 2025) — add it to a workflow and point it at SkedCast's MCP URL directly.
- What can an agent do once it's connected?
- Whatever your SkedCast role and plan allow — the connection acts as you, not with elevated access. Read posts and analytics, schedule and revise posts, and act on approvals, all through the same tools listed on the MCP hub.