MCP server · UTIO API
Connect Claude or another AI to your account with our MCP server
Your AI assistant finds contacts, moves deals, drafts quotes or sends a WhatsApp message in your UTIO account, with the permissions of the key you give it and nothing more. It works with Claude Code, Cursor and MCP clients that let you add an authorization header.
In short
UTIO's MCP server exposes 24 tools on your account: CRM, sales, messages and call campaigns. Each one uses the same key, permissions, validation, spending cap and idempotency as the API.
- It authenticates with an "Authorization: Bearer" header and a channel key. That works with Claude Code, Cursor and MCP clients that accept a header; the claude.ai and ChatGPT connectors require OAuth and don't work today.
- Each key only sees the tools it allows: without the WhatsApp permission, the assistant doesn't even see that tool.
- No price of its own: whatever you do over MCP is charged as if done from the panel, from your balance. Reading the CRM or sales data uses nothing.
- Creating keys requires the AI module, which we switch on for you. It isn't part of the 14-day trial.
What your assistant can do: 24 tools
Each tool is a door into the UTIO API, with the same rules. These, and only these.
-
CRM
Search, view and save contacts; view the history and add notes; assign an owner; view pipelines and move stages; open and close deals; view, create and change the status of tasks.
-
Messages
Send a WhatsApp message or an email. The tool itself tells the assistant to confirm with you before sending.
-
Sales
View products, quotes and invoices; create a quote or an invoice; issue an invoice; turn a quote into an invoice and change its status.
-
Call campaigns
Add contacts to a campaign and see the contacts it has.
-
Only what the key allows
The tool list is filtered by the key's permissions. If the assistant tries something it isn't allowed to do, it gets a readable error.
-
A retry never runs twice
If the connection drops and the assistant repeats the command, it isn't executed twice: every call carries its own idempotency key.
-
Spending cap and rate limit
Each key takes a cap in euros; once it's reached, the key stops working until you raise it. Plus a limit of 120 requests per minute per key.
How to connect
Four steps, with the names you'll see in the panel.
- Ask us to switch on the AI module in your account: without it you can't create API keys.
- In the panel, go to Settings → Developers → API keys.
- Click "Create key" and give it a name. Untick the AI permissions (they come ticked, and a key can't mix both types) and tick the channel permissions you want: CRM, sales or messages. Add a spending cap if you like. Copy the key: it's only shown once.
- In your assistant, add the server https://studio.utio.io/api/mcp with the header "Authorization: Bearer <your key>". With Claude Code:
claude mcp add --transport http utio https://studio.utio.io/api/mcp \ --header "Authorization: Bearer <your key>"
What it costs
No price of its own
Whatever you do over MCP is charged as if done from the panel or the API, from your balance.
- For example, a WhatsApp message sent is charged as a conversation: €0.05 at the base rate.
- Reading the CRM or sales data isn't metered.
- API keys come with the AI module, which we switch on in your account. The module's terms are on the API page.
- Base rates, excluding VAT. If you buy through a partner, their rates apply.
What you need and what it doesn't do
Before you connect anything, here's what's there and what isn't.
What you need
- The AI module active to create keys, even if you only use CRM permissions.
- The module for each channel you use: without the WhatsApp module, sending a WhatsApp message returns an error. The CRM is always there.
- An MCP client that connects over HTTP with an authorization header (Claude Code, Cursor…).
What it doesn't do
- No OAuth: the claude.ai and ChatGPT connectors that require it don't work today.
- No access to the Studio's AI (transcription, speech generation…) or to live voice and calls.
- It doesn't manage the calendar or appointments.
- No events or notifications: the assistant asks and the server answers.
- No single key for everything: AI and channels always use separate keys.
- Tool descriptions are in Spanish; whether the assistant replies in your language is up to the assistant.
Want to code against the API directly? See the AI API . And the CRM your assistant works on is covered in AI CRM .
Further reading
A step-by-step guide to integrating an AI agent with a CRM
Learn how to connect an AI agent to your CRM, set fields, permissions and handoffs, then test the workflow before launch to prevent incomplete records.
Questions about the MCP server
Can the assistant message my customers on WhatsApp without asking me?
Only if the key carries the WhatsApp permission; otherwise it doesn't even see that tool. And the tool tells it to confirm with you before sending.
What if the connection drops and the assistant repeats the command?
It isn't executed twice: every call carries its own idempotency key.
Can I limit what it spends?
Yes. Each key takes a cap in euros and, once it's reached, stops working until you raise it.
Does it work with ChatGPT or the claude.ai connector?
Not today. Those connectors require OAuth, and UTIO's server only accepts a key in the "Authorization: Bearer" header. It works with Claude Code, Cursor and MCP clients that let you add that header.
How much does it cost?
It has no price of its own: each action costs the same as from the panel, from your balance. For example, a WhatsApp message sent is charged as a conversation (€0.05 at the base rate), and reading the CRM or sales data uses nothing.
Want to connect your AI assistant to UTIO?
Tell us which assistant you use and what you want it to do, and we'll switch on the AI module. We'll get back to you as soon as possible, usually within one working day.
- Phone
+34 951 047 200 - Email
utio@utio.io - WhatsApp
Send a message
- 🔒 Secure data
- ⚡ Reply within 24h
- ✓ No commitment