Local MCP server

Announce the release from the terminal that shipped it

Claude Code can already read your repo. Give it SchedPilot and the thing that just wrote your changelog can post about it — to every network — without you opening a browser.

Start for free Full docs

Setup

Connect Claude Code in three steps

Create an API key

In SchedPilot, open API Access and generate a key. It starts with smm_.

Add the MCP server

Drop the configuration below into Claude Code, using your key.

Restart and ask

Restart Claude Code and ask it to list your connected accounts.

claude mcp add schedpilot -s user \
  -e SCHEDPILOT_TOKEN=smm_your_key \
  -- npx -y schedpilot-mcp

Replace smm_your_key with the key from API Access in your SchedPilot account.

Once connected

What Claude Code can do

get_accounts

List every connected social account, with its id and type.

create_post

Schedule a post to one or many accounts, with media, a thread and a video title.

list_posts

Read scheduled and published posts, filtered by date or status.

delete_post

Cancel a scheduled post before it goes out.

upload_media

Upload an image or video from a URL and get a media id back.

get_analytics

Read impressions, reach, likes, comments and shares for a published post.

Rate limits are 150 read and 100 write requests per hour, per user. Scheduling a post with media costs two writes.

Why Claude Code

It can read the repo it is posting about

This is what makes a terminal agent different from a chat one: it has your files. A release post written from the actual diff is more specific than anything you would get from a blank prompt, and it costs you one sentence.

Draft posts from a CHANGELOG, a diff or a commit range
Run it headless in CI so a tagged release announces itself
Same key works across every repo you open

Try asking it

Things that work well once Claude Code is connected.

“Read CHANGELOG.md and draft a thread about v2.4 for X and LinkedIn.”

“Summarise this week of commits into one post for our company page.”

“Schedule the release note for 9am tomorrow and show me the calendar.”

Keep a human in the loop for anything automated. Posts scheduled from CI still wait for approval in your calendar, which is the safety net that makes unattended runs reasonable.

FAQs

Claude Code questions

Can I use this in CI?

Yes. Claude Code runs headless, and because scheduled posts need approval, an automated run cannot publish something you have not seen.

Is this the same as the Claude connector?

No. Claude Code uses the local MCP server over stdio with an API key; Claude web and desktop use the remote connector with OAuth. Both reach the same account.

Can it publish without my approval?

No. Scheduling queues a post; it waits in your calendar until you approve it. That holds for every agent and every connection method.

Using something else?

There is a setup guide for every agent we support, plus a REST API for anything that is not on the list.

See all agents

Connect Claude Code to SchedPilot

Free to start, and every post waits for your approval.

Start for free