Workspace MCP tools
Connect exposes OAuth-authenticated workspace MCP tools. A grant is bound to one workspace and one selected business. Read tools cover profile, readiness, follow-ups, memory and business-scoped customer-operations records; configuration tools update supported Business Setup, channels, autonomy, runtime and memory under explicit write authority; and three operations tools reach every other operation Connect has — sending, calling, campaigns, Employees, settings, administration — with consequential ones waiting for the person's confirmation.
Read surface#
- Business profile, operational readiness and runtime state.
- Follow-ups and central business memory.
- Business-bound searches for people, companies, leads, prospects, opportunities, conversations, calls, cases, onboarding and Knowledge.
- The sheet and business for domain searches are fixed server-side; neither is an arbitrary caller-controlled query target.
Write surface#
- Update supported Business Setup profile fields.
- Set Email, Phone, SMS or WhatsApp requirement state.
- Assign supported business channel endpoints.
- Set autonomy policy within the workspace ceiling.
- Start or pause runtime only when Owner/workspace-admin authorization permits it.
- Add or archive central business memory.
Every other operation#
Beyond the business tools above, the operations tools reach all 384 operations of Connect's versioned API: email, campaigns, audiences, CRM, prospects and leads, customers, WhatsApp messages and calls, AI phone calls, Employees, the Office Manager, workflows, automations, analytics, knowledge, integrations, business settings and administration.
| Tool | What it does | Scope |
|---|---|---|
connect_list_operations | Search the catalogue by area, risk tier or words, paged with cursor. Each entry gives its id, risk tier, required scope, whether the person must confirm it, and whether this connection may use it. | mcp:app:read |
connect_describe_operation | The full contract of one operation: what it does, its tier, scope, confirmation rule and the exact JSON Schema of its path, query and body arguments. | mcp:app:read |
connect_call_operation | Perform one operation as the person who connected the client. Writes accept idempotency_key; consequential operations wait for confirmation. | The operation's own tier |
Every operation runs as the person who connected the client, through the same handler their browser reaches, so their role, their business access, their plan, the autonomy mode, the approval policy and the audit trail apply unchanged. Two things are deliberately different: an agent is never treated as the person pressing Send, so a send under ask-before-send comes back held rather than skipping the gate; and approving held work is refused with person_required, because that step is the person's to take in Connect.
Delete, execute, admin and financial operations are never performed on the first call. A client that speaks revision 2026-07-28 and declares elicitation gets an input_required result carrying an elicitation form, which it shows the person; the retry with their answer performs the operation. Any other client gets a result with status: confirmation_required, a plain summary of exactly what would happen and a confirmation_token: show the person the summary, and only if they agree call again with the identical arguments plus that token. The token is bound to this authorization, this operation and these exact arguments, lasts ten minutes, and its nonce becomes the request's idempotency key, so a confirmed operation retried after a timeout returns its first answer (replayed: true) instead of being performed twice.
Identity and sibling-business protection#
A workspace can contain several businesses and can also know one human across more than one of them. The normal product has human workflows that can deliberately share or adopt that relationship. A single-business MCP grant is narrower. If a supplied email or phone already resolves to a Person outside the authorized business, the create-person tool refuses instead of attaching that Person to the current business. A legacy email Contact outside the business is refused for the same reason.
What success evidence looks like#
Configuration writes already use a persist, read-back, compare sequence and return audit evidence. Customer-operation writes return the row after the canonical Data Workspace has re-read it inside the same business reach. A client should report a held, refused, conflict or verification failure exactly as returned. Retrying a failed state transition as though transport had failed can turn an explicit safety decision into repeated pressure on the same boundary.
- Use read tools first when the requested write depends on current state.
- Use the smallest matching tool instead of reconstructing a generic data editor.
- Keep the business implicit in authorization; never ask a model to copy an internal id between businesses.
- Treat missing records as absent within this business, not as evidence that they do not exist anywhere in the workspace.
Questions#
Can the model pass another business id?
No. Protected tools derive it from authorization.
Are MCP test tools available in production?
No. Diagnostics require an explicitly non-production deployment and explicit opt-in.
Can MCP bypass Connect's normal domain rules?
No. The MCP facade uses canonical services and Data Workspace reach rules.