MCP Server

Schedule & Chill ships a native Model Context Protocol server, so AI agents — Claude, ChatGPT, or your own — can schedule posts, manage media, and read your queue as first-class tools. No glue code: the agent calls tools directly.

Endpoint

https://schedulenchill.com/mcp

Authentication

The MCP server uses the same API keys as the REST API. Send your key as a bearer token:

Authorization: Bearer YOUR_API_KEY

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

What it exposes

Kind	Items
Tools	schedule_post, get_accounts, list_scheduled, cancel_post, get_stats, browse_media, upload_media
Resources	Connected Accounts, Upcoming Schedule, Media Library
Prompts	content_idea, draft_post

Connecting

Claude Desktop / Claude Code

Add a remote MCP server pointing at the endpoint with an Authorization header. In an MCP client config that supports remote HTTP servers:

{
    "mcpServers": {
        "schedulenchill": {
            "url": "https://schedulenchill.com/mcp",
            "headers": { "Authorization": "Bearer YOUR_API_KEY" }
        }
    }
}

ChatGPT / custom agents

Any MCP-capable client works. Point it at https://schedulenchill.com/mcp and pass the bearer token. From your own code, use an MCP client library and the same URL + header.

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.