MCP server

https://api.relay.lantean.tech/mcp

Authorization: Bearer rly_live_…

claude mcp add --transport http relay https://api.relay.lantean.tech/mcp \
  --header "Authorization: Bearer $RELAY_API_KEY"

claude mcp list          # should report: relay ✔ Connected

{
  "mcpServers": {
    "relay": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://api.relay.lantean.tech/mcp",
        "--header", "Authorization: Bearer ${RELAY_API_KEY}"
      ],
      "env": { "RELAY_API_KEY": "rly_live_…" }
    }
  }
}

{
  "mcpServers": {
    "relay": {
      "url": "https://api.relay.lantean.tech/mcp",
      "headers": { "Authorization": "Bearer rly_live_…" }
    }
  }
}

{
  "inputs": [
    { "type": "promptString", "id": "relay-key", "description": "Relay API key", "password": true }
  ],
  "servers": {
    "relay": {
      "type": "http",
      "url": "https://api.relay.lantean.tech/mcp",
      "headers": { "Authorization": "Bearer ${input:relay-key}" }
    }
  }
}

{
  "mcpServers": {
    "relay": {
      "type": "streamable-http",
      "url": "https://api.relay.lantean.tech/mcp",
      "headers": { "Authorization": "Bearer rly_live_…" }
    }
  }
}

curl -X POST https://api.relay.lantean.tech/mcp \
  -H "Authorization: Bearer $RELAY_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

{
  "content": [{ "type": "text", "text": "{ \"post\": { … } }" }],
  "structuredContent": {
    "post": { "id": "3f0c…", "status": "scheduled", "targets": [ … ] }
  }
}

Relay publishes posts to Instagram and TikTok. The path that works, in order:
auth_status          → confirm the key works and something is connected
accounts_list        → resolve a handle like "@northlight.co" to an account id (each has a platform)
tiktok_creator_info  → TikTok targets only: which privacy levels and interactions that creator allows right now
media_upload         → optional: store a file once (public URL, or small inline base64), reuse it across posts
post_create          → queue the post (targets + caption + media [+ tiktok] [+ schedule_at]), or stage it with draft: true
post_status        → poll until every target is published or failed
post_retry         → re-queue a failed or partly-published post after fixing the cause

Rules:
- Never guess an account ID or a post ID — resolve them with accounts_list and posts_list.
- Scheduling is not instant publishing: post_create without schedule_at still goes out on the next scheduler tick, within a minute.
- After creating a post, wait ~30 seconds before the first post_status call. Video takes longer than images — minutes, not seconds.
- Confirm with the user before post_cancel.
- TikTok targets need a tiktok object. For mode "direct" (the default) tiktok.privacy_level is required and has no default: ask the user who should see the post, and offer only the levels tiktok_creator_info returns. Comments, duets and stitches stay off unless the user turns them on. Say whether the post promotes the user's own brand (brand_organic) or a third party (brand_content) — branded content cannot be SELF_ONLY. mode "inbox" sends it to the creator's TikTok inbox to finish in the app instead.
- TikTok takes one video, or 1–35 JPEG images as a photo post; it has no stories and no first comments. A post that targets Instagram as well is held to Instagram's limits too (at most 10 items).
- Posting to TikTok means the user agrees to TikTok's Music Usage Confirmation (and its Branded Content Policy when brand_content is set) — make sure they know before you publish.
- Media over ~700KB cannot go inline: the whole MCP request is capped at 1MB and base64 costs a third on top. POST the raw bytes to /v1/uploads on the same host as this endpoint instead — your API key, the file's Content-Type (image/jpeg, video/mp4, or video/quicktime), and Content-Length set to the exact byte count, which is required. It answers 201 with upload.url, a public link you pass as a media entry to post_create or as media_upload's url, and upload.expires_at, usually an hour out. Create the post before then; the post keeps its own permanent copy, so scheduling weeks ahead is fine.
- Do not publish without an explicit go-ahead. To get one, call post_create with draft: true and give the user the preview_url it returns — that page shows the post exactly as Instagram and TikTok will render it, with Publish and Schedule buttons. A draft never publishes on its own, so this is the safe default when the user has not already told you to send it.