Make social media scheduling: how it connects#
Make social media scheduling runs through Make's outbound MCP client (not its inbound MCP server) pointed at SkedCast's remote MCP endpoint. Once connected, a Make scenario can schedule or check posts across every connected account, with OAuth or a token handling authentication.
1. Add the MCP Client app#
In a Make scenario, add the MCP Client app — not "Make MCP Server", which is the opposite direction (exposing your Make scenarios as tools to outside AI clients).
2. Connect to SkedCast#
Enter SkedCast's server URL (https://api.skedcast.com/mcp) since it isn't in Make's pre-verified server list, then authorize — OAuth or an API key, depending on how your SkedCast credential was issued.
3. Pick a module#
"Call a tool" runs one specific SkedCast tool with a JSON request you build; "Execute an action with AI" lets Make's own AI agent choose which tool to call from a plain-language instruction.
Known limitations#
| What to know |
|---|
| Make's own docs mark MCP Client as a beta feature — functionality and pricing may change. |
| Available starting on Make's Free plan, but credit consumption for the AI-driven module differs depending on whether you use Make's own credits or your own model key. |
FAQ
- Is Make's MCP Client the same as Make MCP Server?
- No — Make MCP Server exposes your Make scenarios as tools to other AI clients. MCP Client is the app inside a scenario that connects Make out to an external 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.