mcpField
S
Schedule & Chill

Schedule & Chill

Remote
schedulenchill.comSocial Media0Updated 8w ago
RepositoryVisit website

About Schedule & Chill

Schedule & Chill is a hosted MCP server for AI agents to schedule and publish content on LinkedIn, Bluesky, Mastodon, and YouTube. It offers 22 tools, 4 resources, and 2 prompts, with OAuth or static Bearer-token access.

Key features

  1. 01Schedule and update social posts
  2. 02Review queues, posts, and available slots
  3. 03Publish, retry, cancel, or restore posts
  4. 04Manage accounts, media, and analytics
  5. 05OAuth and Bearer-token authentication

Use cases

  1. 01Schedule posts across social channels
  2. 02Check pending queues and timing
  3. 03Review post performance and analytics

MCP support

This hosted MCP server provides Streamable HTTP endpoints for clients, with 22 tools, 4 resources, and 2 prompts. It supports OAuth 2.1 + PKCE or static Bearer-token authentication.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://schedulenchill.com/mcp-oauth
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Schedule & Chill MCP Server

A hosted Model Context Protocol server that lets an AI agent schedule and publish social media posts — LinkedIn, Bluesky, Mastodon and YouTube.

No install, no API key, no glue code. Paste one URL into your MCP client, approve a consent screen, and the agent gets 22 typed tools.

https://schedulenchill.com/mcp-oauth

Free. There is no paid plan and no credit card.

Connect it

Claude Code 
claude mcp add --transport http schedule-and-chill https://schedulenchill.com/mcp-oauth

Then run /mcp and approve the browser consent screen.

Claude Desktop / ChatGPT / Cursor / VS Code / Zed

Add a remote (HTTP) MCP server with the URL https://schedulenchill.com/mcp-oauth. Each app words it differently — "Add custom connector", "Add MCP server → HTTP", "Add remote server" — but they all want the same URL. A browser window opens once for consent.

Anything that only takes a config file 
{
  "mcpServers": {
    "schedule-and-chill": {
      "type": "http",
      "url": "https://schedulenchill.com/mcp-oauth"
    }
  }
}
API key instead of OAuth

There is a second endpoint for scripts and clients that would rather send a header:

https://schedulenchill.com/mcp     Authorization: Bearer YOUR_API_KEY

Same tools, same behaviour. Create a key in Settings → API keys.

You will need a free account at schedulenchill.com and at least one connected social channel.

Two transports, one server

EndpointAuthUse it when
/mcp-oauthOAuth 2.1 + PKCE, dynamic client registrationAlmost always. Nothing to copy or store, and each client is revocable on its own.
/mcpStatic bearer tokenScripts, CI, anything without a browser.

Both are streamable HTTP and expose an identical surface: 22 tools, 4 resources, 2 prompts.

What the agent can do

Full reference with parameters: docs/tools.md.

AreaTools
Write & scheduleschedule_post · update_post · duplicate_post
Read the queuelist_posts · get_post · get_queue_slots
Publish & recoverpublish_now · retry_post · cancel_post · delete_post · restore_post
Accounts & limitsget_accounts · get_groups · get_capabilities · get_tiktok_creator_info
Media librarybrowse_media · upload_media · update_media · list_asset_vocabulary
Measurementget_stats · get_analytics
Three things that will save you a bug report
  1. schedule_post requires when. There is no default. Pass "draft", "now", "next_slot", or an ISO-8601 timestamp. Publishing is irreversible, so it is never assumed — omitting when is an error, not a silent publish.
  2. Call get_capabilities before sending platform_options. Unknown option keys are silently dropped and the call still reports success. A guessed key does not error; it publishes with the platform default, which can mean a post you meant to restrict goes out public.
  3. Queue slots are computed, not reserved. get_queue_slots shows a human real times, but the same slot is returned to every caller until something occupies it. For a single post prefer when="next_slot" — the server resolves it at write time, so a batch never lands on the same minute.
Reversibility

cancel_post and delete_post soft-delete, and restore_post brings a post back. A post whose time has passed is restored as a draft rather than re-armed, so restoring never publishes anything by itself. publish_now and retry_post send immediately and cannot be undone — confirm with the human first.

Registry

Published to the Official MCP Registry as com.schedulenchill/mcp, under a DNS-verified namespace. The manifest is server.json in this repo.

What this repo is

Docs and the registry manifest for a hosted server. There is nothing to run locally — the server is operated by Schedule & Chill, in the same codebase as its REST API, so the two surfaces do not drift apart. The product source is not open.

Issues and pull requests on the docs are welcome.

Links

Built by Zakir Hossen · Lomeyo, LLC · MIT licensed docs.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.