Which AI assistants work with the Zircon CRM MCP server?

Claude (web, desktop and mobile), Claude Code, Cursor, VS Code (Copilot agent mode), Codex CLI, Gemini CLI, Windsurf and n8n. The Connect page has step-by-step instructions and copy-ready configuration for each. Other clients can connect too, as long as they support the Streamable HTTP transport and a bearer token.

How long does an AI assistant stay signed in to Zircon CRM?

With an OAuth connection, the access token lasts 60 minutes by default and renews automatically, and the sign-in stays valid for 60 days by default. A staff member with the Manage permission sets both. If a renewal token is ever reused, which suggests it leaked, the whole connection is revoked at once; a personal token is valid until the expiry chosen when it was created.

Can an AI assistant take irreversible actions in Zircon CRM?

Only if you allow it. Only a connection that was given the Delete permission at approval or token creation can delete anything, and even then only tasks, ideas, events and to-dos. Tools that e-mail customers, such as a ticket reply, are flagged, and the assistant is instructed to ask before using them. That is not an enforced step, so if you want to be certain, grant read-only access.

What is the difference between MCP and the REST API in Zircon CRM?

MCP is made for AI assistants: it runs as a real staff member, with that person's permissions, and any staff member with the MCP permission can connect. The REST API is for websites, apps and BI tools, using a separate API user that an administrator creates. Invoices and credit notes are written through the REST API; over MCP, invoices are read-only.

How do I cut off an AI connection straight away?

In Zircon CRM, revoking a token or disconnecting an application from the token list takes effect immediately. A staff member with the Manage permission can switch off an area for everyone, stop the server, or revoke every token in one step. Requests with a revoked token are refused with a clear message.

Zircon CRM / AI & integrations

Runs in the browser · HU / EN / DE

MCP server: your AI assistant works with your permissions

Zircon CRM has a built-in MCP server, so Claude, Cursor, VS Code or Codex CLI work directly with your live data. The assistant searches, reads and writes as the signed-in staff member, with that person's permissions, and every call it makes is logged. Nothing has to be exported, pasted into a chat or typed in again.

Book a 20-minute demo All modules

86 tools in 12 areasOAuth 2.1 or personal tokensEvery call logged

In short

What does the Zircon CRM MCP server do?

The Model Context Protocol (MCP) is the open standard AI assistants use to talk to business systems. The Zircon CRM MCP server offers 86 tools in 12 areas, including customers, leads, projects, tasks and support tickets. The assistant always works with the permissions of the staff member who connected it, and every call is logged. It is built for teams that already use an AI assistant.

Sound familiar?

Your AI is clever, but it cannot see inside your systems.

If one of these rings true, AI still works next to your CRM, not inside it.

01
Copy out, paste back
A project manager copies the open tasks into a chat so the AI can rank them. By the time the answer is pasted back, two deadlines have already moved.
02
One key that sees everything
A developer put an admin key into an AI tool's settings. Nobody knows exactly what it can reach, or whether it ever expires.
03
Who changed the due date?
A task's date was different by Tuesday morning. There is no way to tell whether a colleague, a script or an AI tool touched it.
04
All or nothing
You either hand the AI tool the whole database or nothing at all. There is no middle step, such as read-only or calendar only.

What it does

What the Zircon CRM MCP server can do.

The tool list differs per staff member: the assistant only sees what that person's role can reach.

86 tools in 12 business areas

Customers and contacts, leads, projects and milestones, tasks, support tickets, knowledge base, calendar, to-dos, media library and Social Manager. Invoices and estimates are read-only: the assistant can tell you which invoice is overdue, but it does not issue new ones.

Sign in with your Zircon CRM account (OAuth 2.1)

Claude, Claude Code, Cursor and VS Code open the normal login, followed by an approval screen. There you choose what the assistant may do: Read (always included), Create and update, Delete, and which areas it may touch. There is no key to copy.

Personal tokens for the command line and automations

Codex CLI, Gemini CLI, n8n or your own script connect with a personal access token. You give each token a name, permissions, areas and an expiry: 30, 90 or 365 days, a custom date, or no expiry. The token is shown once, and the system stores only a one-way hash of it.

The staff member's role is the boundary

If a sales rep can only see their own leads, their assistant sees those leads plus public ones, nothing more. If support staff are limited to their own departments, so is the AI.

Activity log with filters and live mode

Every tool call is logged: time, tool, status (OK, Error, Denied), AI client, staff member and duration. Click a row to see the error message and the arguments that were sent. Live mode refreshes the list every five seconds.

Ready-made workflows

Four built-in prompts, which appear as slash commands in Claude Code: daily briefing, support ticket triage, a one-page customer brief and writing social posts. The daily briefing changes nothing. It ranks what needs attention and links to each record.

Setup steps for every client

The Connect page has a tab for each supported client, with numbered steps and copy-ready configuration that already contains your server address. A check button confirms that AI clients can find the login.

