Schedule from ChatGPT, Notion, Claude, and n8n: introducing the Schedulin MCP server


Last month we launched the Schedulin developer platform — a public REST API, SDKs, and a CLI. That was for code. This one is for conversation.
Schedulin now runs an open Model Context Protocol (MCP) server. MCP is the standard that lets AI tools call external services directly, so instead of copy-pasting between your AI assistant and your scheduling dashboard, the assistant talks to Schedulin itself:
- "Draft a post for my X channel that says 'We just shipped our redesigned dashboard!'"
- "Show me everything scheduled for this week, and move Thursday's post to Friday morning."
- "List my connected channels and tag the drafts about the launch with 'product'."
The AI picks the right tool, makes the call, and your queue updates. You review the result in Schedulin — or don't, if you trust your agent.
One endpoint, any MCP client
The server speaks streamable HTTP at:
https://mcp.schedulin.app/mcp
There are two ways in, depending on the client:
- OAuth — hosted agents like ChatGPT, Notion, and Perplexity connect with a sign-in: you approve exactly what the agent can touch on a consent screen, and you can revoke access any time under Settings → API & Apps → Connected Apps. No keys to copy.
- API key — developer tools and automation platforms authenticate with a key from Settings → API keys, sent as an
x-api-keyheader or a standard bearer token.
Either way, access is scoped to one workspace, and the client gets tools for the things you actually do every day: list and search posts (drafts, scheduled, published, failed), create posts with media and tags, schedule or queue them, update and reschedule, delete, list your connected channels, and manage tags.
ChatGPT
- In ChatGPT, open Settings → Apps & Connectors and enable Developer mode under Advanced settings.
- Add a new app with the name
Schedulin, the MCP server URLhttps://mcp.schedulin.app/mcp, and OAuth as the authentication method. - Click Create, sign in to Schedulin when prompted, and approve access.
Notion
- In Notion, go to Settings → Connections → Manage and enable Custom MCP servers.
- Open the custom agent you want to connect and click Settings → Add connection → Add custom MCP.
- Enter the server URL
https://mcp.schedulin.app/mcp, name itSchedulin, pick OAuth, then click Connect and approve access.
Perplexity
- In Perplexity, go to Settings → Connectors and add a Custom connector named
Schedulinwith the server URLhttps://mcp.schedulin.app/mcp. - Find Schedulin in the Custom connectors list, click Add connector, sign in, and approve access.
Claude Code
One command:
claude mcp add schedulin --transport http https://mcp.schedulin.app/mcp \
--header "x-api-key: YOUR_API_KEY"
Claude Desktop
In Settings → Developer → MCP servers, add:
{
"schedulin": {
"url": "https://mcp.schedulin.app/mcp",
"headers": { "x-api-key": "YOUR_API_KEY" }
}
}
Cursor
In .cursor/mcp.json:
{
"mcpServers": {
"schedulin": {
"url": "https://mcp.schedulin.app/mcp",
"headers": { "x-api-key": "YOUR_API_KEY" }
}
}
}
n8n
n8n turns the MCP server into a building block for automations — new RSS item → draft post, weekly summary of next week's queue → Slack, form submission → scheduled announcement.
- Add an MCP Client node to your workflow.
- Set Server Transport to
HTTP Streamableand the endpoint URL tohttps://mcp.schedulin.app/mcp. - Set Authentication to
Bearer Authand create a credential with your Schedulin API key. - Pick the Schedulin tools you want the workflow to use.
Everything else
Any MCP client that supports streamable HTTP works: OAuth-capable clients discover the sign-in flow automatically, and clients with custom-header support can pass an API key instead. That covers Zed, Windsurf, VS Code, Raycast, and most agent frameworks.
Try it
Connect a client and start with one of these:
- "List all my connected Schedulin channels."
- "Show me my scheduled posts for this week."
- "Create a draft that says 'Happy Monday! What are you working on this week?' for every one of my channels."
If you build something fun with it — an agent that runs your whole queue, an n8n pipeline that never sleeps — we'd genuinely love to see it.