MCP Quickstart

SchedPilot ships a Model Context Protocol (MCP) server — schedpilot-mcp — so AI agents can schedule and manage social media posts natively, without copy-pasting content or leaving the chat interface.

Supported clients: Claude Desktop, Claude Code, Hermes, Cursor, Windsurf, and any other MCP-compatible agent.

What Agents Can Do​

Once connected, an AI agent can:

• List all connected social media accounts
• Schedule posts with text and attached media
• List and filter existing scheduled and published posts
• Delete posts
• Upload images or videos from public URLs
• Retrieve post analytics

Prerequisites​

Step 1 — Get Your Token​

Log in to app.schedpilot.com/api-access and create a Personal API Key (smm_...).

If you are building an app that other users will authorise, follow the OAuth 2.0 guide to obtain a sp_tok_... bearer token instead.

Step 2 — Configure Your Client​

Pick your client below. The server package and token are the same for all of them — only the config file location differs.

Claude Desktop​

Open (or create) the config file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "schedpilot": {
      "command": "npx",
      "args": ["-y", "schedpilot-mcp"],
      "env": {
        "SCHEDPILOT_TOKEN": "smm_your_key_here"
      }
    }
  }
}

Fully quit and relaunch Claude Desktop after saving. Look for the 🔧 wrench icon in the chat input bar — click it to confirm the SchedPilot tools appear.

Claude Code​

Claude Code (the CLI) stores MCP servers in ~/.claude.json (global, applies to all projects) or .claude.json in the root of a specific project.

Option A — CLI (recommended)

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

• -s user makes it global (available in every project). Use -s local to scope it to the current project only.
• The server is available immediately — no restart needed.

Option B — edit ~/.claude.json directly

{
  "mcpServers": {
    "schedpilot": {
      "command": "npx",
      "args": ["-y", "schedpilot-mcp"],
      "env": {
        "SCHEDPILOT_TOKEN": "smm_your_key_here"
      }
    }
  }
}

Verify it is loaded:

claude mcp list

You should see schedpilot in the output. Then test it in a session:

> Show me my SchedPilot accounts

Hermes​

Hermes reads MCP server configuration from its mcp_config.json file. Open or create it at the path shown in your Hermes settings panel, then add:

{
  "mcpServers": {
    "schedpilot": {
      "command": "npx",
      "args": ["-y", "schedpilot-mcp"],
      "env": {
        "SCHEDPILOT_TOKEN": "smm_your_key_here"
      }
    }
  }
}

Save the file and restart or reload the Hermes agent context. SchedPilot tools will appear in the available tool list.

Cursor​

Add the following to Cursor's MCP configuration (accessible via Settings → MCP or by editing ~/.cursor/mcp.json):

{
  "mcpServers": {
    "schedpilot": {
      "command": "npx",
      "args": ["-y", "schedpilot-mcp"],
      "env": {
        "SCHEDPILOT_TOKEN": "smm_your_key_here"
      }
    }
  }
}

Windsurf​

Add to Windsurf's MCP configuration (accessible via Settings → Cascade → MCP Servers or by editing ~/.codeium/windsurf/mcp_config.json):

{
  "mcpServers": {
    "schedpilot": {
      "command": "npx",
      "args": ["-y", "schedpilot-mcp"],
      "env": {
        "SCHEDPILOT_TOKEN": "smm_your_key_here"
      }
    }
  }
}

Step 3 — Test with Example Prompts​

Once connected, try these to confirm everything is working:

Show me my SchedPilot accounts

Schedule a tweet saying 'Hello world!' for tomorrow at 10am UTC

Show me my last 5 scheduled posts

Upload the image at https://example.com/banner.jpg and schedule a LinkedIn post using it for next Monday at 9am Eastern time

Using an OAuth Token​

If you obtained a sp_tok_... token via the OAuth flow (for example, to act on behalf of another user), replace the token value in any of the configs above:

"env": {
  "SCHEDPILOT_TOKEN": "sp_tok_xxxxxxxxxxxxxxxxxxxxxxxx"
}

Both personal API keys (smm_...) and OAuth tokens (sp_tok_...) are accepted by SCHEDPILOT_TOKEN.

Next Steps​

• MCP Tools Reference — full parameter docs for all 6 tools
• OAuth 2.0 — connect SchedPilot to an app that other users authorise
• Rate Limits — 60 read / 30 write requests per hour