Social Agent API and MCP Tools — Draft Posts from Cursor and Claude
Phase 2 of social publishing: /api/v1/social routes and aveiro_social_* MCP tools with social:write. Agents draft and revise; humans still approve every post.
Grant social:write on an API token or MCP connection. Agents list accounts, create drafts, generate media, and read rejection feedback. Approve, reject, and publish stay in the dashboard — no autonomous posting.
What we shipped
Social publishing beta gave teams a human-in-the-loop dashboard for Instagram and Threads. Phase 2 wires that pipeline to automation:
REST API (/api/v1/social/*)
Org-scoped bearer tokens with the new social:write scope can:
List connected accounts — use account IDs as post targets
OAuth MCP connections include social:write when social drafting is authorized.
Why we built it this way
Phase 1 proved the editorial workflow — drafts, feedback, approval, Chirio dispatch. Phase 2 lets the same workflow run from Cursor Cloud Agents, scheduled scripts, or Claude with MCP, without opening a loophole for autonomous posting.
Agents propose copy and schedules. Humans still click Approve. The guardrail is structural: no scope, route, or MCP tool grants publish.
Setup checklist
Step
Where
Enable Social publishing
Organization → Features
Connect Instagram and/or Threads
Dashboard → Social
Create API token with social:write
Organization → API tokens
Or connect MCP with social drafting
Cursor → MCP → Aveiro
Agent creates draft with targets + media
API or aveiro_social_create_draft
Human approves in dashboard
Social → Approve with schedule
Try it
Create a token with social:write (plus your usual content scopes if needed).
GET /api/v1/social/accounts — note an account ID.
POST /api/v1/social/posts with a short caption, one target, and submitForReview: true.
Open Dashboard → Social — the draft appears as Needs review.
Approve with a schedule or Post now.
In Cursor, connect the Aveiro MCP server and ask the agent to draft a post for review using aveiro_social_create_draft.
