Remote MCP Server
Alongside the local schedpilot-mcp npm package, SchedPilot runs a remote MCP server at:
https://api.schedpilot.com/mcp
Nothing to install. You paste that URL into your AI client, sign in with your SchedPilot account, and the client gets its own access token through OAuth 2.1.
Use the remote server when your client supports custom connectors (Claude web, desktop and mobile). Use the local npm package when you want a stdio server on your own machine — Claude Code, Cursor and Windsurf all work that way.
Add SchedPilot to Claude
- Open Settings → Connectors in Claude.
- Click Add custom connector.
- Paste
https://api.schedpilot.com/mcpas the URL. - Click Connect. A SchedPilot consent page opens.
- Sign in if you aren't already, review the permissions, and click Allow Access.
Claude registers itself automatically — there is no client ID or secret to create, and no API key to paste. The connector appears with the same tools listed in the MCP Tools reference.
Requirements
| Requirement | Notes |
|---|---|
| A SchedPilot account | The consent screen signs you in at app.schedpilot.com |
| An active subscription | Publishing tools require a paid or trialing plan |
| A client supporting remote MCP | Claude web / desktop / mobile |
Permissions
The consent screen shows what the connector is asking for. Two scopes exist:
| Scope | Grants |
|---|---|
schedpilot:read | List connected accounts, list posts and media, read analytics |
schedpilot:write | Schedule posts, delete posts, upload media |
A client that requests no specific scope receives both.
Revoking access
Go to app.schedpilot.com/api-access and revoke the token listed for the connector. The connector stops working immediately — you do not need to remove it in Claude first, though it will show an error until you do.
Removing the connector in Claude does not revoke the token on our side. Revoke it here if you want the access gone.
OAuth endpoints
The server implements the discovery documents an MCP client needs, so these are informational — clients find them on their own.
| Purpose | URL |
|---|---|
| Protected resource metadata | https://api.schedpilot.com/.well-known/oauth-protected-resource |
| Authorization server metadata | https://api.schedpilot.com/.well-known/oauth-authorization-server |
| Dynamic client registration | https://api.schedpilot.com/oauth/register |
| Authorization | https://api.schedpilot.com/oauth/authorize |
| Token | https://api.schedpilot.com/oauth/token |
| Revocation | https://api.schedpilot.com/oauth/revoke |
PKCE (S256) is required for dynamically registered clients. Access tokens do not expire; they stay valid until revoked.
Building your own integration against these endpoints? See the OAuth 2.0 guide.
Rate limits
Remote MCP calls count against the same per-user limits as the REST API — currently 60 read requests/hour and 30 write requests/hour. An agent working through a long back-and-forth can reach these quickly; see Rate limits.
Troubleshooting
"An active SchedPilot subscription is required" — the read tools work on any plan, but scheduling and uploading need an active subscription. Check app.schedpilot.com/billing.
The connector keeps asking me to sign in — the consent page needs a logged-in session at app.schedpilot.com. Sign in there first, then retry the connection.
Tools stopped working after a while — the token was probably revoked. Remove the connector in Claude and add it again.