Developer API

ThreadMaster MCP server

Let Claude Code, Cursor, Claude Desktop or any MCP client draft, schedule and publish your threads. One endpoint, your existing API key, the same quotas as the REST API.

Create an API key REST API docs

claude mcp add --transport http threadmaster https://threadmaster.ai/api/public/v1/mcp/ \
  --header "Authorization: Bearer tm_live_YOUR_KEY"
# then run: claude mcp list

How it works

Stateless HTTP

Single endpoint POST https://threadmaster.ai/api/public/v1/mcp/. JSON-RPC over Streamable HTTP, no sessions, works behind any proxy.

Same key, same limits

Send Authorization: Bearer tm_live_…. Requests count against the same per-key burst and daily limits and the same AI-generation and publishing caps as the REST API. Keys are revocable in Settings.

Speaks old and new MCP

Supports protocol revision 2026-07-28 and legacy clients on 2025-03-26 → 2025-11-25 (2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26).

Connect

Claude Code

claude mcp add --transport http threadmaster https://threadmaster.ai/api/public/v1/mcp/ \
  --header "Authorization: Bearer tm_live_YOUR_KEY"
# then run: claude mcp list

Claude Code — project .mcp.json (keeps the key in an env var)

{
  "mcpServers": {
    "threadmaster": {
      "type": "http",
      "url": "https://threadmaster.ai/api/public/v1/mcp/",
      "headers": {
        "Authorization": "Bearer ${THREADMASTER_API_KEY}"
      }
    }
  }
}

Cursor — ~/.cursor/mcp.json

{
  "mcpServers": {
    "threadmaster": {
      "url": "https://threadmaster.ai/api/public/v1/mcp/",
      "headers": {
        "Authorization": "Bearer tm_live_YOUR_KEY"
      }
    }
  }
}

Claude Desktop and other clients without header support — via mcp-remote

{
  "mcpServers": {
    "threadmaster": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://threadmaster.ai/api/public/v1/mcp/",
        "--header",
        "Authorization: Bearer tm_live_YOUR_KEY"
      ]
    }
  }
}

Clients that only support OAuth-based remote connectors (for example ChatGPT connectors) are not supported yet.

Tools

Tool	What it does	Arguments
`whoami`	Your account, key and subscription	none
`get_quota`	Remaining posts this month and reset date	none
`list_connected_accounts`	Connected X, Threads and Facebook Pages	none
`generate_thread`	Generate a thread with AI from a topic	topic (required), style, thread_format, language, regenerate
`create_thread`	Save a thread you wrote yourself	topic, content (required), thread_format
`list_threads`	Browse your threads	status, favorite, since, limit, cursor
`get_thread`	One thread with its publications	thread_id
`update_thread`	Edit topic, content or favourite flag	thread_id, topic, content, is_favorite
`delete_thread`	Delete an unpublished thread	thread_id
`preview_x_thread`	See how the thread splits into X posts	thread_id
`publish_to_x`	Post now, schedule, or queue on X	thread_id, scheduled_for, queue, idempotency_key
`publish_to_threads`	Post to Meta Threads	thread_id, share_to_instagram, idempotency_key
`list_facebook_pages`	Facebook Pages you can post to	none
`publish_to_facebook`	Post to a Facebook Page	thread_id, page_id, mode, idempotency_key
`list_posts`	Publish jobs per platform	platform, status, since, limit, cursor
`get_post`	One publish job	platform, post_id
`cancel_x_post`	Cancel a scheduled X post	post_id
`reschedule_x_post`	Move a scheduled X post	post_id, scheduled_for
`retry_post`	Retry a failed publish job	platform, post_id
`get_post_metrics`	Likes, impressions, replies and more	platform, post_id

Publishing tools post to your real accounts. Good MCP clients ask for confirmation before running them; keep it that way.

What people do with it

All use cases →

Under the hood

Each tool call runs the matching REST endpoint in-process, so scopes, quotas, throttles, Idempotency-Key and error codes behave exactly as documented on /developers.
Errors come back as tool results with isError: true and the REST error envelope in structuredContent.
Rate-limit headers X-RateLimit-* are on every MCP response.

Try it with curl

curl -s https://threadmaster.ai/api/public/v1/mcp/ \
  -H "Authorization: Bearer tm_live_YOUR_KEY" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"curl","version":"1"}}}'

curl -s https://threadmaster.ai/api/public/v1/mcp/ \
  -H "Authorization: Bearer tm_live_YOUR_KEY" -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"whoami","arguments":{}}}'

Get started

Write your next Twitter thread or LinkedIn post today

Get started →