Anthropic's Claude right inside saldiaCore: connect it yourself via the MCP server or get set-up AI workflows for long documents.
The most direct way for Claude to work with your data is the saldiaCore MCP server. Through the open Model Context Protocol you connect Claude Code and other MCP-capable clients with a personal API token from saldiaCore. Claude then reads tickets, tasks, projects, offers and contacts, creates tasks, logs time and drafts offers – always with exactly the permissions of the person who owns the token. A token can be limited to read-only, customer replies stay proposals, and every call lands in the audit log. The MCP server is part of the AI assistant in saldiaCore.
For fixed routines there is also the connection via our integration layer: it links Anthropic's Claude to your saldia setup, so that more complex text analysis, long documents and secure AI workflows happen right where your business data already lives. Tickets, CRM notes or HR documents from saldiaCore can be handed to Claude for summaries, drafts or structured evaluations, which you then feed back into your processes.
The connection is set up by the saldia team: together we define which content from saldiaCore goes to Claude and in what form the results come back. With saldiaTools you bundle recurring Claude routines as small, specialised helpers in one place. Support comes from Switzerland and in German and French – you don't build the connection yourself, you receive it cleanly configured and ready to use.
Claude Code works directly in saldiaCore
Your team opens a task from saldiaCore in Claude Code: through the MCP server, Claude reads the task together with the linked ticket and project briefing, makes the change in the code, then leaves a note with the changed files and logs the time if asked. Nobody has to copy content back and forth between CRM and editor.
Summarise long support tickets in saldiaCore
An SME with heavy ticket volume has tangled threads from the saldiaCore ticketing module summarised through the Claude connection. Your team grasps the gist of a long case at a glance instead of reading every reply – the saldia team sets up how the content is handed over.
Structured analysis of CRM data
The CRM in saldiaCore collects notes and correspondence about your customers. Through the Claude connection these texts can be turned into structured evaluations – such as recurring topics or open items per customer. Which saldiaCore fields feed in is something you define together with the saldia team.
Bundle Claude routines as saldiaTools helpers
Recurring tasks – like checking long documents against a fixed scheme – are stored as a specialised app in saldiaTools. Your team triggers a cleanly defined Claude routine with one click instead of rewriting it each time. The saldia team handles the setup.
In two ways. You connect Claude Code and other MCP-capable clients yourself through the saldiaCore MCP server – with a personal API token that has your permissions. Fixed routines, such as evaluating certain documents, are set up by the saldia team: we define with you which content from saldiaCore is handed to Claude and how the results flow back.
At the centre is saldiaCore as the source for ticketing, CRM and HR content. Our integration layer establishes the link to Claude, and saldiaTools lets you bundle recurring routines as specialised helpers.
With the MCP server, Claude sees exactly what the person who owns the token is allowed to see – with a read-only token Claude cannot change anything, and every call is in the audit log. With the connection set up by the saldia team, only the content you release goes to Claude, such as selected ticket threads, CRM notes or documents from saldiaCore.
The MCP server, yes: if the AI assistant is active in your saldiaCore, a personal token is created in the admin area under API tokens. You enter it together with your saldiaCore's MCP address in Claude Code or another MCP client. Fixed routines are set up for you by the saldia team – get in touch and we'll discuss your use case. Support comes from Switzerland and in German and French.
Want to connect Claude to saldiaCore? You set up the MCP server yourself with a personal token. For fixed routines, get in touch with the saldia team – we'll discuss your use case and set up the connection for you. Support from Switzerland, in German and French.
These saldia products work together with this integration.
Activate the integration directly in your saldia product's backend, or contact us if you need help.