How it works

Connecting Claude to your CRM, step by step.

01
Copy the server address
On the Connect page of the MCP menu, open the Claude tab and copy the address.
02
Add it as a custom connector
In Claude, go to Settings → Connectors → Add custom connector, give the connection a name and paste the address.
03
Sign in and approve
Click Connect. The Zircon CRM login opens, then the approval screen. Keep or narrow the permissions and areas, then allow access.
04
Ask
"What is overdue for me today?" or "Summarise the open tickets of our largest customer." The connection works in Claude on the web, on desktop and on mobile.
05
Disconnect at any time
Under Access tokens, disconnecting a connected application signs the assistant out immediately.

Control

Admins stay in charge of AI access.

Two permission levels

A dedicated permission in staff roles governs MCP: Use (your own tokens, connections and activity) and Manage (everyone's tokens and activity, plus the settings). Staff with neither do not see the menu and cannot complete an approval.

Kill switches

You can turn off the whole server (tokens are kept), OAuth sign-in only, single areas for everyone, one token, or every token of every staff member in one step.

A limit per token

By default each token may make 120 calls per minute. The limit can be changed or switched off, so a runaway automation cannot overload the system.

Flagged tools when e-mail goes out

Tools that e-mail customers or reach outside the system carry a flag. On connection, the assistant is given the instruction to ask the user before such a step and before anything that cannot be undone.

Works with

Where the assistant does its work.

Customer managementthe assistant finds, creates and updates customers and contacts, and writes a one-page brief on any customer.
Task managementit creates tasks with checklists, adds comments and logs time against a task.
Helpdesk and ticketsit ranks tickets, writes internal notes, shows reply drafts and is instructed to ask before sending.
Social Managerfor ideas waiting in the AI queue, it writes the blog, LinkedIn, Instagram and Facebook posts and saves them back.
Roles and permissionsthe AI inherits the staff member's role, and the MCP permission is granted in that role.
REST APIfor classic system integrations, with a separate API user, where financial records can be written too.

Honestly

Good to know before you start.

You need a supported AI client and a system reachable over HTTPS. Some clients look for the login details at the root of the website; if nothing answers there, the Connect page shows the short configuration snippet that fixes it.
The AI assistant's subscription is your own, for example a Claude plan. Zircon CRM only hands over what the staff member's permissions and the token's settings allow.
Asking before sending an e-mail is an instruction the assistant receives on connection, not an enforced step. If a connection must never send anything, give it read-only access.
Invoices and estimates are read-only over MCP. You create invoices in the interface or through the REST API.
The activity log keeps entries for 30 days by default, and administrators set the retention period. A daily clean-up run by the server's scheduled job (cron) removes older entries.

Before you write

Fair questions. Straight answers.

01
Which AI assistants work with the Zircon CRM MCP server?
Claude (web, desktop and mobile), Claude Code, Cursor, VS Code (Copilot agent mode), Codex CLI, Gemini CLI, Windsurf and n8n. The Connect page has step-by-step instructions and copy-ready configuration for each. Other clients can connect too, as long as they support the Streamable HTTP transport and a bearer token.
02
How long does an AI assistant stay signed in to Zircon CRM?
With an OAuth connection, the access token lasts 60 minutes by default and renews automatically, and the sign-in stays valid for 60 days by default. A staff member with the Manage permission sets both. If a renewal token is ever reused, which suggests it leaked, the whole connection is revoked at once; a personal token is valid until the expiry chosen when it was created.
03
Can an AI assistant take irreversible actions in Zircon CRM?
Only if you allow it. Only a connection that was given the Delete permission at approval or token creation can delete anything, and even then only tasks, ideas, events and to-dos. Tools that e-mail customers, such as a ticket reply, are flagged, and the assistant is instructed to ask before using them. That is not an enforced step, so if you want to be certain, grant read-only access.
04
What is the difference between MCP and the REST API in Zircon CRM?
MCP is made for AI assistants: it runs as a real staff member, with that person's permissions, and any staff member with the MCP permission can connect. The REST API is for websites, apps and BI tools, using a separate API user that an administrator creates. Invoices and credit notes are written through the REST API; over MCP, invoices are read-only.
05
How do I cut off an AI connection straight away?
In Zircon CRM, revoking a token or disconnecting an application from the token list takes effect immediately. A staff member with the Manage permission can switch off an area for everyone, stop the server, or revoke every token in one step. Requests with a revoked token are refused with a clear message.

Let's talk.

The first call costs nothing
A human replies — not a bot

Bring the one question you would most like to ask an AI assistant about your own customers. In the demo we connect Claude live, walk through the approval screen, then look at the activity log together to see exactly what it did.

E-mail: hello@zircon.hu
Phone: +36 30 487 7979
Hours: Weekdays 9–17
Support: support@zircon.hu (existing clients)