yeetpost

Posting

MCP for agents

yeetpost ships a hosted MCP server, so agents can post without you writing any glue. Streamable HTTP, the same API key, five tools.

#Point a client at it

The server speaks Streamable HTTP at POST https://api.yeetpost.com/api/v2/mcp and authenticates with the same API key as the REST API, in either header.

claude code
claude mcp add --transport http \
  --header "Authorization: Bearer $YEETPOST_API_KEY" \
  yeetpost https://api.yeetpost.com/api/v2/mcp

Any other MCP client works the same way: point it at that URL with an Authorization: Bearer <api-key> header, or x-api-key.

#The five tools

list_connectionsGET /connections

The accounts and channels available, with their slugs.

create_postPOST /posts

Posts text to connectionSlugs[], optionally at scheduledFor. Returns the same per-connection results array as POST /posts.

list_postsGET /posts

Recent posts, with an optional status filter and limit.

get_postGET /posts/{postId}

One post by postId.

cancel_scheduled_postDELETE /posts/{postId}

Cancels a scheduled post by postId.

Tool arguments use the same camelCase names as the JSON endpoints: text, connectionSlugs, scheduledFor, postId, status, limit.

#What a call looks like

tools/call
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "create_post",
    "arguments": {
      "text": "shipped the new api docs today",
      "connectionSlugs": [
        "linkedin",
        "x"
      ]
    }
  }
}
create_post returns the same per-connection results array as POST /posts, and a single connection failing is a failed item rather than a tool error. Tool errors are reserved for problems with the whole call: empty text, a bad scheduledFor, or none of the slugs matching a connection.

Every endpoint page on these docs carries an MCP tab where a tool maps to the endpoint, so you can read the REST call and the tool call side by side.

#Rate limits

The MCP endpoint has its own bucket: 60 requests per minute per API key, counted separately from /posts and /webhooks. See rate limits and request ids.