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 分