Claude Cloze connectorWhat Claude can do in your Cloze account.
The Claude Cloze connector exposes 20 tools. 5 of them read your contacts, timelines and deals, 6 change something in your account, and 9 are documented nowhere. Below: what Claude finds, what it records for you, and what Cloze still calls a beta.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for an agent juggling clients
Relationship work in Cloze means looking people up, logging what happened and remembering the next step. With the connector, you say it in one sentence: Claude searches your contacts, reads their timeline, adds the note or the to-do, and saves an email draft for you to review in Cloze.
Get ready for a call in seconds. person_find locates the contact by name, email or phone, and timeline shows your recent interactions with them.
Capture a new lead on the spot. After an open house, person_add records the new contact, add_note logs what they are looking for, and add_todo sets the follow-up.
Write a first message in your voice. about_me pulls your own profile and bio, then save_draft stores a personalized email in your Cloze drafts, unsent.
Now what the connector does not do. Nine of its twenty tools are described by no source, including one whose name suggests adding projects. Cloze documents tools for Canva, Cloud CMA and HomeSpotter, but they are not on the directory sheet. And Cloze calls the whole server an experimental beta. Nothing runs by itself either: for a sequence that fires when a deal changes stage, an automation tool is the right job, and the Cloze Make integration page covers it.
The vocabulary in one minute
Five words you will meet while plugging Cloze into Claude.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in it while answering you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs by itself; the directory lists each by name.
- Authorization
- The sign-in screen of the service itself, where you hand Claude its access. Granted once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it goes through with something that changes your account, shown right in the chat.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service.
Plug Cloze into Claude in three steps
- 01
Find Cloze in Claude
In Claude's settings, open Customize, then Connectors, and look for Cloze in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on first so each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Cloze in the window that Cloze opens itself. If the link ever breaks later on, use Disconnect and then plug it back in.
- 03
Read the authorization screen
Read the authorization screen before you accept. It belongs to Cloze, not to Claude, and it is what decides what the access covers. You can also withdraw that access later from your Cloze account.
The 20 tools, sorted by what they do
Cloze gives Claude 20 tools: 5 that read your account, 6 that change something in it, and 9 no official source describes.
Three groups: what Claude reads, what it changes, and what no official source describes. Tool names stay exactly as Claude shows them.
- 5 read
- 6 write
- 9 not documented
What Claude reads (5)
5 toolsFive tools that look up people, timelines, deals and counts without touching them.
about_me
Returns your own Cloze profile and bio, which Claude uses to personalize introductions in your style and experience.
person_count
Counts how many contacts match criteria such as clients, sellers or a tag, which Cloze suggests checking before any bulk operation.
person_find
Searches your Cloze database for someone using a name, email, phone number or any other detail you remember, so a partial memory is enough.
project_find
Looks up active or past deals and listings by address, status or tag, so you land on the right project quickly.
timeline
Shows the recent history with a contact, so Claude can tell you what happened lately before you pick up the phone.
What Claude changes (6)
6 toolsSix tools that record something in your Cloze account. No source spells out their confirmation, so the general rule below applies.
add_note
Approval: see the ruleAdds a note to a contact's timeline to capture details from a call, a meeting or an update, keeping the history complete.
add_todo
Approval: see the rulePuts a to-do on a contact so the next step does not depend on your memory; Cloze's own example is a call about a contract renewal.
person_add
Approval: see the ruleCreates a new contact in Cloze with a name, phone number and email, which Cloze pitches for capturing new leads on the fly.
person_change
Approval: see the ruleUpdates one or many people at once: contact details, tags, segments or custom fields, either individually or in bulk.
project_change
Approval: see the ruleUpdates an existing listing or deal: status, price or tags, to keep project details current and organized.
save_draft
Approval: see the ruleWrites a personalized email and saves it to your drafts in Cloze, so you can review, edit and send it yourself when ready.
Not documented (9)
9 toolsThe directory publishes these nine names and nothing else. No official text says what they do, and this page will not guess from a name.
full_content
The directory lists this name and nothing more. Cloze's help articles never mention it, and no Claude page does either, so this page adds nothing about what it covers.
person_find_steps
Only its name shows on the directory sheet. No official source describes it, and reading a role into the name would be a guess, which this page does not make.
person_tags
Listed by the directory without a single line of explanation. Neither Cloze's examples article nor Claude's help center says what it returns or when Claude would call it.
person_views
Cloze's list of examples skips this name entirely, and no other source picks it up. With nothing written about it, this page stays silent on its effect.
project_add
Nothing in the sources goes beyond its listing in the directory. Its name sits next to documented tools, yet no sentence from Cloze or Anthropic says what it does, so this page does not either.
project_count
The directory shows this tool, Cloze's articles do not describe it, and Claude's documentation has no page for this connector. There is simply no text to rely on.
project_find_steps
This name appears in the tool list with no accompanying text from any official source. We read Cloze's two help articles and found no mention of it at all.
project_tags
A listed name that no documentation covers. Cloze names a dozen tools in its examples, but not this one, and nothing on Claude's side fills the gap.
project_views
Published by the directory as a bare name. No official page describes this tool, so its role remains unknown here and on every source we could read for Cloze.
What Claude asks before it acts
By default, Claude stops and asks you before any action it takes on an account on your behalf. The request shows up in the conversation, at the moment it matters.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked every time. They can also limit what a connector may do for the whole organization, for instance keeping reading open and closing writing. That setting applies to everyone and nobody gets around it from their own account. Finally, Claude works with your rights and nothing beyond: a contact you cannot see in Cloze stays out of its reach too.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. The answer per connector is published nowhere, and that is a real hole in the catalog rather than a gap in our reading.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each sign in. Cloze's own article states a narrower condition, set against this rule in the limits section. For the live state of this one, go to Cloze's sheet in the official directory, the only place that shows it.
Where the Claude Cloze connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a lead arrives or a deal changes stage.
This connector is documented only by its publisher: neither Claude's help center nor Anthropic's developer docs cover it, so the facts here come from the directory sheet and two Cloze help articles, one updated in September 2026. Those articles describe eleven tools by example and leave nine names unexplained. The partner badge is not a security audit, and Anthropic states on every sheet that it does not control which tools a publisher exposes. The Integrations hub gathers the automation families.
Which Claude plans can use this connector?
- Claude help center, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise an Owner has to enable each one first.
- Cloze help article ↗September 2026Lists Claude Desktop on the Pro plan or above, and says the custom connector option needs Pro or above.
What this page followsThe two do not describe the same path: Cloze's article walks through adding a custom connector in Claude Desktop, while Anthropic's rule covers directory connectors. Neither is marked outdated. Check the directory sheet on your own account before relying on either.
Need help connecting Cloze to Claude?
A person reads every message.
