Posting queue · MCP-first
Your agent writes the post.
BlastCP sends it on schedule.
Connect LinkedIn and Substack once. Then any AI with an MCP connector can draft, queue, and publish as you — or stop at drafts, if you want the last word.
› create_post
platform: "linkedin"
intent: "queue"
body: "Why we killed the weekly status meeting…"
✓ scheduled · Mon 09:00 · the next free slot
- Mon 09:00LinkedInWhy we killed the weekly status meetingsending
- Wed 09:00SubstackThe two-pizza rule was never about pizzaqueued
- Fri 09:00LinkedInHiring a founding designer: the briefqueued
How it works
Three moves, then it runs itself.
- 01
Connect a channel
LinkedIn signs in with OAuth. Substack takes your session cookie and only ever creates drafts. You do this once, in the app — no credential passes through an agent.
- 02
Point your AI at BlastCP
One URL. Claude, Cursor, or anything that speaks MCP walks a standard OAuth flow and gets a revocable token that acts as you.
- 03
Say “queue this”
The agent drafts, attaches a link, and drops it into your weekly slots — or names a time, or publishes now. The calendar shows what went out and what didn’t.
approval: off
The agent schedules.
Its token is your account, so a queued post goes out under your name and the record says who queued it. This is the default. It is what makes a Monday-morning “queue these three” a single sentence.
approval: on
A person approves.
Flip one switch in the workspace and every agent stops at a draft. It hands back a link; you read it, then schedule it. Same queue, same calendar, one more click.
One line
Any assistant that speaks MCP.
Claude Code, Claude Desktop, Cursor. Sign-in happens once, in your browser. The token is revocable and never leaves your client. Setup for every client →
claude mcp add --transport http blastcp https://blastcp.com/api/mcpLinkedIn · Substack (drafts) · next: Facebook, Instagram, TikTok, YouTube