Zapier social media scheduling: how it connects#
Zapier social media scheduling runs through "MCP Client by Zapier" inside a Zap, pointed at SkedCast's remote MCP endpoint. Once connected, a Zap can schedule or check posts across every connected account as a trigger or action step.
1. Add the MCP Client app to a Zap#
In a Zap, add a step and search for "MCP Client" (by Zapier) — not "Zapier MCP", which is a different, unrelated product that exposes Zapier's own actions to outside AI clients rather than connecting Zapier out to one.
2. Connect to SkedCast#
Create a new MCP Client connection and enter SkedCast's server URL: https://api.skedcast.com/mcp. Zapier's exposed tools become available as trigger/action steps in the Zap once connected.
Known limitations#
| What to know |
|---|
| Zapier ships two MCP products going opposite directions: "Zapier MCP" exposes Zapier's own 9,000+ app actions to external AI clients (not relevant here); "MCP Client by Zapier" is the one that connects Zapier out to a server like SkedCast's — use the second. |
Zapiermcpai agents
FAQ
- Is "Zapier MCP" the same as "MCP Client by Zapier"?
- No — they run in opposite directions. Zapier MCP exposes Zapier's own actions as tools to other AI clients. MCP Client by Zapier is the app that lets a Zap call an external MCP server like SkedCast's, and is the one you want here.
- 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.