Skip to main content
Hosted MCP exposes these 27 operational tools. tools/list returns only the tools your connection has permission to call, together with their current input schemas.

Workspace

Customers

Conversations and messages

Recording a message does not send it through email or another connected channel. Do not treat a successful create_message result as delivery confirmation.

Webhooks

Inputs and writes

Tool schemas use top-level path and query parameters, and a body object for request bodies. The API reference describes each operation’s resource fields. Every write requires expectedWorkspaceId, matching the result of workspace_context. Operations that support idempotent retries also require idempotencyKey; the tool’s input schema identifies them. Other writes do not promise idempotent retries. Writes execute immediately. Confirm the user’s intended action before calling them. If a result is uncertain, read the resource to reconcile its state. When retrying an idempotent operation, reuse the original arguments and key. Successful results include workspaceId, status, data, requestId, and replayed. Failed HTTP operations become MCP tool errors.

Help Center tools

Eligible API-key connections also expose these tools. Reads require help:read; proposals additionally require help:drafts:write. OAuth does not grant these permissions. Hosted tool inputs follow the REST schemas, including a body object for proposal payloads. They are not interchangeable with the local stdio input shapes. Consult tools/list and the Help authoring API reference for the current schema. Both transports retain connection-bound proposal ownership and the human review workflow.