Claude Close connectorWhat Claude can do in your Close account.
The Claude Close connector exposes 55 tools: 22 read your CRM, 29 create, edit or delete, and 4 have no tool description. Here: what Claude pulls from leads and opportunities, what it can change or erase, the access scope you choose at sign-in, and who can switch it off.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for a sales team on Close
Answering a pipeline question in Close usually means a smart view, a filter and some scrolling. With the connector on, you ask Claude which opportunities are slipping this month. It searches leads, opportunities and activities itself, reads what matters and answers in the conversation, within the access you granted at sign-in.
Prepare a call without clicking around. lead_search finds the company, fetch_lead opens it, and activity_search lists recent calls and emails, newest first.
Log what came out of a meeting. create_contact adds the new stakeholder you met, and create_opportunity records the deal that just opened.
Keep the pipeline tidy. update_opportunity moves a deal, and find_opportunities surfaces the ones by status, owner or lead.
What the sheet does not tell you. Four entries on it have no tool description: three of them are the names Close gives to access scopes. Which tools Claude may use depends on the scope granted when you connect: read only, safe writes, or full writes including edits and deletions. Several deletions are permanent. And nothing runs on its own: no tool fires when a lead changes status. For that kind of background work, the Integrations hub gathers automation tools, which do a different job.
The vocabulary in one minute
Five words you will meet while connecting Close.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work on it while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude chooses the ones it needs on its own; the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use afterwards. Granted once per person, revocable the same way.
- Approval
- The confirmation Claude waits for before it goes through with something that changes the account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service.
Connect Close to Claude in three steps
- 01
Find Close in Claude
In Claude's settings, open Customize, then Connectors, and look for Close. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first; after that, each member connects individually.
- 02
Start the connection
Click Connect on its row. Close opens its own authorization page, where you pick the Close organization to grant. If the link breaks later, use Disconnect and connect again.
- 03
Read the authorization screen
Read the screen before you allow access. It is Close's screen, not Claude's, and it decides what the access covers, including the scope. You can take the access back later from the Close side too.
The 55 tools of the Claude Close connector
Close gives Claude 55 tools: 22 that read your account, 29 that change something in it, and 4 no official source describes.
Three groups: what Claude reads, what it changes in Close, and entries no official source describes as tools. Names stay exactly as Claude shows them.
- 22 read
- 29 write
- 4 not documented
What Claude reads (22)
22 toolsTwenty-two tools that search and open leads, deals, templates and settings without changing them.
activity_search
Searches the activities recorded across your organization and returns them in date order, the newest first. It is how Claude reconstructs what happened on an account.
fetch_contact
Opens an existing contact by its ID, with the details Close stores on that person. It needs that ID, so it comes after a search.
fetch_email_template
Retrieves a single email template by ID so Claude can read the exact wording your team uses.
fetch_lead_smart_view
Opens a smart view, which is Close's name for a saved search, by its ID, so Claude knows the exact filter behind it.
fetch_lead_status
Reads a single lead status by its ID. Claude uses it to translate an internal status reference into the label your team actually sees.
fetch_lead
Pulls up an existing lead, a company in Close's model, by its ID, with what Close holds on it. It is the core record behind contacts and deals.
fetch_opportunity_status
Looks up one opportunity status by ID, so Claude can name the stage a deal sits in rather than quote a code.
fetch_opportunity
Fetches a specific opportunity by its ID, with the deal information Close keeps on it.
fetch_pipeline_and_opportunity_statuses
Retrieves an opportunity pipeline by its ID, together with all the statuses that make it up.
fetch_sms_template
Opens a single SMS template by ID so Claude can go through the text word for word.
find_email_templates
Lists the email templates in your organization, or finds the ones that match what you describe.
find_lead_smart_views
Lists the smart views, Close's saved searches, available to you. Claude uses the list to point you to an existing view instead of rebuilding a filter.
find_lead_statuses
Lists or finds the lead statuses defined for your organization, with their labels.
find_opportunities
Searches opportunities by status (active, won or lost), by owner or by lead. Pipeline questions usually start with a filter like one of those three.
find_pipelines_and_opportunity_statuses
Lists every opportunity pipeline in the organization along with its statuses, so Claude sees the whole structure at once.
find_scheduling_links
Lists the scheduling links available to you and to your organization, so Claude can drop the right one into a reply.
find_sms_templates
Browses the SMS templates stored in Close, or looks up the ones matching a description.
find_workflows
Returns the workflows, which Close also calls sequences, so Claude can tell you which ones exist and what they are named.
lead_search
Runs a simple lead search and returns the initial set of results. For a quick lookup, it is the natural starting point before opening any single record.
org_info
Returns general information about your Close organization and about you as the connected user. It answers two questions at once: where Claude is working, and as whom.
org_users
Returns the active users of your organization, which lets Claude match an owner name to the right person.
paginate_search
Pages through a previous search to bring back the results beyond the first batch. It picks up a search already under way rather than starting one.
What Claude changes (29)
29 toolsTwenty-nine tools that create, edit or delete. Only one has a confirmation described by a source; the general rule below covers the rest.
create_address
Approval: see the ruleAttaches a new address to an existing lead.
create_contact
Approval: see the ruleCreates a new contact under an existing lead.
create_email_template
Approval: see the ruleSets up a new email template in your Close organization.
create_lead_status
Approval: see the ruleAdds a new lead status to your organization's list.
create_lead
Approval: see the ruleAdds a lead, which is a company in Close's model.
create_opportunity_status_tool
Approval: see the ruleIntroduces one more opportunity status, a stage a deal can sit in.
create_opportunity
Approval: see the ruleOpens a deal, called an opportunity in Close, on an existing lead.
create_pipeline
Approval: see the ruleSets up an additional opportunity pipeline for a distinct sales motion.
create_sms_template
Approval: see the ruleSaves a new SMS template in Close, ready for the texts your team sends.
create_workflow
Approval: see the ruleBuilds a workflow, Close's word for a sequence, and saves it in Draft status.
delete_address
Approval: see the ruleDeletes an address from an existing lead when it finds an exact match.
delete_contact
Approval: see the ruleDeletes an existing contact from Close for good.
delete_email_template
Approval: see the rulePermanently deletes an email template.
delete_lead_smart_view
Approval: see the rulePermanently deletes a smart view, one of your saved searches.
delete_lead_status
Approval: see the ruleRemoves a lead status from your organization for good.
delete_lead
Asks you firstWipes out a lead for good, along with everything under it: addresses, contacts, opportunities, tasks and activities.
delete_opportunity_status_tool
Approval: see the rulePermanently removes an opportunity status, a stage deals can sit in.
delete_opportunity
Approval: see the ruleErases an opportunity from Close, with no way back.
delete_pipeline
Approval: see the ruleTakes an opportunity pipeline out of Close permanently.
delete_sms_template
Approval: see the ruleDiscards an SMS template for good.
update_contact
Approval: see the ruleUpdates an existing contact's details.
update_email_template
Approval: see the ruleRevises an email template that already exists in Close.
update_lead_smart_view
Approval: see the ruleUpdates a smart view, one of the saved searches your team relies on.
update_lead_status
Approval: see the ruleChanges the label of an existing lead status.
update_lead
Approval: see the ruleChanges the company record itself, the lead.
update_opportunity_status_tool
Approval: see the ruleGives an opportunity status a new label.
update_opportunity
Approval: see the ruleEdits a deal record, what Close calls an opportunity.
update_pipeline
Approval: see the ruleAdjusts an opportunity pipeline that already exists.
update_sms_template
Approval: see the ruleRewrites an existing SMS template in Close.
Undocumented (4)
4 toolsThe directory publishes these four names, but no official source describes a tool behind them. We will not guess from a name.
mcp.read
This name appears on the directory sheet, yet no official source documents a tool behind it. Close's docs use the same name for an access scope, the read-only level you can pick at sign-in, which is not a tool description.
perform_search
Listed on the sheet, absent from Close's developer list of tools, which describes a search tool under a different name. No official source documents this exact name, so this page does not guess.
mcp.write_safe
No official source documents a tool with this name. In Close's documentation, the same label names the middle access level chosen when connecting; the page stops at that fact and treats the entry as undocumented.
mcp.write_destructive
The last of the four: the sheet prints the name, and Close's docs use it for the widest access level you can grant at sign-in. No official source documents a tool behind it.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account on your behalf. The request shows up in the conversation right when it matters.
With 29 tools that create, edit or delete, that rule matters here. Close adds its own layer: the scope you grant at sign-in decides which of those tools exist for Claude at all. On Team or Enterprise, owners decide whether members may let some actions through without being asked, and they can cap what the connector may do for everyone. Claude works with your Close permissions and nothing more, whatever the scope.
Which Claude plans it runs on
Of the 819 sheets in the official directory, none shows plan availability. The connector-by-connector answer is not published anywhere.
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 enables the connector for the organization before each member can connect. Close's own help page says something narrower, set against this rule in the limits section. For the current state, check the connector's sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you; nothing starts when a lead changes status or an email arrives.
The tool list is an observed floor, not a promise: an admin can open actions no public sheet shows. The partner badge is not a security audit either, and Anthropic writes it on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as described. Connect only what comes from a publisher you trust. Only Close documents this connector; no Claude help article covers it. For a lighter CRM connector, compare with the Claude activecampaign connector.
Which Claude plans can use the Close connector?
- Claude help center, general rule for connectors ↗September 2026Remote connectors are available to all users; on Team and Enterprise, an Owner or Primary Owner must enable each one first.
- Close's help article ↗September 30, 2026The publisher says the connectors library requires a paid Claude plan, then adds that the Claude desktop app can reach Close's server on any plan.
What this page followsThe two texts do not cover the same ground: Anthropic's rule applies to every connector, while Close speaks about its own, and even nuances itself. Neither is marked outdated, and neither settles it for your account: check the connector's directory sheet from your own Claude account.
Need help connecting Close to Claude?
A person reads every message.
