MCP Server

Schedule & Chill ships a native Model Context Protocol server, so AI tools — Claude Code, Claude Desktop, Cursor, Gemini CLI, or your own agent — can schedule posts, upload video from your machine, and read your queue as first-class tools. No glue code: the agent calls tools directly.

Two ways to connect

There are two endpoints. They expose exactly the same tools, resources and prompts — only the way you sign in differs.

	Endpoint	Sign in with	Use it when
Connect with a link (recommended)	https://schedulenchill.com/mcp-oauth	OAuth 2.1 — you approve a consent screen in your browser	Your tool has an "Add connector" or "Add MCP server" button: Claude, ChatGPT, Cursor, VS Code, Zapier
Connect with an API key	https://schedulenchill.com/mcp	A bearer token you paste into a config file	Your tool wants a static header, or you are scripting it

Connect with a link (recommended)

Paste this URL into your AI tool and approve the screen it shows you:

https://schedulenchill.com/mcp-oauth

There is no key to create, copy, or store. Your tool discovers everything it needs from the URL, sends you to a Schedule & Chill consent screen that names the tool and lists what it is asking for, and gets its own token once you approve. Each tool is approved separately and can be revoked on its own. Your password is never shared.

Connect with an API key

https://schedulenchill.com/mcp

Send the key as a bearer token on every request:

Authorization: Bearer YOUR_API_KEY

Create a key under Settings → API Keys (see Authentication).

What it exposes

Kind	Items
Tools	22 in total — schedule_post, update_post, get_post, list_posts, cancel_post, publish_now, retry_post, duplicate_post, delete_post, restore_post, get_accounts, get_groups, get_capabilities, get_queue_slots, browse_media, upload_media, update_media, get_stats, get_analytics and more
Resources	Connected Accounts, Upcoming Schedule, Media Library, Get Started
Prompts	content_idea, draft_post

Connecting

Connect Your AI Tool has copy-paste setup for Claude Code, Claude Desktop, Cursor, VS Code, Gemini CLI, Codex, Windsurf, Zed, Kimi CLI, OpenClaw, Hermes, and any other MCP client.

The short version — Claude Code, one command, no key:

claude mcp add --transport http schedulenchill https://schedulenchill.com/mcp-oauth

Then run /mcp and approve it in the browser window that opens.

In Claude, ChatGPT or Zapier, add a custom connector and paste https://schedulenchill.com/mcp-oauth — there is nothing else to fill in.

Clients that speak stdio only (Claude Desktop, Codex, Zed) still need the mcp-remote bridge rather than a plain URL — the setup guide covers each one.

A typical agent flow

1. Call get_accounts to discover where it can post.
2. Optionally browse_media (or upload_media from a URL) to attach visuals.
3. Call schedule_post with content, platforms, and an optional time.
4. Confirm with list_scheduled, or cancel_post to undo.

See Tools for full parameters.