Claude Connector
Add Schedulala to Claude as a custom connector and let Claude schedule posts, build threads, read analytics, and reply to comments on your behalf. The connector is a remote MCP server that exposes the same 29 tools as our local server, but you do not paste an API key. Claude walks you through a one-time approval and handles the credential for you. If you want the non-technical overview first, see the Claude integration page.
Endpoint: https://schedulala.com/api/mcp is a Streamable HTTP MCP server. Add it as a custom connector and Claude discovers OAuth automatically.
Add the connector
In Claude.ai or Claude Desktop, open Settings, then Connectors, then Add custom connector. Paste the server URL and save:
https://schedulala.com/api/mcp
Claude reads the server's OAuth discovery metadata, registers itself, and sends you to a Schedulala consent screen. Sign in if you are not already, review what the connector can do, and click Approve. That is the whole setup. From then on Claude can call the tools in any conversation.
No key to copy. Unlike the local server, you never paste a key into Claude. Approving the consent screen is what grants access. The key it mints lives in your developer dashboard, not in your Claude settings.
How authorization works
The connector uses OAuth 2.1 with PKCE. You do not need to understand any of it to use the connector, but here is what happens behind the consent screen:
- Claude fetches the discovery documents at
/.well-known/oauth-protected-resourceand/.well-known/oauth-authorization-server, then registers itself dynamically. - You are sent to the Schedulala consent screen and sign in. Approving redirects Claude back with a one-time authorization code, verified with PKCE S256.
- Schedulala mints an API key named
Claude Connectorand hands it to Claude as the access token. There is no refresh token; the key is long-lived and the token is advertised with a 90 day lifetime. - Every tool call Claude makes carries that key. It runs through the normal Schedulala API, so all of your plan quotas, rate limits, and permissions apply exactly as they would for a key you created yourself.
The connector key is visible and revocable. The Claude Connector key shows up in your developer dashboard like any other API key. Revoke it there at any time to cut Claude off. There is one active connector key per account, so reconnecting replaces the previous one.
What Claude can do
The connector exposes 29 tools, grouped below. These are the same tools you get from the local stdio server, so behavior, parameters, and responses match the rest of these docs.
| Group | Tools |
|---|---|
| Posts | Create, list, get, update, cancel, retry, bulk create, and validate posts across all twelve platforms. |
| Threads | Create a chain of sequential posts on twitter, threads, and bluesky. |
| Accounts | List the connected accounts an action can target, with their account ids and brand ids. |
| Usage | Read current plan usage and remaining quota. |
| Analytics | Per-post metrics, follower growth, and best posting times across all nine analytics platforms: instagram, twitter, bluesky, threads, facebook, linkedin, pinterest, tiktok, and youtube. |
| Engagement | List comments and mentions, reply, and hide comments. Platform support varies by action. |
| YouTube | Pull a video's caption transcript and per-video audience retention from a connected YouTube channel. |
| Feeds | Search public posts by keyword on bluesky and threads, look up public Bluesky profiles, and manage the saved keyword watch list. Results include reply targets that chain into the engagement tools. |
| Media | Re-host a public image or video URL on the Schedulala CDN, then attach it to posts. |
| Account setup | Get links to connect new social accounts and to subscribe or manage billing. Sign-in, credentials, and payment always happen on schedulala.com in your browser, never in the chat. |
The same tools are available locally via the stdio server @schedulala/mcp-server, which you run with a raw API key instead of OAuth. See CLI & SDKs for the local setup.
For API developers
OAuth exists so that Claude can connect without you handling a key by hand. For your own scripts and agents you do not need it. The /api/mcp endpoint also accepts any valid Schedulala API key directly as a bearer token. Point your own MCP client at the same URL and send the key:
# List the tools the remote server exposes, using a raw API keycurl -X POST https://schedulala.com/api/mcp \-H "Authorization: Bearer sk_live_abc123..." \-H "Content-Type: application/json" \-H "Accept: application/json, text/event-stream" \-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
A sk_test_* key runs in sandbox mode through the connector just as it does on the REST API, so you can wire up an agent end to end without real posting or quota burn.
Troubleshooting
| Symptom | What it means |
|---|---|
401 Unauthorized | The key is missing, revoked, or expired. If you revoked the connector key, or it aged out, remove the connector in Claude settings and add it again to mint a fresh one. |
| A tool reports an unsupported platform | Engagement and analytics support a subset of platforms, and it differs by action. Check which platforms each action covers on the Engagement and Analytics pages. |
| A platform action is denied | The connected account may need to be reconnected with the right permissions. See Connecting Accounts. |