Browse docs
The connection#
Add SkedCast to an n8n workflow#
- Add the MCP Client Tool node to your workflow, as a sub-node of an AI Agent.
- Enter the SkedCast endpoint from the table above. n8n's documentation labels this field SSE Endpoint. If your version of the node has a transport setting, choose HTTP Streamable, which is what SkedCast's MCP server uses, and check n8n's documentation for the transports your version supports.
- For authentication, choose MCP OAuth2 and create the credential. n8n opens the SkedCast sign-in once. After you approve, n8n keeps the connection signed in with the refresh token, so the workflow runs unattended. The MCP server does not accept API keys.
- Connect the MCP Client Tool to the AI Agent node's tool input. The agent can then call any tool the scopes you approved allow.
mcpn8nautomationai agent
FAQ
- Which authentication should I choose in n8n?
- MCP OAuth2. The SkedCast MCP server accepts only OAuth access tokens, so Bearer Auth or Header Auth with an API key is refused. For API-key automation, use the REST API through n8n's HTTP Request node.
- Which transport should I pick?
- Pick HTTP Streamable if your version of the node offers it. It is the transport SkedCast's MCP server uses. n8n's documentation lists what each version supports.