MCP server for social media

Pick your client

Each client connects to a remote MCP server a little differently — here's the real, current way for each.

ChatGPT social media scheduling with SkedCast (MCP)ChatGPT social media scheduling works through a custom MCP connector: enable Developer Mode, add SkedCast's server URL, and sign in. Once connected, ask ChatGPT to schedule or check posts, and it confirms every write action with you first.Connect it
ClaudeConnect SkedCast to Claude as a custom connector, on claude.ai or Claude Desktop, using the same steps either way. Once connected, Claude can schedule and check posts through SkedCast's remote MCP server, asking you to confirm every write.Connect it
Cursor MCP social media with SkedCast (MCP)Cursor MCP social media scheduling means adding SkedCast to Cursor's `mcp.json`, with either Cursor's native OAuth "Connect" flow or a static bearer token in a `headers` field. Once connected, Cursor's agent can call SkedCast's scheduling tools directly from the editor.Connect it
N8n social media scheduling with SkedCast (MCP)n8n social media scheduling connects through the built-in MCP Client Tool node — no community package needed. Point it at SkedCast's MCP endpoint, attach it to an AI Agent node, and the workflow can schedule or check posts across every connected account.Connect it
Zapier social media scheduling with SkedCast (MCP)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.Connect it
Make social media scheduling with SkedCast (MCP)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.Connect it

What SkedCast's MCP server exposes

59 tools

31 read tools (posts, accounts, analytics, best times, approvals, reports) and 28 write tools (create, revise, reschedule, approve, publish) — the full, current list is generated from the same catalog the server exposes.

Scoped to you

A connection acts as the person who authorized it — your role, your plan limits, your client access. An agent can never reach further than you can.

Standard MCP

Streamable HTTP, OAuth 2.1 with PKCE and Dynamic Client Registration, RFC 9728 protected-resource metadata — any spec-compliant MCP client can connect, not only the six above.

See every tool, its scope, and its schema

Using the REST API instead?

The MCP server and the REST API are two doors onto the same versioned surface — every MCP tool wraps a real /v1 endpoint. Pick MCP for an AI client, REST for everything else.