# Connect n8n to SkedCast with MCP
URL: https://skedcast.com/developers/guides/mcp-n8n

n8n's MCP Client Tool node turns a remote MCP server into tools an AI Agent node can call inside a workflow. Point it at SkedCast's endpoint, sign in once with an MCP OAuth2 credential, and connect it to your agent's tool input.

## The connection
Property | Value
Endpoint | `https://api.skedcast.com/mcp`
Transport | Streamable HTTP
Auth | OAuth 2.1: the client runs the sign-in for you. The MCP server does not accept API keys.
SkedCast plan | MCP access depends on your SkedCast plan (see pricing).
Tools | 79 tools: 44 that read and 35 that change your workspace. See the MCP tools reference for the full list.

## Last checked 2026-11-04
These steps follow n8n's documentation as of 2026-11-04. Menus and plan rules change. If a step differs in your version, follow n8n's page: https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.toolmcp/

## 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.

## No browser on the server?
Complete the OAuth2 sign-in once from the n8n editor in your browser. The credential then refreshes itself. If you would rather use an API key, call the REST API with n8n's HTTP Request node instead of MCP.

## Plan requirement
n8n's documentation for this node states no plan requirement. Check it for your n8n version. SkedCast's MCP access depends on your SkedCast plan (see the table above).

## Write tools change your workspace
The write tools (the ones that create, edit, reschedule, cancel or delete things) are marked non-read-only. A well-behaved MCP host asks you to confirm before the agent calls one. The agent's effective power is always your scopes ∩ your access, so it can never do more than you could do by hand.

## FAQ
**Q: Which authentication should I choose in n8n?**
A: 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.

**Q: Which transport should I pick?**
A: 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.