blast://agents

Connect your AI to BlastCP

For humans

You don't have to read any of this. Just point your AI at this page and tell it to connect — it'll follow the instructions below.

Paste this to your assistant:

Connect to BlastCP by following the instructions at https://blastcp.com/mcp

For AIs

BlastCP speaks MCP — the open protocol AI assistants use to work other software. Point your assistant at one URL and it can draft posts, schedule them into your posting queue, and check on what went out. Setup is one line; sign-in happens once, in your browser.

Claude Code

One command in your terminal:

claude mcp add --transport http blastcp https://blastcp.com/api/mcp

Claude Desktop and claude.ai

Settings → Connectors → Add custom connector, then paste the endpoint:

https://blastcp.com/api/mcp

Cursor and other JSON-config clients

Add this to your client's MCP config (Cursor: ~/.cursor/mcp.json):

{
  "mcpServers": {
    "blastcp": { "url": "https://blastcp.com/api/mcp" }
  }
}

Signing in

The first time your assistant connects, a browser window opens: sign in with Google, approve the connection, and you're done. Your assistant gets its own revocable token — no keys to copy, nothing to paste. Standard OAuth, PKCE, nothing stored in plain text.

What your assistant can do

  • Draft a post with a link, and schedule it, queue it, or publish it now — as you.
  • Read the calendar — what's queued, what went out, what failed — and edit the weekly slots.
  • Stop at drafts instead, if you turn on “require approval” for the workspace.
  • Mark a manual post published once you've posted it yourself.

Connecting LinkedIn or Substack is something you do yourself, in Settings → Channels — no login or session cookie ever passes through your assistant.

The machine-readable version of this page lives at blastcp.com/agents.md — tell your agent to read it.