One server, every client that speaks the protocol
We did not write a Gemini integration. We wrote one standards-compliant MCP server, and anything that can add a custom MCP server reaches it - nothing vendor-specific to maintain.
Which matters more than it sounds. A client that ships MCP support on a Tuesday should work with infioo on that Tuesday, because there was never a Gemini-shaped adapter to write.
How to connect it: five steps
Copy this URL:
https://infioo.ai/api/mcp
- On a computer, open gemini.google.com and sign in with an eligible personal Google account.
- Open Settings -> Connected Apps -> Add a custom app.
- Paste the URL. Leave Advanced features empty and click Next.
- Sign in to infioo, choose which business and which permissions, and approve.
- Ask "what needs me today?" If your real brief comes back, you are done.
Nothing else to paste: you sign in to infioo when Gemini asks. Leave any client ID, client secret or advanced OAuth fields empty - Gemini registers itself, and infioo issues no client secret.
Once set up on the web, it works in the Gemini mobile app too. Gemini asks you to confirm before any tool that changes something runs - that's Google's check, on top of ours.
Gemini 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, so the client reaches it directly.
Try it first, with no account
Use this URL at step 3 instead. It needs no sign-in; we haven't confirmed Gemini accepts a server without one.
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 Gemini 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 Gemini calls an infioo tool, the answer - customer names, messages, amounts - goes to Google and becomes part of that chat, kept under Google's terms and your settings there. infioo doesn't copy your records anywhere else. Custom apps require Keep Activity on, so Google keeps these chats under your activity settings.
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 Gemini yet. The server follows the published MCP specification and Gemini's documented connector setup, so it should work. If it trips, tell us at hello@infioo.com.