What is MCP?
The Model Context Protocol is an open standard that lets AI clients (Claude Desktop, claude.ai web, Claude Code, Cursor, and others) call tools on remote servers. Postbreeze publishes an MCP server athttps://mcp.postbreeze.ai/mcp that wraps the same REST API documented
on this site.
Postbreeze’s MCP server supports two authentication paths:
- API keys (
pb_live_…) — best for Claude Desktop, Claude Code, Cursor, scripts, CI jobs. Paste a key into your client’s config. - OAuth 2.1 — best for claude.ai’s web “Custom Connectors”. One click on the connect button, a consent screen on postbreeze.ai, then you’re connected. No keys to copy or rotate.
claude.ai (web) — Custom Connectors via OAuth
Open claude.ai connector settings
On claude.ai, go to Settings → Connectors and click Add
Custom Connector.
Sign in to Postbreeze
claude.ai redirects to postbreeze.ai. Sign in if you’re not already.
You’ll land on the consent page.
Pick a workspace and click Allow
Choose which workspace claude.ai should be able to act on. (Each
grant is bound to exactly one workspace — to give claude.ai access
to a second workspace, repeat this flow.)
Claude Desktop
Create an API key
Settings → Developers → New API key. Name it “Claude Desktop”.
Copy the
pb_live_… value.Edit your Claude Desktop config
Open Settings → Developer → Edit Config in Claude Desktop. Add
the
postbreeze entry:Claude Code
Cursor
In Cursor’s Settings → MCP, add a new server with type HTTP and the URLhttps://mcp.postbreeze.ai/mcp. Add the Authorization header
with your Bearer pb_live_… token.
What can the LLM do?
See the Tools page for the full v1 surface —list_posts,
schedule_post, update_post, cancel_post, list_connected_accounts,
list_media, ingest_media_from_url, list_comments, reply_to_comment,
and per-platform analytics.