MCP access with a real boundary.
Give agents scoped tools, explicit consent, and a clear way to revoke access.
MCP interoperability, OAuth client support, consent scopes, and API-token controls live in the Integrations workspace.
Made to work as a system.
Connect compatible assistants to approved work without creating a universal back door.
Compatible clients
Expose a protocol endpoint that supported MCP clients can discover and use.
Scoped consent
Authorize named capabilities instead of granting blanket access to site data.
Token controls
Create, review, and revoke API tokens and integration access from one workspace.
Verification boundary
Keep reachability, authentication, authorization, mutation, and readback as distinct checks.