CRM · Close + Claude
Close MCP with Claude: Automate Sales Follow-Ups and Lead Management
The short answer
Claude works with Close through the Model Context Protocol (MCP), a secure connection that lets Claude read lead and activity records and carry out approved actions. Your sales team can ask for updates, draft and send follow-up emails, and log calls in everyday language, while you control which actions Claude may take.
What is Close?
Close is a customer relationship management platform built for sales teams. It brings calling, email automation and predictive dialers into one place, so reps can work leads without switching between tools. Sales managers, business development teams and small and mid-sized companies use it to track deals, manage outreach and measure how their sales activity performs.
How Claude connects to Close through MCP
The Model Context Protocol, or MCP, is an open standard that lets Claude use other software securely. Think of it as a universal adapter between Claude and a business tool. It sets out what Claude can see and do, and your organisation controls those permissions.
Once connected to Close, Claude can read leads, contacts, notes and activity history. It can search for records, summarise an account before a call, send emails and create follow-up tasks, as typically configured. Requests can be made in natural language, such as asking for every lead that has not been contacted this week.
Permissions and approvals keep people in charge. Access is limited to what each role needs, and consequential actions such as bulk emails can require a person to approve them first. Every action is recorded, so managers can see what Claude did and why.
What you can automate
Pre-call lead briefings
Before a rep dials a prospect, Claude pulls together the account history, previous calls, open notes and recent emails into a short summary. Reps walk into conversations prepared, without spending ten minutes searching through records. Managers can ask for briefings across a whole territory before a weekly pipeline review.
Automated follow-up sequences
After a call or meeting, Claude can draft a follow-up email that reflects what was discussed and suggest the next task. The rep reviews and approves the draft before it is sent. This keeps prospects moving through the pipeline and reduces leads that fall through the cracks after a busy week.
Stale lead clean-up
Claude can identify leads that have had no activity for a set period and list them by owner. It can suggest which should be re-engaged, closed or reassigned. Sales operations teams use this to keep the CRM accurate, which makes forecasts more reliable.
Activity logging from natural language
Reps can tell Claude what happened in a meeting, and Claude can record the call outcome, note and next step against the correct contact. This saves time on admin and means managers see up-to-date activity without chasing reps for updates.
Weekly pipeline reporting
Managers can ask Claude for a summary of calls made, emails sent, meetings booked and deals moved between stages during the week. Claude compiles the figures and highlights unusual changes. The report can then be shared with leadership in the format the business already uses.
An end-to-end workflow: Inbound enquiry to booked demo
TriggerA new enquiry arrives from the website contact form and is recorded as a lead in Close.
Claude reads the enquiry and checks Close for any existing contact or company record.
Claude drafts a personalised first-response email based on the enquiry details and the sales team's standard tone, and places it in the rep's approval queue.
The rep reviews and approves the email, which is sent from Close.
Claude creates a follow-up task for two working days later and, if the prospect has not replied, drafts a reminder.
When the prospect books a meeting in Microsoft 365 calendar, Claude updates the lead stage in Close and attaches the meeting details to the record.
OutcomeTypically, enquiries receive a faster and more consistent first response, and fewer leads are lost between the form and the first meeting. Reps spend more time on conversations and less on admin.
How we set it up
Free automation audit
We review how your sales team uses Close today, where leads are lost, and which tasks take the most time. You receive a short list of workflows worth automating, at no cost and with no obligation.
Secure API key connection
Close supports API key sign-in. We create a dedicated key for the integration with the access it needs, stored securely, and connect Claude to Close through an MCP server or a direct API connection, depending on your requirements.
Workflow design and permissions
We design the end-to-end workflow across Close and your other systems, such as Microsoft 365, your ERP or ticketing tool. Each action is assigned the least access needed, and approval steps are set for anything that contacts customers.
Testing against real cases
We test the workflow using past leads and real scenarios, check the drafts and updates Claude produces, and adjust the instructions until your team is satisfied with the quality.
Launch, monitoring and training
We launch with audit logs and monitoring in place, train your sales and operations staff on how to use Claude with Close, and review performance with you after the first few weeks.
Who benefits
- Sales representatives
- Spend less time on admin and more time with prospects, with each call prepared by a clear summary of the account.
- Sales managers
- Get accurate activity reports and pipeline summaries without asking reps for manual updates.
- Sales operations leads
- Keep CRM records clean and consistent, which supports more reliable forecasting.
- Business owners and directors
- Build a repeatable sales process that does not depend on any one person remembering every follow-up.
Security and control
- Access is limited to the permissions each user and integration needs, and the API key is stored securely.
- Consequential actions, such as sending customer emails or bulk updates, can require human approval before they run.
- Every action Claude takes in Close is recorded in audit logs so it can be reviewed.
- Test environments and staged rollouts reduce the risk of errors reaching live customer records.
- Regular reviews check that permissions and workflows still match your sales policies.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can use Claude with Close under their own data protection frameworks, with hosting chosen to meet their requirements. Indian businesses must align with the Digital Personal Data Protection Act, 2023, and we configure access and retention accordingly. Companies in the UAE and Saudi Arabia must follow local data protection laws, and we select a hosting region that suits those obligations. We confirm the right setup for your region during the audit.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Close MCP server do?
The Close MCP server is the bridge that lets an AI assistant such as Claude read and work with Close data. It presents Close's lead, contact and activity information in a form Claude understands, and it allows approved actions such as creating tasks or sending emails. It can be used alongside a direct API connection, depending on what your workflow needs.
Is connecting Claude to Close secure?
The connection uses an API key that is stored securely and given only the access it needs. Permissions are limited, consequential actions can require human approval, and activity is logged. We also test the setup before launch so you can see exactly what Claude can and cannot do.
What can Claude do with Close once connected?
Typically, Claude can find and summarise leads and contacts, review activity history, draft and send emails, log calls and notes, create follow-up tasks and produce pipeline reports. Requests are made in natural language. The exact actions depend on the permissions you approve.
How long does setup take?
A focused integration with a clear workflow often takes a few weeks, from the free audit through testing to launch. More complex setups that involve several systems take longer. We agree on a timeline during the audit so you know what to expect.
What access or plan do I need in Close?
You need a Close account with an API key that your administrator can generate. The access level granted to that key determines what Claude can do, so we recommend a dedicated key with only the permissions the workflow requires. We confirm the details for your account during the audit.