The Postjam MCP server and API

Quickstart

Add the server to your agent, then ask it to call workspace_status. The first call opens a browser tab to sign in; after that the agent works on its own.

{
  "mcpServers": {
    "postjam": { "url": "https://mcp.postjam.app" }
  }
}

Claude Code

claude mcp add --transport http postjam https://mcp.postjam.app

Cursor

Paste the JSON above into .cursor/mcp.json

Codex

codex mcp add postjam --url https://mcp.postjam.app

Claude Desktop and claude.ai

Customize → Connectors → Add custom connector, paste the URL

Any other client: add a remote HTTP server at https://mcp.postjam.app, with no headers.

Endpoint

URL

https://mcp.postjam.app

Transport

Streamable HTTP (MCP), JSON-RPC 2.0 over POST

Sessions

None. Every request stands alone and carries its own token

Auth

OAuth 2.1 bearer token. No API keys

Timeout

300 seconds per call

Authentication

There is no API key to copy. A client gets a token the standard MCP way, and any client that implements MCP authorization does all of this for you:

1. 1
   ChallengeA request without a token is a 401 whose WWW-Authenticate header names https://mcp.postjam.app/.well-known/oauth-protected-resource.
2. 2
   DiscoveryThat document (RFC 9728) names the authorization server; its own discovery document lists the authorize, token and registration endpoints.
3. 3
   RegistrationThe client registers itself with dynamic client registration. Nothing to create in a dashboard first.
4. 4
   ConsentThe authorization-code flow with PKCE opens Postjam in the browser. The person signs in, or signs up, and approves the client by name.
5. 5
   BearerThe token endpoint returns an access token and a refresh token. Every call carries the access token as Authorization: Bearer.

A token is a grant to one client from one person, and it acts as that person. Revoke it any time from Settings → Agents in the dashboard. A browser session token is refused here, even a valid one: only a token somebody consented to opens this door.

Calling the API

The API is the MCP endpoint itself, so you can call it without an agent. List the tools with tools/list and run one with tools/call:

curl https://mcp.postjam.app \
  -H "Authorization: Bearer $POSTJAM_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": { "name": "workspace_status", "arguments": {} }
  }'

Each tool answers in plain text written for an agent to read back to a person: what happened, and the link to see it. A refusal (credits short, an account missing) is an answer too, not an HTTP error, and says what to do next.

Workspaces

Every tool takes an optional workspace argument, an id from list_workspaces. Leave it out and the call goes to your usual workspace.

Prompts

Three prompts ship with the server. Claude Code offers them as slash commands.

start

Reads the workspace and proposes the one next step, then waits for your yes.

import <url>

Imports a TikTok post as a format, then proposes accounts and a schedule.

post <files>

Uploads slides or a reel the agent made, hands them in as an export, and proposes where and when to post it.

Your own slides or reel

An agent that drew a carousel with Pillow, cut a reel with ffmpeg or generated clips elsewhere does not need a format to post it. Three calls take a finished post from the agent's machine to any account you connected, as a one-off, now or at a time you name:

1. 1
   Uploadprepare_upload names the files on the agent's machine and answers with one curl per file; finish_upload lands them in a gallery folder. Files already at a link go through upload_to_gallery instead.
2. 2
   Hand increate_export names the gallery files in slide order with the caption and hashtags, and answers with an export and its page. 1 credit, the price of an export.
3. 3
   Post or schedulepost_exports sends that export to the accounts you name: `when: "now"` for the next drain, or `when: "at"` with an ISO instant for later. Scheduling needs a plan; posting is free.

Images make a slideshow — a carousel on Instagram, Threads and Facebook, a photo post on TikTok — and one video makes a Reel, a Short or a TikTok. The platform's own limits apply when it is sent: Instagram takes 2 to 10 slides, Threads up to 20, TikTok up to 35. The export has a page like any other, stands on the calendar until its time, and can be brought forward or deleted there.

Tools

66 tools in 6 groups. Anything that sends something out (set_schedule, bind_accounts, post_exports) takes explicit accounts, days and times, and defaults to nothing.

Credits

The same credits as the dashboard. An import is 3 credits, an export is 1 whether Postjam rendered it or your agent handed it in, and posting it everywhere is free. A new account starts with 10. credit_balance and billing say what is left; when it runs short, the tool says so and hands back the link to top up.

What stays in the browser

The platform's own sign-in when connecting an account: connect_account hands back a single-use link, or the same as a QR code drawn in text, that any browser or phone opens, and connect_status says when it has landed. Choosing or changing a plan, TikTok's choice of who can see a direct post, and workspace settings stay in the dashboard; the tools that need them answer with the link. Everything else the dashboard does, a tool does. Everything an agent schedules shows on the format's Exports tab and the calendar before it goes out, where you can review it, post it early or pull it.

New here? Start with the MCP page.