VS Code supports MCP servers, so SchedPilot becomes a tool Copilot Chat can call. If VS Code is where you spend the day, it is also where your posts can come from.
In SchedPilot, open API Access and generate a key. It starts with smm_.
Drop the configuration below into VS Code / Copilot, using your key.
Restart VS Code / Copilot and ask it to list your connected accounts.
{
"mcpServers": {
"schedpilot": {
"command": "npx",
"args": ["-y", "schedpilot-mcp"],
"env": { "SCHEDPILOT_TOKEN": "smm_your_key" }
}
}
}
Replace smm_your_key with the key from API Access in your SchedPilot account.
Rate limits are 150 read and 100 write requests per hour, per user. Scheduling a post with media costs two writes.
The appeal is not that it is clever — it is that there is nothing new to open. The editor you already have becomes the place where content gets queued.
Things that work well once VS Code / Copilot is connected.
MCP support lives in VS Code itself, so keep it reasonably current. After adding the server, reload the window.
There is a setup guide for every agent we support, plus a REST API for anything that is not on the list.
See all agentsFree to start, and every post waits for your approval.
Start for freeSchedule 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.