New in saldiaCore: an AI assistant in the CRM – and an MCP server for Claude, Cursor & co.

You have been working with AI for a while. You ask Claude to draft a reply, have a concept reviewed or write code with Cursor. But the AI knows nothing about your customers. So you copy: the ticket in, the draft back out, the task into the CRM by hand.

In saldiaCore that back and forth is no longer needed. Since 20 October there are two new ways for AI to work with your business data: an AI assistant that sits right in the CRM next to every record, and an MCP server through which your own AI tools read and work in saldiaCore.

The key points

• AI assistant in the CRM: a panel next to tickets, tasks, deals, projects, companies and contacts. It reads along, writes drafts and only changes something once you confirm it.
• MCP server: Claude Code, Cursor and other AI tools that support MCP work directly in saldiaCore. They sign in with a personal token and have exactly your permissions.
• Control: a token can be limited to read-only. Over MCP, customer replies stay proposals, and every call is recorded in the audit log.

What is MCP?

MCP stands for Model Context Protocol. It is an open standard that Anthropic published in late 2024. It defines how an AI tool talks to a piece of software: the software offers tools, for example “read ticket” or “create task”, and the AI calls them when it needs them.

For you this means you no longer have to paste anything into the AI. It fetches the context from saldiaCore itself and puts the result where your team will find it.

The MCP server: saldiaCore as a tool for your AI

Once your AI tool is connected, you talk to it about your work the way you would to a colleague who has the CRM open:

• “What is currently going on with Muster AG?”
• “Which tickets are new since yesterday?”
• “Create a task for this ticket and log 30 minutes.”
• “Write a reply proposal for the customer.”

Four groups of tools are behind this:

• Fetching context. Company and project briefings, your open items, new tickets since yesterday, running timers and conversations.
• Work, not just read. Create tasks, tickets, to-dos and projects, log time, link records, write help articles and draft offers.
• The whole REST API. Whatever has no dedicated tool, the AI reaches through the saldiaCore REST API, for example offers with single positions, revisions and addenda.
• Code and knowledge. Connected Git repositories, the knowledge base and your guidelines for offers and writing style.

How we use it ourselves

We first built the MCP server for our own development team. When one of us works on a task with Claude Code, the AI first reads the task together with the linked ticket. So it knows what the customer reported before it touches a line of code. When the work is done, it writes a note on the task: which files changed, how it was tested and what is still open.

This way the knowledge does not stay in one person’s chat window. It sits where the whole team looks.

The AI assistant: right next to the record

Not everyone on the team works with Claude Code. That is why the same tools are also available right in saldiaCore: as a panel you open with ⌘ + period (or Ctrl + period). It docks next to tickets, tasks, deals, projects, companies and contacts, follows the record you have open and keeps the conversation history.

• It only acts after your click. Creating and assigning tasks, to-dos, tags, tickets, links, time entries and timers: every change shows up as a preview card first. It runs once you confirm.
• Reply proposals in tickets. The draft appears right above the reply editor, in the customer’s language, in your company’s writing style and signed with the full name. If you have already typed something, the assistant takes it into account.
• It reads documents. PDF, Word and PowerPoint files attached to a record feed into the answers, as do original mails that were cut off in the ticket.
• Offers by your playbook. The assistant builds offers from your product catalog and follows your sales playbook. You edit guidelines and writing style in the admin area.
• It knows your code. You connect Git repositories from GitHub or GitLab and map them to products. The assistant then answers technical ticket questions from the code.

What the AI may and may not do

An AI that can write to your CRM needs clear limits. These always apply:

• Your permissions, nothing more. MCP access runs on a personal API token. The AI sees and changes only what the person who owns the token is allowed to.
• Read-only if you want. A token can be limited to read-only. The AI can then look things up and summarise, but change nothing.
• No e-mails over MCP. No e-mail is sent through the MCP server. Replies stay proposals in the ticket, offers stay drafts. You review and send them in the CRM.
• Confirmation before every change. In the assistant you confirm every change on the preview card. Over MCP your AI tool takes on that step: by default, Claude Code asks before it calls a tool that writes.
• Limits built in. There is a daily limit on changes per person, and deleting through the API is switched off by default.
• Everything is logged. Every call is recorded in the audit log. You see what an AI read and changed in your CRM.

A note on data: whatever an AI tool reads over MCP is processed by the provider of that tool. So connect only tools you want to entrust with this data, and give a token write access only when you need it.

How to connect your AI tool

1. Switch on the module. The AI assistant and the MCP server belong to the “Internal AI assistant” module. It is off by default, and you activate it for your workspace.
2. Create a token. Under Admin → API Tokens an admin creates a personal token for you, with write access or read-only.
3. Add the server. In Claude Code, Cursor or another MCP-capable tool, enter the address of your saldiaCore followed by /mcp and store the token.

Your tool then lists the saldiaCore tools, and you can ask your first question.

Would you rather have a fixed routine that we set up for you? For Claude and ChatGPT there is also the connection via saldiaConnect.

Try it out

If you use saldiaCore: switch on the “Internal AI assistant” module, open a ticket and press ⌘ + period. Ask the assistant for a summary or a reply proposal. If you work with Claude Code or Cursor, have a token created afterwards and connect the MCP server.

If you do not use saldiaCore yet: the saldiaCore product page shows all modules at a glance, including the AI assistant with MCP. How AI has found its way into the CRM since the summer is covered in our posts on the Focus module and on the search that understands what you mean.

Frequently asked questions

What is the MCP server in saldiaCore?

The MCP server is an interface based on the open Model Context Protocol. Through it, AI tools such as Claude Code or Cursor work directly in saldiaCore: they read tickets, projects, offers and contacts, create tasks, log time and draft offers.

Which AI tools can I connect to saldiaCore?

Claude Code, Cursor and other tools that support MCP and sign in with an API token. For fixed routines with Claude or ChatGPT there is also the connection via saldiaConnect, which our team sets up for you.

Can the AI send e-mails to my customers over MCP?

No. No e-mail is sent through the MCP server. Customer replies stay proposals in the ticket, and offers stay drafts. You review and send them yourself in the CRM.

Can I limit access to read-only?

Yes. Access runs on a personal API token with exactly the permissions of the person who owns it. It can be limited to read-only when it is created. Every call is recorded in the audit log.

What is the difference between the AI assistant and the MCP server?

The AI assistant is a panel right inside saldiaCore, for everyone on the team. The MCP server opens the same tools to external AI tools such as Claude Code or Cursor. Both belong to the “Internal AI assistant” module.

What does the AI assistant cost?

Like every AI feature in saldiaCore, the assistant runs on the credit system: a monthly quota plus an optional prepaid balance, visible in the workspace at any time.