Most SuiteCRM AI add-ons write text. This one runs the CRM.
If you searched for AI in SuiteCRM you found panels that summarise a record or draft an email inside the CRM screen. Useful, and a different thing. Here is the honest comparison.
| What it does | Where you use it | Writes to the CRM | Builds views | Model and key | Works on your phone | |
|---|---|---|---|---|---|---|
| SuiteMCP | Runs the CRM from a conversation: reads, writes, builds dashboards and boards from live records | Claude on web, desktop and phone | Yes, as the signed-in user, under your SuiteCRM roles | Yes, from any module including custom ones | Claude, on your own Claude plan; nothing to install on your server | Yes, the Claude app |
| In-CRM assistant add-ons (for example Suite Assistant, SuiteAI Insight) | Summaries, next-step suggestions and drafted emails inside SuiteCRM screens | A panel inside the SuiteCRM UI | Varies; mostly suggestions the user applies | No | Bring your own OpenAI, Gemini or local model key; installed on your server | Only through the SuiteCRM mobile view |
| ChatGPT email plugins | Drafts campaign and email text | The email composer | No | No | Your own OpenAI key | No |
| Automation platforms (Zapier, Make, n8n) | Trigger and action recipes between apps | A workflow builder | Yes, per recipe you build | No | You wire the model call yourself | No |
Descriptions of other products follow their public listings on the SuiteCRM Store and their own sites as of September 2026. Tell us if one is out of date and we will correct it.
Where the difference shows up
Where the work happens. An in-CRM add-on helps once you are already in the record. SuiteMCP works where your team already is: Claude, on the laptop or the phone, before the record is open. Most of the pain people describe is finding the record in the first place.
Writing back. Suggestions the user applies are still data entry. “BlueRiver agreed, mark it won, log the call” is three writes from one sentence, attributed to the person who said it.
Views. A board of cases by status, a chart of leads by source, a dashboard for the board meeting, built at the moment you ask and drawn from live records, on any module including the custom ones.
Keys and servers. Add-ons need a model key and code on your SuiteCRM server, which the next upgrade may break. SuiteMCP installs nothing there and runs on the Claude plan your team already has.
Where they win. If what you want is a summary or a drafted email inside the record screen for people who live in SuiteCRM all day, an in-CRM add-on does that well and costs an API key. Use both if you like.
Say it.
Done.
Every CRM your team already has, now something they will use.