Clarify

Your client is holding a stale tool list. Clarify renamed several write tools, so `create-record`, `update-record` and `create-list` now fail with MCP error -32602 while read queries keep working. Clarify's own fix is to remove the Clarify app from your client and add it again, because reconnecting alone does not refresh the list.

Not directly. Clarify's MCP tools create campaigns in draft mode, and Clarify documents a connected email account as required to enable a campaign rather than to create one. No tool in either published list enables a campaign. Sending starts when a human flips the Enabled toggle in the app.

Yes, and this is the sharpest risk on the connector. Clarify states that agents Rep builds are enabled on creation and start running when their trigger next fires. An agent can send email automatically when configured to, and Clarify names the absence of undo for agent actions as its most significant limitation today.

Partly, and the granularity is coarse. Clarify scopes agents to their creator's permissions, so an agent cannot read records its owner cannot. But Clarify offers only two roles, Admin and Member, and states more granular permissions are planned. Members reach every CRM record, so role is a weak boundary.

Your AI client decides when to call a connector, not Clarify. Clarify recommends three fixes: confirm Clarify is enabled for that specific conversation rather than only added to your account, name Clarify in your first message, and add a line to your project instructions telling the assistant to use Clarify for CRM questions.

Authenticate with a Personal API key instead of OAuth. Clarify states the interactive login needs periodic re-authorising, which interrupts scheduled work. Send the key as an `api-key` authorization header alongside an `X-Clarify-Workspace` header. Only Personal keys work; Clarify warns a workspace key lists every tool then fails on every call.

Only in your AI client, not at Clarify's consent screen. Clarify's OAuth server advertises four scopes and all four are identity scopes, so there is no read-only grant to choose. Clarify states every tool is available to all workspaces with nothing to enable on its side, which puts the whole approval burden on your client.