Organizations via MCP and API
Manage org structure through session-authenticated dashboard APIs. MCP tools operate on the caller's org but do not replace admin endpoints.
Org summary
GET /api/org Authorization: Bearer <session_jwt>
Returns org name, your role, teams, and accessible_team_ids.
Teams
| Method | Path | Admin only |
|---|---|---|
| GET | /api/org/teams | No |
| POST | /api/org/teams | Yes |
| PATCH | /api/org/teams/{id} | Yes |
| DELETE | /api/org/teams/{id} | Yes (moves resources to General) |
Members and invites
| Method | Path | Admin only |
|---|---|---|
| GET | /api/org/members | Yes |
| POST | /api/org/members | Yes (invite) |
| PATCH | /api/org/members/{userId} | Yes |
| DELETE | /api/org/members/{userId} | Yes |
| POST | /api/org/invites/accept | Invitee |
Audit log
GET /api/org/audit?page=1&limit=50 Authorization: Bearer <session_jwt>
Org admins only. Dashboard: Team → Audit.
Envelope team reassignment
PATCH /api/envelope/{id}/team
{ "team_id": "<uuid>" }
Org admin only.
MCP org awareness
MCP create responses include team_id, created_by, and org_credits_remaining when available.
MCP list tools accept optional team_id:
list_envelopes({ team_id })list_templates({ team_id })send_contract_for_review({ team_id })when the user has multiple teams
MCP does not expose invite, audit, or team CRUD. Use dashboard or session APIs for admin work.
Platform orgs
Platform and connected account orgs use the same team model inside each workspace. Connected account lifecycle is under /api/platform/*, not /api/org/*.