Browse docs
The connection#
Add a social media MCP node for n8n#
- Add an MCP Client Tool node (n8n-nodes-langchain.toolmcp) to your workflow, or install the community node n8n-nodes-mcp if you're on an n8n version without it built in.
- Set the endpoint to
https://api.skedcast.com/mcpand the connection type to Streamable HTTP (SSE is deprecated across MCP clients generally — use HTTP). - For authentication, choose Header Auth and send
Authorization: Bearer sked_live_YOUR_KEY— SkedCast's MCP server accepts an API key as a bearer token exactly like the REST API, which avoids setting up an interactive OAuth flow on a server with no browser to complete it in. - Wire the MCP Client Tool's output into an AI Agent node's Tool input, and the agent can call any tool your key's scopes allow.
mcpn8nautomationai agent
FAQ
- Which n8n node should I use — the built-in one or the community package?
- Newer n8n versions ship an MCP Client Tool node (n8n-nodes-langchain.toolmcp) built in for use inside AI Agent workflows; if yours doesn't have it, the community node n8n-nodes-mcp provides equivalent functionality.
- Does the node support the older SSE transport?
- It can, but SSE is being phased out in favor of Streamable HTTP across the MCP ecosystem — SkedCast's server is Streamable HTTP, so configure the node for that transport, not SSE.