Question 1

What is a social media MCP server?

Accepted Answer

An MCP server is a standard way to expose tools to an AI agent. A social media MCP server gives the agent typed tools for posting — schedule, cancel, browse media, read the queue — so it can act on social platforms without you writing custom function definitions or platform OAuth code.

Question 2

What does the Schedule & Chill MCP server expose?

Accepted Answer

10 tools, 4 read-only resources, and 2 prompts. The tools cover scheduling, updating, cancelling, and inspecting posts, listing connected accounts and channel groups, browsing and uploading media, and reading publishing stats.

Question 3

Which platforms can an agent post to?

Accepted Answer

Eight: X (Twitter), LinkedIn profiles, LinkedIn Pages, Facebook, Instagram, YouTube, TikTok, and Pinterest. Threads, Bluesky, and Google Business Profile are on the roadmap.

Question 4

Which MCP clients does it work with?

Accepted Answer

Any client that supports remote MCP servers over HTTP with custom headers — Claude Desktop, Claude Code, and third-party clients. From your own code, use an MCP client library, or langchain-mcp-adapters if you are on LangChain.

Question 5

How is the MCP server authenticated?

Accepted Answer

With the same API keys as the REST API. Generate a key under Settings → API Keys and send it as Authorization: Bearer YOUR_API_KEY. Keys are scoped to your workspace and revocable at any time.

Question 6

Is the MCP server officially maintained or a community wrapper?

Accepted Answer

It is built and maintained by Schedule & Chill, in the same codebase as the REST API. New API capabilities land in both surfaces, so the tools do not drift out of date.

Question 7

Can the agent connect my social accounts?

Accepted Answer

No. Connecting an account needs an OAuth flow in a browser, which you complete once in the dashboard. After that, the agent can publish to any connected account.

Question 8

How do I stop an agent from publishing something wrong?

Accepted Answer

Have it schedule rather than publish. A future scheduled_at gives you a review window, and cancel_post removes anything you do not want. For programmatic control, add a human approval step before the publishing tool call.

Question 9

Does an MCP server cost extra?

Accepted Answer

No. MCP access is included on every plan, starting at $99/month. It uses the same post quota as the REST API rather than a separate meter.

Question 10

What is the difference between the MCP server and the REST API?

Accepted Answer

Same capabilities, different consumers. The REST API is for deterministic code — workflows, cron jobs, your backend. The MCP server describes those same operations with schemas a model can reason about, so an agent can decide what to call.

Tool	What it does
`schedule_post`	Create a post for one or many accounts, now or at a future time.
`update_post`	Edit a draft or scheduled post before it publishes.
`get_post`	Retrieve one post with per-account delivery status and errors.
`list_scheduled`	Read the upcoming queue so the agent knows what is already planned.
`cancel_post`	Cancel a scheduled post the agent or user decides against.
`get_accounts`	List connected accounts with ids, platforms, and handles.
`get_groups`	List channel groups so the agent can target a set of accounts at once.
`browse_media`	Search the media library for an image or video to attach.
`upload_media`	Ingest a file into the media library from a public URL.
`get_stats`	Read publishing stats across accounts and time ranges.

The social media MCP server

The short version

Connect in one config block

10 tools your agent gets

4 read-only resources

2 prompts

A typical agent flow

Frequently asked questions

Give your agent a mouth