Schedule & Chill

com.schedulenchillPublished by schedulenchill.comOfficial publisherv1.0.1Updated Nov 2, 2026

A free social media scheduler your AI tools can post through — LinkedIn, Bluesky, Mastodon, YouTube.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Hosted MCP server that lets an AI assistant schedule, publish and measure social media posts on LinkedIn, Bluesky, Mastodon and YouTube.

What you can do
  • Create, update, duplicate and schedule posts, choosing draft, now, next slot or a timestamp
  • Read the queue: list and inspect posts and see upcoming queue slots
  • Publish immediately, retry, cancel, delete and restore posts
  • Inspect connected accounts, groups, platform capabilities and TikTok creator info
  • Browse, upload and update media library items and list asset vocabulary
  • Fetch post statistics and analytics
When to use it
Useful when you want an assistant to draft and queue social posts across several channels, or to check what is scheduled and how published posts performed, without leaving the chat client.
Requirements
A remote streamable HTTP endpoint; nothing runs locally. A free Schedule & Chill account and at least one connected social channel. Authentication is OAuth 2.1 with a browser consent screen, or a static bearer API key created in the account settings for scripts and clients without a browser.
Before you install
publish_now and retry_post send posts immediately and cannot be undone, so confirm with a human first. Unknown platform option keys are silently dropped and the post may go out with public defaults. Queue slots are not reserved and can be reused. The API key endpoint uses a long-lived bearer token that should be kept secret. Posts and media are sent to a third-party service.

Installation

In SourceWeft

  1. Open Schedule & Chill in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.schedulenchill%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "schedule-chill": {
      "type": "http",
      "url": "https://schedulenchill.com/mcp-oauth"
    }
  }
}

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
bash
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
json
{  "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.

Source: README.md at commit e13f5a5

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts