Skip to main content

assembl · mcp

A governed doorway into Assembl.

Assembl MCP lets authorised tools such as ChatGPT or Codex read work and proof, create proposed internal work, and place drafts into the human approval queue. MCP does not bypass the Assembl runtime, permissions, approvals or evidence ledger.

DO Enquiries · private pilot

Open DO → Enquiries, sign in with your verified founder account, and enable enquiry plugin access. Then connect https://www.assembl.co.nz/api/mcp through your client’s OAuth flow. The endpoint uses Assembl sign-in; Sign in with ChatGPT is a separate partner integration.

The tools are list_enquiries, get_enquiry_evidence and prepare_enquiry_reply. They prepare work and return evidence and approval links. Review and approve sending on the signed-in Assembl page.

Your OAuth server and client registration must be configured before connecting. This pilot is not a published directory listing. Revoke enquiry plugin access on the Enquiries page whenever you need to.

Current tools

  • list_work — recent work in the authorised workspace.
  • get_work_item — task detail, plan and activity.
  • read_proof — evidence attached to work.
  • create_work_item — creates a proposed internal task only.
  • request_action_approval — places an email draft into the human approval queue; it does not send.

Authorization model

OAuth 2.1 proves the user identity. Assembl then resolves the user to an explicit tenant membership and business permissions. Tenant identity cannot be supplied or overridden by a model tool call.

Sending, publishing, spending, deleting and consequential external changes remain separate Assembl capabilities with their own policy and human-approval boundaries.

For administrators

Production access is granted per user and workspace. Revoke the OAuth grant or the Assembl MCP membership to remove access. Write tools can also be disabled globally without affecting read-only access.