Guides
Connect your CRM to ChatGPT and Claude with MCP
Published November 12, 2026 · 8 min read
More and more teams keep an AI assistant open all day to draft, summarise or prepare meetings. The catch is that the assistant knows nothing about your customers. You copy and paste data from the CRM into the chat, and every time you do it you lose time and move information out of its proper place.
An MCP connector fixes that: the assistant queries your CRM directly, with your user and your permissions. This guide explains MCP in plain language, how it connects to ChatGPT, Claude and other tools, what you can ask and what to check so you do it safely.
Key takeaways
- MCP (Model Context Protocol) is an open standard that lets an AI assistant use outside tools, such as your CRM.
- With an MCP connector, ChatGPT or Claude can search contacts, read deals or create tasks without you copying anything.
- What matters most is the permission model: the assistant should act as you, seeing and doing no more than you can.
- Prefer connectors with no tools to send messages or delete data, and check which changes are logged.
- Revoke access when you stop using it, as you would with an API key.
What is MCP and what is it for?
MCP stands for Model Context Protocol, an open protocol that describes how an AI assistant discovers and uses tools from other systems. Instead of every assistant building its own integration with every app, the app publishes an MCP server with a list of tools ("search contacts", "create task"...) and the assistant calls them when it needs to.
For you the difference is practical: you type "which deals over €5,000 are still open in the proposal stage?" and the assistant checks the CRM, instead of making up an answer or asking you to paste a table.
What can you ask the assistant?
Some examples that work well with a connected CRM:
- "Summarise Ana Garcia's history before my 12 o'clock call: emails, notes and deals."
- "Which open deals have had no activity in the last two weeks?"
- "Create a task for tomorrow: call Northside Workshops to go over the quote."
- "Add a note to this contact with what we discussed in the meeting."
- "Move the Southbuild deal to the negotiation stage."
- "Which invoices does this customer still have outstanding?"
The assistant combines what it reads from the CRM with its writing skills: for example, it drafts a follow-up email based on the history. Sending it is still up to you.
How does each assistant connect?
The process varies by tool, but it follows two patterns:
| Client | How it connects | Credential |
|---|---|---|
| Claude (web and desktop) | Custom connector with the MCP server URL | You sign in to the CRM and approve access (OAuth) |
| ChatGPT | Connector in developer mode with the server URL | You sign in when prompted (OAuth) |
| Claude Code | Command to add an HTTP MCP server | API key in the header |
| Cursor and other MCP clients | Remote HTTP MCP server | API key in the header |
With OAuth, the assistant acts as the user who approved access: with their role, their permissions and only the records they can see. With an API key, the tools on offer depend on that key's permissions.
Is it safe to connect a CRM to an AI assistant?
It depends on how the connector is built. Before you turn it on, check these points:
- Does it act with your permissions? If a salesperson only sees their own contacts in the CRM, an assistant connected with their user should not see more.
- What can it change? Reading and creating records is reasonable. Sending emails or messages, starting automations or deleting data from a chat is another matter.
- Is there a log? Every change made by the assistant should land in the audit log.
- Can you revoke it? You should be able to see which assistants have access and remove it in one click.
- Which data leaves? Whatever the assistant reads goes through the AI provider. Check your provider's data terms and your own internal policy.
- How long does access last? Tokens should expire and rotate, not live forever.
One important nuance: creating a contact or moving a deal from the assistant is the same as doing it by hand. If you have automations triggered by those events, they will fire just the same.
Does MCP replace the API?
No. The REST API is still the way to build stable integrations between systems: syncing an ERP, a custom shop or a form. MCP is designed for a person working conversationally with their assistant. If you are weighing both, the CRM API integration guide explains when each fits.
Frequently asked questions
Do I need to code to use an MCP connector?
Not for ChatGPT or Claude: you add the connector URL in their settings and sign in. For Claude Code or Cursor you paste a command or a config with your API key.
Can the assistant email my customers?
In Flowgration, no. The connector has no tools to send email, SMS or WhatsApp, start journeys or delete data. It can help you draft, but you send from the CRM.
Can it read the shared inbox?
Only when you connect with sign-in (OAuth), and only for the mailboxes you have access to. With an API key, the inbox tools are not available. Reading a conversation from the assistant does not mark it as read.
Does it count towards my plan limits?
Yes. In Flowgration, each tool call counts as one API request of your plan.
How do I remove an assistant's access?
The AI assistants (MCP) card in the API settings lists the authorised assistants and lets you revoke them. Changing your password or signing out everywhere also cuts access.
How Flowgration does it
Flowgration runs a remote MCP server at https://app.flowgration.com/mcp. In Claude and ChatGPT you add it as a custom connector and sign in; in Claude Code, Cursor and other clients you use an API key. The tools call the same routes as the app, so organisation isolation, roles, module and section permissions, "own records only" visibility and plan limits all apply in the same way.
It can search, read, create and update contacts; add notes; read pipelines and deals, create deals and move them between stages; list and create tasks; search and read inbox conversations (sign-in only); list invoices read-only and read the account summary. Every change is written to the audit log with the tool and field names, never their values.
The limits: it doesn't send messages, start journeys or delete anything; it offers tools only, with no resources or real-time notifications; and clients that use custom redirect schemes can't use OAuth, so they connect with an API key. If you want an assistant inside the app itself, see the AI assistant.
Build your WooCommerce CRM in 60 seconds
Flowgration turns your store's orders into a living CRM and runs email, SMS and WhatsApp on autopilot. Free up to 500 contacts.
Start free