Schedchie Logo
Schedchie
Start free trial

Schedchie in Claude API and Agent SDKAPI

Build social posting into your Claude agent

The Claude API reaches Schedchie’s MCP server through the MCP connector with a connection token as authorization_token, and gets the posting, media and analytics tools. Schedchie is a flat-price social media scheduler for 20 platforms: Pro is €9.99 a month, with MCP included.

  • Messages API: mcp_servers plus an mcp_toolset entry, with a connection token as authorization_token.
  • Agent SDK: an http server with an Authorization header. Same token, same tools.
  • The API runs no sign-in: you pass a token, and the token carries posting, media and analytics.
Start free trial

14-day free trialCancel anytime, no questions asked

See the 4 setup steps

Setting up Claude API and Agent SDK

The Messages API connects to remote MCP servers itself. Point it at Schedchie with a connection token and your own agent can schedule, edit and report on posts.

Requirements

Access
An Anthropic API key. The MCP connector is a beta on the Messages API (anthropic-beta: mcp-client-2026-09-15), and neither the API nor the Agent SDK runs an OAuth sign-in, so you pass a token.

  1. Claude API and Agent SDKConfig

    Messages API: add the server and its toolset

    POST this body to /v1/messages with the header anthropic-beta: mcp-client-2026-09-15. The server goes in mcp_servers, and one mcp_toolset in tools must name it.

    Config
    {
  "model": "claude-opus-5-5",
  "max_tokens": 1000,
  "messages": [{"role": "user", "content": "List my Schedchie accounts."}],
  "mcp_servers": [{
    "type": "url",
    "url": "https://mcp.schedchie.com/mcp",
    "name": "schedchie",
    "authorization_token": "<connection token>"
  }],
  "tools": [{"type": "mcp_toolset", "mcp_server_name": "schedchie"}]
}

  2. Claude API and Agent SDKConfig

    Agent SDK: an http server with a header

    In the Agent SDK, pass the server in mcpServers as type http with the token in an Authorization header, and allow its tools.

    Config
    const options = {
  mcpServers: {
    schedchie: {
      type: "http",
      url: "https://mcp.schedchie.com/mcp",
      headers: { Authorization: "Bearer <connection token>" }
    }
  },
  allowedTools: ["mcp__schedchie__*"]
}

  3. Claude API and Agent SDKPrompt

    Read the response

    Claude calls the Schedchie tools and returns mcp_tool_use and mcp_tool_result blocks, plus mcp_tool_listing blocks under the 2026-09-15 header. Send the assistant message back unchanged on the next request.

Official docs: platform.claude.com/docs/en/agents-and-tools/mcp-connector

Three prompts for Claude API and Agent SDK, with the tools they call

  • A request that drafts tomorrow’s LinkedIn post from a changelog entry and schedules it for 9:00.

    list_accounts, schedule_posts

  • List the connected accounts and what each one has scheduled next week.

    list_accounts, list_posts

  • Which posts are waiting for my approval? Approve the LinkedIn one.

    list_pending_approvals, approve_post (Ultra)

Connection details

Same MCP server, permission groups and approvals as the Schedchie web app.

Request shape
mcp_servers with type url, url, name and authorization_token, and one mcp_toolset in tools that names the server.
Response
mcp_tool_use, mcp_tool_result and, under the 2026-09-15 header, mcp_tool_listing blocks. Code that reads content[0] skips the listing; the assistant message goes back unchanged with the header on every later request.
Beta header
anthropic-beta: mcp-client-2026-09-15. It includes everything mcp-client-2025-11-20 does; mcp-client-2025-04-04 is deprecated.
Sign-in
The API does not run OAuth. You pass a token: a Schedchie connection token, or an access token your app gets through our OAuth flow.
What the connector covers
Tool calls only, over Streamable HTTP or SSE. It is not covered by zero data retention arrangements.
Tools
With a connection token: posting, media and analytics.
Only what you tick
Connect Claude API and Agent SDK to Schedchie. Your assistant gets the posting, media and analytics tools across 20 platforms, and only the permission groups you tick at sign-in.
Video from your phone
Your assistant can hand you an upload link for a video up to 200 MB and 15 minutes, then set your own cover on Instagram, Facebook, TikTok, Pinterest and YouTube.

More about Schedchie in Claude API and Agent SDK

What does a connection token give access to?

Posting, media and analytics: schedule, edit and retry posts, upload media, read analytics. Team, approvals, library and engagement need the browser sign-in. A token lasts 30 days; generate a new one in Dashboard, AI assistants.

Can my app use the OAuth sign-in instead of a token?

Yes, if your app runs the flow. Anthropic leaves OAuth to the caller: get and refresh the access token yourself and pass it as authorization_token. Schedchie supports dynamic client registration and PKCE, and the token then carries the groups the user ticked.

Which beta header do I send?

mcp-client-2026-09-15. Anthropic’s page says it includes everything mcp-client-2025-11-20 does, and mcp-client-2025-04-04 is deprecated.

Do I still need tools if I set mcp_servers?

Yes. Each server in mcp_servers must be referenced by exactly one mcp_toolset in tools, or Claude gets none of its tools.

Is the MCP connection billed on top of the plan?

No. It is included on every plan and in the 14-day free trial. Pro is €9.99 a month, flat. Posting to X is paid in X credits, as in the web app.

Are there limits?

Each connection can make up to 120 tool calls a minute. On Pro it gets 300 tool calls an hour, plus 30 session opens that make no call; on Ultra four times that, 1,200 calls and 120 opens.

14 days on your own accounts, then €9.99 a month

The assistant connection is included on every plan and in the trial.

Start free trial

14-day free trialCancel anytime, no questions asked

Other assistants on the same server

Claude API and Agent SDK and its logo belong to Anthropic. Schedchie is not affiliated with or endorsed by Anthropic.