Claude connects to SchedPilot over a remote MCP server, so you can plan a week of content in the same chat where you thought of it. Nothing to install, and no API key to paste.
Last reviewed October 2026. A human still approves every post before it publishes.
In Claude, go to Settings and choose to add a custom connector.
Use the URL below. There is no client id or secret to create.
A SchedPilot consent page opens. Approve it and the tools appear straight away.
https://api.schedpilot.com/mcp
Paste this as the connector URL. OAuth handles the rest — no key to copy.
Claude is at its best when it has your material in front of it. Paste a changelog, a brief or a tone guide into the conversation and it drafts from that, then schedules the result without you leaving the chat. The approval still waits for you in SchedPilot.
Also try
Rate limits are 150 read and 100 write requests per hour, per user. Scheduling a post with media costs two writes.
Because the connector is remote rather than something running on your laptop, it follows your account. Draft on the desktop app at your desk, approve from your phone on the train — it is one connection, not three.
Things that work well once Claude is connected.
Claude asks for permission the first time it uses a tool. Scheduling still only queues a post — it waits in your calendar for your approval before it publishes.
Less "write me a post", more "here is the raw material, handle it". Copy any of these as a starting point.
“Using the tone guide in this project, write four posts about our Bluesky launch and schedule them across LinkedIn and Threads next week.”
“Read the changelog I just pasted, pull out the five changes customers will care about, and queue one post per weekday at 10am.”
“Pull the analytics for everything I published in the last 30 days, tell me which three performed best and why, then draft follow-ups to those three.”
“What is scheduled for the rest of this week? Cancel anything going out on Saturday and shift Sunday to Monday at 8am.”
The connector lives on your SchedPilot account, not on a machine. Add it in Claude on the web and it is already there on the desktop app and your phone.
Claude requests permission the first time it reaches for a SchedPilot tool, so you see what it is about to do before it does it rather than afterwards.
Paste a changelog, a brief or a tone guide into the conversation and Claude drafts from that, instead of inventing a voice for your brand.
The remote connector uses OAuth. Nothing is stored in a config file, and you can revoke the connection from your SchedPilot account at any point.
Once a post is approved and queued, SchedPilot publishes it at the set time. Closing the conversation changes nothing.
Claude can fill your calendar but it cannot publish past you. Every queued post waits for a one-click approval before anyone sees it.
Two different Anthropic products, and SchedPilot works with both — but they connect in different ways, so start on the right page. This one is for Claude, the assistant you chat with.
| Claude (this page) | Claude Code | |
|---|---|---|
| What it is | The assistant at claude.ai, on desktop and on mobile | Anthropic’s coding agent, running in your terminal |
| How it connects | Remote MCP connector — paste a URL and sign in | Local MCP server, added with one claude mcp add command |
| Credentials | OAuth, no key to store | An API key beginning smm_, passed to the server |
| Where it runs | Anthropic’s side, so it follows you between devices | On your own machine, alongside the repository you are in |
| Best for | Planning and approving content by conversation | Announcing a release from the terminal that shipped it |
Working in an editor instead? Cursor, Windsurf, VS Code and Zed all use the same local MCP server as Claude Code — each has its own guide.
Claude reaches SchedPilot through MCP, the Model Context Protocol — the standard way an assistant talks to an outside application. For terminal and editor agents that usually means running a small server on your own machine. Claude does not need to.
SchedPilot hosts the MCP server itself, so the connector is just a URL plus an OAuth sign-in. Claude discovers the six available tools on connection: list accounts, create a post, list posts, delete a post, upload media and read analytics. You never name an endpoint.
The practical consequence is that the connection belongs to your account rather than to a laptop. Add it once and it is present in Claude on the web, on the desktop app and on your phone, with nothing to keep in sync.
Read the full setup docsWhatever you have linked in SchedPilot. Claude reads the list on connection, so you can name an account directly or tell it to post everywhere at once.
There is a setup guide for every agent we support, plus a REST API for anything that is not on the list.
See all agentsSchedule posts, find your best time to publish, and keep your calendar full — without the chaos. SchedPilot makes consistency simple across every channel.
Start for freeFree trial available. Cancel anytime.
SchedPilot