logo
Schedulin

MCP server

Schedulin runs a Model Context Protocol (MCP) server at mcp.schedulin.app. Any MCP-compatible AI client (Claude Desktop, Cursor, Zed) can talk to it and act on your workspace — list channels, draft posts, manage your queue.

What MCP gives you

Instead of switching between Schedulin and your AI tool, the AI talks to Schedulin directly. Examples:

  • "Draft a LinkedIn post about today's product launch and add it to the queue." The AI creates a draft and you review in Schedulin.
  • "What's scheduled for this week, and which drafts are still waiting?" The AI pulls your queue and summarizes.
  • "Schedule these five clips across this week's queue." The AI uses your posting schedule and adds the posts.

Setup (hosted agents: ChatGPT, Notion, Perplexity)

Hosted agents connect over OAuth — no API key needed. Add a custom MCP server / connector in the agent's settings with the URL https://mcp.schedulin.app/mcp and OAuth as the auth method, then sign in to Schedulin and approve access on the consent screen. You choose which organization the agent can act on, and you can revoke access any time under Settings → API & Apps → Connected Apps.

Setup (Claude Desktop)

  1. Get a Schedulin API key (Settings → API keys).
  2. In Claude Desktop, open Settings → Developer → MCP servers.
  3. Add a new server: 
    {
  "schedulin": {
    "url": "https://mcp.schedulin.app/mcp",
    "headers": { "Authorization": "Bearer YOUR_API_KEY" }
  }
}
  4. Restart Claude Desktop. The Schedulin tools appear in the tools panel.

Setup (Cursor)

In .cursor/mcp.json:

{
  "mcpServers": {
    "schedulin": {
      "url": "https://mcp.schedulin.app/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Available tools

The MCP server exposes the core surfaces of the REST API: posts (list, get, create, update, delete — as drafts, queued, or scheduled), connected channels, and tags. The AI client sees a tool list and picks the right one for your request.

Authentication accepts the API key either as a bearer token (Authorization: Bearer YOUR_API_KEY) or as an x-api-key header — use whichever your client supports.

Security

  • The API key scope = workspace scope. The AI can only see and act on the workspace the key belongs to. OAuth connections are additionally limited to the permissions you approved on the consent screen.
  • Rotate the key any time under Settings → API keys; revoke OAuth grants under Settings → API & Apps → Connected Apps.
  • For agencies, create one key per client workspace and load the right one in your AI tool when switching contexts.

See also