1. Add the MCP Client Tool node#
In your workflow, add the MCP Client Tool node as a sub-node of an AI Agent, so the agent can call SkedCast's tools.
2. Point it at SkedCast#
Enter https://api.skedcast.com/mcp as the endpoint (n8n's documentation labels the field "SSE Endpoint") and choose HTTP Streamable as the transport. n8n fetches SkedCast's tool list once the node connects.
3. Add credentials#
Under Authentication, choose MCP OAuth2, create the credential and sign in to SkedCast once. n8n then refreshes the connection itself, so the workflow runs unattended. To use an API key instead, call the REST API from an HTTP Request node rather than MCP.
Requirements#
Before you connect:
- SkedCast: a plan that includes MCP access (see pricing). The connection acts as you, with your role and plan limits.
- n8n: no plan requirement is documented. If the node is missing, update n8n.
- SkedCast's MCP server uses Streamable HTTP. A node version that offers only SSE cannot connect, so update n8n.
n8nmcpai agents
FAQ
- Do I need a community node to connect n8n to SkedCast's MCP server?
- No. The MCP Client Tool node is part of n8n. Add it to a workflow and point it at SkedCast's MCP URL.
- 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. It can read posts and analytics, schedule and revise posts, and act on approvals, through the tools listed on the MCP hub.