One server, any client that speaks the protocol
We did not write a Mistral integration. We wrote one standards-compliant MCP server and let every client that speaks the protocol come and get it - nothing vendor-specific to maintain.
Worth saying plainly, since it's often why people pick Vibe: connecting infioo doesn't keep your data inside infioo. When Vibe calls a tool, the answer - customer names, messages, amounts - is sent to Mistral and becomes part of that conversation, under Mistral's terms and your Vibe settings. What stays the same: infioo doesn't copy your records anywhere else, the connection reaches only what you granted, and the tools that send or bill aren't on the server at all.
How to connect it: five steps
Copy this URL:
https://infioo.ai/api/mcp
- In Vibe (Mistral's app, called Le Chat until 2026), open Connectors and choose + Add Connector.
- Open the Custom MCP Connector tab.
- Name it INFIOO - one word, since Vibe rejects spaces and special characters - and paste the URL.
- Vibe detects the sign-in method itself. Leave any OAuth client ID or client secret fields empty, connect, then sign in, choose which business and which permissions, and approve.
- Turn the connector on in a chat and ask "what needs me today?" If your real brief comes back, you are done.
Nothing else to paste: you sign in to infioo when Vibe asks, unless you use the key fallback below. Leave any client ID, client secret or advanced OAuth fields empty - Vibe registers itself, and infioo issues no client secret.
Vibe then reads the tool list off the server itself - nothing to configure tool by tool. No install, no hosting, no tunnel: infioo.ai is already on the public internet.
If sign-in doesn't work: the key fallback
Mistral's docs list a bearer token among the sign-in methods Vibe supports, but Vibe picks the method itself from the server's response, and infioo's server asks for sign-in - so Vibe may not offer you a token field. If it does, an owner can mint an automation key in infioo under Settings -> Connections - shown once, so copy it then - and paste it as the token instead of signing in.
An automation key is different. It always carries read and write (never approve), isn't tied to a person's role, and works until an owner revokes it in Settings -> Connections. Use it only where sign-in isn't possible.
Try it first, with no account
Use this URL at step 3; Vibe should detect that it needs no sign-in.
https://infioo.ai/api/mcp/demo
No sign-in, no email, nothing to cancel - a fictional plumbing company carrying a normal week's mess. Read-only, and the assistant is told the data is invented as soon as it connects.
Eighteen tools. Five write. None send.
Can
- Read contacts, conversations and messages
- Read the schedule, invoices and open tasks
- Search your knowledge base
- Create a task or a contact
- Tag a contact
- Draft a reply for your approval
- Mark an appointment complete
Cannot
- Send a message to a customer
- Create, send or sync an invoice
- Post publicly as your business
- Add anyone to a marketing list
- Touch billing, team invites or payroll
- Manage API keys
- See another business's data
Drafting is not sending. A reply Mistral writes becomes a pending draft behind the Approve button already in your inbox. And the right-hand column is not a setting - those tools are absent from the connector, each with its reason recorded in code and a test that fails if one sneaks back. There is a daily write ceiling per business too, so a confused loop cannot run away with your records.
Permissions, and who may grant them
On the sign-in screen you grant from three permissions - read, write, approve - and your role caps what you may hand over, so plugging in an assistant is never a way to gain access you did not have. Owners and managers may grant all three; staff cannot grant approve; an accountant can grant nothing.
When you connect by signing in, access tokens last fifteen minutes, refresh tokens rotate, and your role is re-checked on every call against live membership - so a change in infioo narrows the connection on the next question.
When Vibe calls an infioo tool, the answer - customer names, messages, amounts - goes to Mistral and becomes part of that chat, kept under Mistral's terms and your settings there. infioo doesn't copy your records anywhere else.
Honest limits
Booking and invoice proposals are not offered from chat yet. Both belong in the owner's approval queue, which today assumes a pending item came from one of your agents - so a proposal from a chat connector would fail the moment you pressed Approve. That code guards real money, so it changes carefully or not at all.
We haven't tested infioo end to end in Vibe yet. The server follows the published MCP specification and Vibe's documented connector setup, so it should work. If it trips, tell us at hello@infioo.com.