Local MCP server

Build it and post about it in the same window

Cursor already has your project open. Add SchedPilot as an MCP server and the feature you just finished can be announced before you have context-switched away from it.

Start for free Full docs

Setup

Connect Cursor 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 Cursor, using your key.

Restart and ask

Restart Cursor 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.

Once connected

What Cursor 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 Cursor

Posting while the work is still fresh

The best time to write about a feature is the moment it works, when you still remember why it was hard. The reason that rarely happens is the context switch. Removing it is most of the battle.

Ask in the chat pane you are already using
Reference files and code in the prompt
One config block, available in every project

Try asking it

Things that work well once Cursor is connected.

“Draft a short post about the feature in this file and schedule it for tomorrow morning.”

“What do I have queued this week?”

“Post this benchmark result to X and LinkedIn at 2pm.”

Cursor reads MCP servers from its settings file. After adding the block, restart Cursor so the tools register.

FAQs

Cursor questions

Where does the config go?

Into Cursor's MCP settings. Paste the block, add your key, restart, then ask it to list your connected accounts to confirm.

Does it work in every project?

Yes, if you add it at user level rather than per project.

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 Cursor to SchedPilot

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

Start for free