Studios

The workspace every tool call is scoped to.

A studio is a workspace: it owns posts, platform connections, uploaded assets, and members. Everything the MCP server touches is scoped to exactly one studio — the one resolved from your session.

• Signing in with Google for the first time creates a personal studio automatically, with you as owner.
• Members can be invited from the web app (/settings) with role owner, admin, or member.
• Data never crosses studios. A post or asset id from another studio simply reads as not_found.

Roles

Role	Can do
owner	Everything, including connecting and disconnecting platforms
admin	Same as owner for the MCP tools
member	Drafts, publishing, scheduling, assets — not connections

Studio selection over MCP

The MCP session picks your active studio if the token’s user is a member of it, and otherwise falls back to your first membership. See Authentication.