MCP integration
The planned MCP server and its live-backed tools.
MCP integration
Status: planned. The MCP server will let AI assistants (Claude Code, Cursor, and other MCP clients) act on your workspace through natural language — with the full tools catalogue below. It's a Creator-tier feature.
What works today
Every tool the MCP server will expose is already backed by a live REST endpoint (see API reference). You can automate the same actions right now with an API key.
The tools catalogue
| Tool | Backed by |
|---|---|
| list_accounts | GET /accounts |
| create_post / list_posts / update_post | /posts |
| publish_post, approve_post | /posts/{id}/publish, /approve |
| batch_create | POST /posts/batch |
| analytics_summary | GET /analytics/summary |
| usage | GET /me/usage |
| evergreen_rules, sync_routes | /evergreen, /syncs |
| disconnect_account | DELETE /accounts/{id} |
When it ships
When it ships, each workspace will get a unique MCP endpoint together with ready-made client configs (Claude Code one-liner and Claude Desktop JSON). The Developer → MCP Server page will host the live endpoint and setup snippets — the page today shows the catalogue and working REST examples.