AAttentionPilot

Live now

Post to social from Claude

AttentionPilot runs an MCP server. Point Claude at it and you can say “post this to X and Bluesky at 9am” and it happens — with the same pre-flight checks and per-network delivery isolation the app uses.

Connect it

Add AttentionPilot as a remote MCP server in Claude, with your API key as a bearer token.

{
  "mcpServers": {
    "attentionpilot": {
      "type": "http",
      "url": "https://attentionpilot.com/api/mcp",
      "headers": {
        "Authorization": "Bearer pilot_your_key_here"
      }
    }
  }
}

What it can do

list_accountsWhat's connected, and on which network.
create_postPublish now, schedule for a time, or drop into the queue.
list_postsRecent posts and how each network delivery went.

Then just ask

You: Post "we shipped per-network retries today" to X and Bluesky.

Claude: [list_accounts] → x (@yourbrand), bluesky (@you.bsky.social)
        [create_post] → Scheduled for 2026-08-01T09:00:00Z on:
                        x (@yourbrand), bluesky (@you.bsky.social).

It tells the model why

When a caption won't pass, the tool returns the specific network and its limit rather than a generic failure — so the model can shorten it and retry instead of discovering the problem after half your networks already published.

This caption will not pass on every network you chose:
- x: 412 chars — X allows 280.

Shorten it, or target fewer networks.

A note on access

Discovery — the handshake and the tool list — is open, so a client can find the server before it has a key. Anything that touches your accounts requires one. An MCP server that publishes to real social accounts unauthenticated would be an obvious hole, and some are.

Ten networks, one sentence.

Start free5 posts a month, no card.