Skip to main content

Security & data access

Connecting an assistant gives it real access to your CRM, so Zoie's MCP server is built so you stay in control of exactly what it can reach.

You authorize with OAuth, not API keys​

Connections use OAuth 2.1. You never paste a Zoie password or long-lived API key into the assistant. Instead, the assistant is redirected to a Zoie consent screen where you sign in and approve access. Zoie issues the assistant its own credential, which you can revoke independently.

Clients register themselves automatically via dynamic client registration, and the server publishes its OAuth metadata per RFC 9728, so compliant clients discover the right authorization server without manual configuration.

Access is scoped​

Two boundaries limit every connection:

  • Permission scopes — the assistant only gets the read/write categories you approved (Leads, Conversations, Appointments, Campaigns). See Permissions & scopes.
  • One business per connection — a connection is tied to a single business and cannot reach data in any other business, even ones your own account can access.

Everything is logged​

Each connection keeps an activity log of the tools the assistant called, with timestamps and success/error status, plus a last used time. This gives you an audit trail of exactly what an assistant did. See Managing connections.

You can revoke at any time​

Access is not permanent. From Settings → Claude / ChatGPT / Other MCP connectors you can revoke any connection, which immediately cuts off the assistant's access to your data. Reconnecting requires going through consent again.

What an assistant cannot do​

  • It cannot exceed the scopes you approved (e.g. write if you granted read only).
  • It cannot reach a business you didn't select for that connection.
  • It cannot access Zoie's admin/platform tooling — MCP exposes business CRM data only.

Good practices​

  • Grant the least access an assistant needs — prefer Read only when the assistant just needs to look things up.
  • Review the activity log after big tasks to confirm what changed.
  • Revoke connections you no longer use.
  • Connect from the environment that matches your data (production vs. beta/dev) so you're not surprised by which records appear.