CRM · Kommo + Claude
Kommo MCP with Claude: Automate Lead Follow-Ups and Pipeline Updates
The short answer
Claude works with Kommo through the Model Context Protocol, an open standard that acts as a secure adapter between the two. Once connected with OAuth sign-in and limited permissions, Claude can read leads and contacts, update pipeline stages, sync records and draft follow-ups from plain-language instructions, while your team approves consequential actions.
What is Kommo?
Kommo is a CRM platform used to manage leads, contacts and sales pipelines. It records customer conversations, moves deals through stages and helps teams organise who needs to be contacted next. Sales teams, account managers, marketing teams and small and mid-sized businesses use it to keep customer interactions organised and to automate routine workflows that would otherwise depend on manual data entry.
How Claude connects to Kommo 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 tool like Kommo. The organisation controls what Claude is allowed to see and do, and access is granted through the sign-in method Kommo supports, which is OAuth sign-in.
Once connected, Claude can typically read lead details, contact records and pipeline stages, and help update them. For example, it could summarise a lead's recent activity, suggest the next stage for a deal, or sync contact information from another system. Your team can ask for these things in ordinary language rather than navigating screens or building complex filters.
Permissions and approvals keep people in charge. Access is limited to the pipelines and actions you choose, following least-privilege principles. Consequential steps, such as changing deal values or sending customer messages, can require a person's approval before they happen. Activity is logged so you can review what Claude did and when.
What you can automate
Lead qualification summaries
Before a sales representative calls a prospect, Claude can review the lead's history in Kommo and produce a short summary of past conversations, open questions and likely interests. Representatives spend less time reading old notes and more time having useful conversations with buyers.
Pipeline hygiene and stage updates
Deals often sit in the wrong stage because nobody updated them after a meeting. Claude can review open deals, flag ones with no activity for a set period and propose stage changes for a manager to approve. This keeps pipeline reports reliable for leadership.
Automated follow-up drafting
When a prospect goes quiet, Claude can draft a follow-up message tailored to the stage and history of the deal. Staff review and send the message, and the follow-up is recorded against the lead so the whole team can see it.
Contact synchronisation
Customer details frequently differ between a CRM and other business systems. Claude can help match and update contact records based on rules you define, flagging duplicates or conflicts for a person to resolve rather than overwriting them silently.
Account manager briefings
Before a renewal or review meeting, Claude can gather the relevant contacts, open deals and recent interactions for an account manager. The briefing arrives in one place, saving preparation time and reducing the chance of missing an important detail.
An end-to-end workflow: Inbound enquiry to qualified opportunity
TriggerA new enquiry arrives from the website contact form and is recorded as a lead in Kommo.
Claude reads the new lead and checks Microsoft 365 for any earlier emails from the same contact.
Claude matches the contact to an existing record in Kommo or creates a new one with the agreed fields.
Claude suggests a pipeline stage and a first-contact task, based on the enquiry details and your qualification rules.
A sales lead reviews the suggestion and approves the stage change and task in Kommo.
Claude drafts a personalised first reply for the representative to review and send.
If there is no response after the agreed number of days, Claude proposes a follow-up for approval.
OutcomeEnquiries are qualified and routed faster, records stay consistent across Kommo and email, and representatives spend their time on conversations rather than data entry. Results vary by business, but many teams see quicker first responses.
How we set it up
Free automation audit
We review how leads, contacts and pipelines move through your business today and identify the workflows worth automating first, at no cost.
Secure connection
We connect Claude to Kommo using OAuth sign-in, granting only the permissions the agreed workflows need, and document exactly what access is in place.
Workflow design
We design the end-to-end process across Kommo and your other systems, such as Microsoft 365, your ERP or ticketing tool, and agree which actions need human approval.
Testing with real cases
We test the workflows against past leads and deals to check accuracy, adjust the rules and confirm that approvals behave as intended before anything goes live.
Launch, monitoring and training
We launch with audit logs and monitoring in place, then train your sales and operations teams on how to use, review and correct Claude's work.
Who benefits
- Sales directors
- More reliable pipeline reports, because deals are kept up to date with less manual effort.
- Sales representatives
- Faster access to lead histories and drafted follow-ups, leaving more time for customer conversations.
- Operations managers
- Consistent contact records across systems, with conflicts flagged for review rather than hidden.
- Account managers
- Ready-made briefings before renewals and reviews, so no important detail is missed.
Security and control
- Least-privilege access, limited to the pipelines and actions agreed in advance.
- OAuth sign-in, so no shared passwords are stored in the workflow.
- Human approval for consequential actions such as changing deal values or sending customer messages.
- Complete audit logs of what Claude read and changed, available for review.
- Regular checks of workflow accuracy against real cases after launch.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom are subject to data protection rules such as state privacy laws and the UK GDPR, and we design access to meet them. Businesses in India must comply with the Digital Personal Data Protection Act, 2023, while organisations in the UAE and Saudi Arabia follow their own national data protection laws. We choose the hosting region for any custom application to meet your requirements, whether India, the United States, the United Kingdom or the European Union.
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 Kommo's MCP server do?
Kommo's MCP server provides a standard way for AI agents and chatbots to work with Kommo data. In general terms, it lets Claude read leads and contacts, manage pipelines and automate follow-ups through natural-language requests. We connect Claude to Kommo using the sign-in method Kommo supports, and we limit access to what your workflows need.
Is connecting Claude to Kommo secure?
Security depends on how the connection is designed. We use OAuth sign-in, grant least-privilege permissions, require human approval for important actions and keep audit logs of all activity. Your customer data stays under your control, and we review the setup with your IT team before launch.
What can Claude do with Kommo once connected?
Typically, Claude can read lead and contact information, summarise deal histories, suggest or make pipeline stage updates, sync contact records and draft follow-up messages. The exact actions allowed are set during design, so you decide what Claude can do and what needs approval.
How long does setup take?
Timelines vary with the number of workflows and the systems involved. A focused project connecting Kommo to Claude for a small set of workflows is often completed in a few weeks, including testing and team training. We confirm a realistic timeline after the free automation audit.
Which Kommo plan or permissions are needed?
In general, you need an active Kommo account with a user who has permission to authorise integrations and access the pipelines involved. Which features are available depends on your current Kommo arrangement, so we check your account setup during the audit and advise on any changes needed.