MCP24
Connect your AI assistant to CRM: masking, limits and a log
-
Rating
-
Installations6
-
DeveloperARTISMEDIA
MCP24 connects the AI assistant you already use (Claude, ChatGPT, Gemini CLI, Cursor and other MCP clients) to your CRM over the open Model Context Protocol, and puts a control layer between the assistant and your data. You always know what the AI can see and what it has done.
Control layer
- Access profiles. "Read only" by default: the assistant looks and changes nothing. "Manager" adds comments to CRM records but cannot delete. "Full access" allows deletion, but only after a human confirms it.
- Personal data masking, on by default. Phones, e-mails, addresses, tax and bank identifiers (VAT ID, IBAN, BIC/SWIFT and others) reach the AI as "[hidden]", including IBANs typed into free text. A real contact is revealed only by a separate action with a stated reason, and every reveal is logged.
- Data scope and caps. Limit the assistant to selected deal pipelines, cap records per response and changes per hour, so "show me everything" never becomes a database export.
- Deletion only with confirmation. The assistant gets a clear refusal, the employee gets a notification, and nothing is deleted until someone clicks Confirm on the MCP24 page.
- Journal inside your account. Data changes, reveals, policy refusals and confirmation requests are written to the "AI Actions (MCP24)" smart process, and stay with you after uninstalling. Contact and company cards get an "AI Actions" tab, deal cards an "AI Actions" button.
- Kill switch and revocation. One switch disables all assistants; any connection is revoked in one click.
What the assistant can do: find contacts, companies, deals and leads by part of a name, open a record, list deals by pipeline, stage, responsible person, amount and inactivity, read timeline comments, add a comment, and delete a record with confirmation. There is no "call any API method" tool that could bypass the rules.
Connect in a minute: open MCP24, copy the server address into your AI client and confirm with a 6-character code valid for 10 minutes.
Your AI, GDPR in mind. MCP24 supplies no AI and no model keys. CRM data goes only to the AI provider you choose; we do not store it or train models on it. Servers are in Germany (EU).
Additional terms
- MCP24 is free of charge.
- You need your own AI assistant that supports remote MCP servers (OAuth). MCP24 does not provide AI models; the provider's plans are paid separately to that provider.
- Data requested by the assistant is passed to the AI provider you have chosen, which may process it outside the EEA. As controller, you are responsible for the agreements and the legal basis for this transfer; MCP24 gives you tools to minimise it (masking, scope, caps, journal).
- Names of people and companies are not masked: without them the assistant cannot find a client.
- CRM data is not stored on our servers; it is processed in memory within a single request. Our service log keeps only technical data (tool, record type and ID, time, result).
- The in-account journal is a smart process. If your plan has no smart processes or their limit is reached, the journal is not created; access profiles, masking, confirmation and the log on the MCP24 page still work.
- The current tool set covers CRM contacts, companies, deals and leads. Bitrix24 REST API limits apply.
