Schedule & Chill

com.schedulenchill由 schedulenchill.com 發布官方發布者v1.0.1更新於 Nov 2, 2026

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

已驗證Streamable HTTP可網頁執行溝通與協作商業與電商

概覽

AI 產生的概覽

託管式 MCP 伺服器，讓 AI 助理在 LinkedIn、Bluesky、Mastodon 和 YouTube 上排程、發佈並統計社群貼文。

可以做什麼
  • 建立、修改、複製並排程貼文，可選擇草稿、立即、下一個空檔或指定時間
  • 檢視佇列：列出與查看貼文，查詢即將到來的發佈時段
  • 立即發佈、重試、取消、刪除與還原貼文
  • 查看已連結帳號、群組、平台能力以及 TikTok 創作者資訊
  • 瀏覽、上傳與更新媒體庫內容，列出素材詞彙表
  • 取得貼文統計與分析資料
適用情境
適合讓助理在多個管道起草並排隊發佈社群貼文，或在聊天用戶端內查看已排程內容與已發佈貼文的表現。
執行需求
需要遠端 streamable HTTP 端點，無需在本機執行。需要免費的 Schedule & Chill 帳號和至少一個已連結的社群管道。驗證方式為含瀏覽器同意頁的 OAuth 2.1，或在帳號設定中建立的靜態 Bearer API 金鑰（供腳本與無瀏覽器用戶端使用）。
安裝前請注意
publish_now 和 retry_post 會立即送出且無法復原，應先與人工確認。未知的平台選項鍵會被默默捨棄，貼文可能依公開預設設定送出。佇列時段不會被保留，可能被重複使用。API 金鑰端點使用長期有效的 Bearer 權杖，需妥善保管。貼文與媒體會傳送給第三方服務。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Schedule & Chill，將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存，絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/com.schedulenchill%2Fmcp/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

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

來源：README.md，提交 e13f5a5

工具

0
該伺服器需要登入，因此 SourceWeft 無法在沒有帳號的情況下讀取其工具，也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

1
  1. v1.0.1最新Sep 16, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分