CRM · Twenty + Claude
Twenty MCP with Claude: Keep Your Open-Source CRM Up to Date Automatically
The short answer
Claude works with Twenty through the Model Context Protocol (MCP), a secure standard that lets Claude read and act inside the tool. Once connected with an API key, Claude can create and update contacts, manage deals and pipelines, log notes and activities, and run CRM searches and reports from natural-language instructions, within permissions you set.
What is Twenty?
Twenty is an open-source customer relationship management (CRM) system. It helps businesses track their contacts, companies, sales deals, pipelines and day-to-day activities in one place. Sales teams use it to follow leads and close deals, while account managers use it to keep customer history organised. Because it is open source, many organisations choose it for flexibility and control over their customer data.
How Claude connects to Twenty through MCP
The Model Context Protocol is an open standard that works like a universal adapter between Claude and other software. It lets Claude use a tool securely, reading information and taking actions, with permissions the organisation controls. For Twenty, the connection is set up with an API key so that Claude only reaches the parts of the CRM you allow.
Once connected, Claude can look up contacts and companies, check the stage of a deal, review recent activity, and create or update records when asked. It can also log call notes, add follow-up tasks and run searches or summary reports in everyday language, such as asking which deals have been idle for two weeks.
Permissions and approvals keep people in charge. We typically give the connection least-privilege access, so it cannot do more than the job requires. Consequential actions, such as changing a deal value or moving a large account to a new owner, can be routed for human approval first, and every action is recorded in an audit log.
What you can automate
Logging meeting notes after sales calls
After a call, a sales representative can give Claude a short summary of what was discussed. Claude records the note against the right contact and company in Twenty and sets a follow-up task with a date. Representatives spend less time on admin and more time with prospects, and nothing important is lost between calls.
Keeping contacts clean and up to date
Contact details change often when people move roles or companies. Claude can search for duplicate records, flag outdated entries for review and update fields once a person confirms the change. This keeps the CRM reliable for marketing and sales, which depend on accurate data.
Moving deals through the pipeline
When a prospect agrees to a proposal, a team member can ask Claude to move the deal to the next stage and record the expected close date. Claude makes the change in Twenty and summarises what was updated, so managers always see a current view of the pipeline.
Weekly pipeline and activity reports
Sales managers often spend hours assembling reports by hand. Claude can run CRM searches and produce a plain-language summary of open deals, win rates by stage and activity levels per representative. The manager reviews the summary and decides what to act on.
Account follow-up for customer success
Customer success teams can ask Claude to list accounts that have had no logged activity for a set period. Claude then drafts follow-up tasks and notes for each account owner, helping renewals and upsell opportunities are not missed.
An end-to-end workflow: Turning a won proposal into an onboarding request
TriggerA sales representative tells Claude that a prospect has signed a proposal.
Claude finds the contact and company record in Twenty and confirms the deal.
Claude moves the deal to the Won stage and records the signed value and close date, after the representative approves the change.
Claude logs a note summarising the agreed terms and the key contacts involved.
Claude creates a new onboarding request in the company's ticketing system and links it to the Twenty record.
Claude notifies the customer success lead in Microsoft 365 Teams with the account summary and onboarding date.
OutcomeOnboarding starts within hours rather than days. The handover is documented in the CRM, the operations team has what it needs, and the sales representative is free to pursue the next opportunity.
How we set it up
Free automation audit
We review how your sales, account and support teams use Twenty today and identify the workflows worth automating first. There is no charge for this session.
Secure connection with an API key
We create a dedicated API key in Twenty with least-privilege access and connect Claude to the CRM through an MCP server. Access is limited to the objects and actions your workflows need.
Workflow design across your systems
We design the end-to-end workflow, linking Twenty with your other systems such as Microsoft 365, your ERP or ticketing tool. Approval points are set for actions that carry financial or customer risk.
Testing and launch with monitoring
We test the workflows against real past cases, then launch with monitoring dashboards and audit logs so you can see every action Claude takes.
Team training and handover
We train your sales, operations and IT staff on how to use the workflows, how to approve actions and how to review the logs. We also leave clear documentation for ongoing support.
Who benefits
- Sales representatives
- Less time on data entry and more time with prospects, with notes and follow-ups recorded automatically.
- Sales managers
- Faster, plain-language pipeline reports that show where deals are stuck and where to focus coaching.
- Customer success leads
- Early warning on accounts with no recent activity, so renewals and upsell chances are not missed.
- IT and operations heads
- Controlled, auditable access to the CRM, with clear permissions and a record of every automated action.
Security and control
- Least-privilege API key access, limited to the objects and actions each workflow needs.
- Human approval for consequential changes such as deal values, ownership transfers and bulk updates.
- Complete audit logs of every action Claude takes in Twenty, available for review.
- Testing against real past cases before launch, with monitoring once the workflow is live.
- Regular review of permissions, so access keeps matching current job roles.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can run this workflow with data handling aligned to their own privacy requirements. Businesses in India must meet the Digital Personal Data Protection Act, 2023, and organisations in the UAE and Saudi Arabia must follow their local data protection laws. We choose the hosting region for your custom applications to help meet these requirements, whether in 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 the Twenty MCP server do?
The Twenty MCP server is the bridge that lets Claude and other AI agents use your CRM securely. It makes standard actions available to Claude, such as finding contacts, creating records, updating deal stages, logging activities and running searches. Each action happens only within the permissions you have granted, so the server acts as a controlled gateway rather than open access.
Is it secure to connect Claude to Twenty?
It can be, when set up carefully. We use a dedicated API key with least-privilege access, restrict it to the objects each workflow needs, require approval for important changes and keep full audit logs. Security also depends on how your team manages keys and reviews access, which we cover during setup and training.
What can Claude actually do in Twenty?
Once connected, Claude can create and update contacts, manage deals and pipelines, log notes and activities, and run CRM searches and reports based on natural-language requests. For example, a manager can ask which deals have not moved in thirty days, and Claude will find them and summarise the results for review.
How long does setup take?
Simple connections can be running within a few days, while multi-step workflows across several systems usually take longer. The timeline depends on how many workflows you want, how clean your CRM data is and how many approval steps you need. The free automation audit gives a clear estimate before any work begins.
What permissions or plan do I need?
Generally, you need an account in Twenty that allows you to create an API key, and a role with permission to access the records you want automated. The exact access depends on how your Twenty workspace is set up. We confirm the requirements during the free audit and recommend the narrowest permissions that still support your workflows.