Run Scheduloid from your AI.

What the Scheduloid MCP server is

MCP (Model Context Protocol) is the standard way an AI assistant uses outside tools. Scheduloid runs an MCP server, so your assistant can work in your Scheduloid workspace for you. It sees what you see and does what you could do in the app, with the same plan limits and credits.

Sign in, or use an API key

You need a Scheduloid account with at least one social account connected. There are two ways to let your assistant in:

• Sign in (easiest). Claude, ChatGPT and Claude Code open a Scheduloid sign-in page and you approve access. No key to copy, and you can remove access any time.
• API key. Codex, VS Code and the Claude Desktop config file use a key. Make one in Settings → API keys & Claude. Keys start with sk_live_ and are shown once, so store yours somewhere safe. Never paste it into a public place.

Only a workspace owner's access can publish, schedule or spend credits. A teammate's key can read.

Set up your assistant

Pick the app you use. Each one takes about a minute.

https://app.scheduloid.com/mcp

https://app.scheduloid.com/mcp

claude mcp add --transport http scheduloid https://app.scheduloid.com/mcp

claude mcp add --transport http scheduloid https://app.scheduloid.com/mcp \
  --header "Authorization: Bearer sk_live_YOUR_KEY"

[mcp_servers.scheduloid]
url = "https://app.scheduloid.com/mcp"
bearer_token_env_var = "SCHEDULOID_API_KEY"

export SCHEDULOID_API_KEY=sk_live_YOUR_KEY

{
  "servers": {
    "scheduloid": {
      "type": "http",
      "url": "https://app.scheduloid.com/mcp",
      "headers": { "Authorization": "Bearer sk_live_YOUR_KEY" }
    }
  }
}

{
  "mcpServers": {
    "scheduloid": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.scheduloid.com/mcp",
               "--header", "Authorization:${SCHEDULOID_AUTH}"],
      "env": { "SCHEDULOID_AUTH": "Bearer sk_live_YOUR_KEY" }
    }
  }
}

Check it works

Ask: "What's in my Scheduloid workspace?" You should see your plan, credits and connected accounts. If you don't, see Troubleshooting.

Talk to it like a teammate

You don't need to know tool names. Ask in your own words and the assistant picks the right tool.

• Which of my posts failed this week, and what do I need to fix?
• Schedule this caption on LinkedIn and X for Thursday at 10am.
• Move tomorrow's Instagram post to Friday morning.
• How did my last five LinkedIn posts do?
• Make a square image for a spring sale, in our brand colours.
• Turn this blog post into posts for every network I've connected.
• How many AI credits do I have left?

Plan a week on your own topics

Give your website and the topics you want to talk about. Scheduloid reads your site, plans a week of posts on those topics only, and waits for your approval at every paid step.

1. Start. Share your website and, if you like, your topics, facts you want used and anything never to say.
2. Answer. Scheduloid may ask a few short questions about your audience and offer.
3. Review the plan. You get one post per day with a hook and angle. Ask for changes to any post.
4. Approve and make. The assistant tells you the cost in AI credits first. You can set a limit, and it stops rather than going over.
5. Approve posts, then schedule. Only the posts you approve are scheduled, to the accounts you choose.

An example conversation

All tools

Your assistant sees these tools once you're connected. Tools that change something are marked.

What a key is allowed to do

When you make a key, you choose its permissions. A tool the key isn't allowed to use doesn't appear in your assistant. New keys and sign-in connections get posts:read, posts:write, users:read, billing:read, content:read and content:write.

You can see and remove every connection and key in Settings → API keys & Claude.

It asks before it posts or spends

• Publishing is confirmed. The assistant is told to publish only after you approve the exact text, media and accounts. Claude and ChatGPT also ask your permission before a tool that changes something runs.
• Costs come first. Paid steps show the price in AI credits before they run. If you don't have enough, you're told before anything starts.
• No double charges. Every paid request carries a one-time ID, so a retry after a dropped connection never posts twice or charges twice.
• Planning text is cheap. Researching and writing a plan uses a small fraction of a credit. Images and videos are what cost credits.
• Same limits as the app. Your plan's post limit, account limit and AI credits apply exactly as on the website.
• You can cut it off. Revoke a key or a sign-in connection in Settings and it stops working at once.

The REST API

Everything the MCP server does goes through our REST API, which you can call directly from your own code with the same key.

Try it

curl https://app.scheduloid.com/api/v1/me \
  -H "Authorization: Bearer sk_live_YOUR_KEY"

curl -X POST https://app.scheduloid.com/api/v1/posts \
  -H "Authorization: Bearer sk_live_YOUR_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"account_ids":[123],"text":"Hello from the API","schedule_at":"2026-12-01T10:00:00Z"}'

Field names and every endpoint are in the OpenAPI spec, which is kept in step with the live API.