Schedule & Chill
Start free
5 integrations

Post to social media from anything that speaks HTTP

One REST API and one MCP server, so your workflow tool or AI agent publishes to LinkedIn, Bluesky, Mastodon, YouTube and TikTok without an OAuth app per network.

Start freeRead the docs

Free · No credit card · No trial timer

Guides

Pick your tool

Each guide is a working setup — the exact steps, the request body to copy, and what the integration cannot do.

Claude

AI assistant

Connect Claude Desktop or Claude Code to Schedule & Chill over MCP so Claude can draft, schedule, and publish social posts as first-class tools.

Native MCP server

Read the guide

n8n

Workflow automation

Automate social posting in n8n with the HTTP Request node — no community node to install, no self-hosted social integrations to maintain.

REST API via HTTP Request node

Read the guide

Make.com

Workflow automation

Publish to every social platform from a Make scenario using the HTTP module — one module instead of a separate connection per network.

REST API via HTTP module

Read the guide

LangChain

AI agent framework

Give a LangChain or LangGraph agent the ability to publish social posts — wrap the REST API in a @tool, or load the MCP server with langchain-mcp-adapters.

REST API tool or MCP adapter

Read the guide

Zapier

Workflow automation

Post to every connected social platform from a Zap using Webhooks by Zapier — one action step instead of one per network.

REST API via Webhooks by Zapier

Read the guide
Two ways in

REST API or MCP server

Both are on the free plan and share the same quota. The REST API uses an API key; the MCP server takes either that key or an OAuth connector URL with no key at all. Which one you want depends on whether a human or a model decides what to publish.

REST API

One POST to /api/posts fans out to every connected account. Best for deterministic automation — n8n, Make, Zapier, cron jobs, and your own backend.

API reference

MCP server

A native Model Context Protocol server with 22 tools, 4 resources and 2 prompts. Best when a model decides what to post: Claude, LangGraph agents, or any MCP-capable client.

MCP server details
FAQ

Integration questions

Anything that can make an HTTPS request or speak the Model Context Protocol. That covers automation platforms like n8n, Make.com, and Zapier, AI agent frameworks like LangChain, LangGraph, CrewAI, and AutoGen, and MCP clients like Claude Desktop and Claude Code.

Use the REST API from deterministic automation — workflows, cron jobs, and your own backend. Use the MCP server when an AI agent is deciding what to post, because MCP exposes all 22 tools with schemas the model can reason about directly.

One API key covers everything. Generate it under Settings → API Keys and send it as Authorization: Bearer YOUR_API_KEY. The same key authenticates both the REST API and the MCP server, and can be revoked at any time. AI tools can skip the key entirely and connect to https://schedulenchill.com/mcp-oauth over OAuth instead.

22 tools, 4 resources and 2 prompts — covering scheduling, publishing, media upload, queue slots, analytics and account discovery. Connect at https://schedulenchill.com/mcp with an API key, or over OAuth at /mcp-oauth.

No. That is the point of the API. One request to POST /api/posts fans out to every connected account across LinkedIn, Bluesky, Mastodon, YouTube and TikTok. You maintain one integration instead of an OAuth app per platform.

Not yet. Each platform connects through its generic HTTP step — the HTTP Request node in n8n, the HTTP module in Make, and Webhooks by Zapier. These need no installation and work on self-hosted instances too.

No. Connecting an account requires an OAuth flow in a browser, which you complete once in the Schedule & Chill dashboard. After that, any integration can publish to it.

Get an API key and start posting

It is free — no card, no trial timer. Make real API calls, connect your account, and see it work.

Start free

Free · No credit card · No trial timer