Cloze
by Cloze
Search a Cloze CRM, add contacts, log notes and to-dos, and draft emails from an AI agent. Anthropic lists 20 tools; Cloze documents 14, and three of those are absent from the directory. OAuth sign-in, Business Platinum plan required.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Cloze via MCP
https://api.cloze.com/v1/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Cloze Tools & Capabilities (20)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Cloze calls this a beta. Both MCP articles open with a notice stating the server is experimental, still in development, and provided on an as-is basis, and warning of bugs, errors and unexpected behavior. Cloze's Maia article adds that AI "can get things wrong" and to double-check important information.
- The server publishes no RFC 9728 descriptor.
https://api.cloze.com/.well-known/oauth-protected-resourceand the path-suffixed variant both returned 404 on 2026-08-22, with a body hash identical to a deliberately bogus control path — so this is a genuine absence, not a catch-all. The 401 response also carried noWWW-Authenticateheader, so a client cannot discover Cloze's authorization server from the endpoint. Discovery works only becausehttps://api.cloze.com/.well-known/oauth-authorization-serverhappens to answer. - No MCP scope boundary is published. Cloze's authorization server metadata omits
scopes_supportedentirely. The REST descriptor's twelve scopes are API-level; the one namedmcpgrants "Use Cloze as an MCP server" without stating which data scopes it carries. - Delete is not separated from edit.
delete_relationis advertised as a scope but appears on no operation in the published spec; all three delete endpoints requirechange_relation, the same scope as create and update. - Neither tool list is complete or current. Anthropic lists 20, Cloze documents 14, 11 overlap, and the union is 23. Cloze's tool article is dated 2025-08-31 and its connection article 2026-08-26.
- We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request on 2026-08-22, so no parameter-level detail is published here. Everything said above about
campaignId,archivedandreplaceIdentitydescribes Cloze's REST API, and we could not confirm the MCP tools expose those fields. - Plan gates stack. Business Platinum for MCP itself, Business Platinum for campaigns, and both Cloze Enterprise and Canva Enterprise for
canva_create_designs. - One client only. Cloze documents Claude Desktop and says other clients are in the works.
- No rate limits are published. Cloze's OpenAPI specification contains no rate-limit, retry or 429 documentation, and we found none in its help centre. Absence of documentation is not absence of limits.
- Whether a stage change emails a contact is unresolved in the general case. Cloze documents stage and segment changes as campaign triggers, and campaigns as sending email, but whether your workspace has such a campaign configured is not knowable from outside it. Treat it as possible rather than as a no.
Frequently asked questions
Not directly. The tool named for email is save_draft, and Cloze documents it as saving the message to your Cloze drafts for you to review, edit and send. Cloze's own help article on drafts describes them as messages you return to later. No tool name in either list carries a send verb, so nothing transmits without you pressing send.
Indirectly, and this is the risk worth understanding. Cloze's API carries an optional write-only campaignId field on the person record that triggers a campaign. Separately, Cloze documents stage, segment and next-step changes as campaign triggers, and person_change edits all three. A campaign sends real emails, so a routine contact edit can start outbound mail.
No tool name in either list carries a delete verb, but do not read that as a boundary. Cloze's OAuth descriptor advertises a delete_relation scope covering people, companies and projects. Its published API instead puts all three delete endpoints under change_relation, the same scope as create and update, so no grant separates editing from deleting.
Three, and all three push data to an outside platform. Cloze's help article names canva_create_designs, project_send_to_cloudcma and project_send_to_homespotter with bracketed tool names. None appears in Anthropic's twenty-name listing. Canva design creation additionally requires both a Cloze Enterprise and a Canva Enterprise plan, per Cloze's documentation.
A Cloze Business Platinum subscription or trial, plus a Claude Pro plan or above. Cloze states both prerequisites in its connection article, and notes that the custom connector option is only visible on Claude Pro and higher. Cloze currently supports Claude Desktop only, describing more clients as in the works.
Contact records and communication history about people who never authorised anything. Cloze's API person record carries emails, phone numbers, postal addresses, birthday, gender, household and social handles. The timeline tools return logged calls, texts, meetings and email bodies, so third-party correspondence enters the agent's context.
No. Cloze labels it a beta feature in a notice at the top of both of its MCP articles, stating it is experimental, still in development, and provided on an as-is basis. Cloze explicitly warns you may encounter bugs, errors or unexpected behavior. Treat outputs as unverified and check anything consequential.
No. The connector uses OAuth, and Cloze's authorization server metadata advertises a dynamic client registration endpoint, so Claude registers itself. You add the endpoint as a custom connector, click Connect, and approve. API keys exist in Cloze for direct REST access but are not part of the documented MCP setup.
Sources
- Cloze MCP Server help article (retrieved 2026-08-22) · retrieved 2026-08-22
- Cloze, "What can I ask my AI assistant to do in Cloze?" — the vendor tool enumeration (retrieved 2026-08-22) · retrieved 2026-08-22
- Cloze, "How do I connect Claude to Cloze?" (retrieved 2026-08-22) · retrieved 2026-08-22
- Cloze API Reference, OpenAPI 3.1.1 specification version 2026.7 — scopes, person schema and delete endpoints (retrieved 2026-08-22) · retrieved 2026-08-22
- Cloze, "What triggers a Cloze Campaign to start?" (retrieved 2026-08-22) · retrieved 2026-08-22
- Cloze, "What causes a campaign to stop?" (retrieved 2026-08-22) · retrieved 2026-08-22
- Cloze, "Example Campaign: Get To Know Campaign" (retrieved 2026-08-22) · retrieved 2026-08-22
- Cloze, "Where can I see my email drafts?" (retrieved 2026-08-22) · retrieved 2026-08-22
- Cloze, "What can I ask Maia to do?" (retrieved 2026-08-22) · retrieved 2026-08-22
- Live auth posture check — anonymous MCP initialize to
https://api.cloze.com/v1/mcpreturned 401 with noWWW-Authenticateheader; RFC 9728 probes 404; authorization server metadata athttps://api.cloze.com/.well-known/oauth-authorization-serverreturned 200 (2026-08-22) · retrieved 2026-08-22 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Cloze support — <mailto:support@cloze.com> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Cloze
- Tools
- 20
- Domain
- api.cloze.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.