Your shop, answerable in chat
infioo publishes itself as a remote MCP server - the standard assistants use to reach outside tools. Claude is a client. So you stop navigating a dashboard and just ask:
"What needs me today?"Overdue money, unanswered messages, today's jobs - in one pass.
"Who hasn't paid, oldest first?"Straight off the ledger, with amounts and ages.
"Catch me up on the Novak job."Conversation, appointments and invoice, tied together.
"Draft a reply to Maria about Thursday."Written in context, parked in your inbox for one tap.
Eighteen tools. Five write. None send.
Drafting is not sending. A reply Claude writes becomes a pending draft behind the Approve button already in your inbox.
What Claude may and may not do
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
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 creeps back.
How to connect it: six steps
Copy this URL - it is the only thing you need:
https://infioo.ai/api/mcp
- Open Claude in a web browser and sign in.
- Go to Customize -> Connectors.
- Click +, then Add custom connector.
- Paste the URL. Ignore Advanced settings - no client ID, no secret, no header. Click Add.
- Click Connect, sign in to infioo, choose which business and which permissions, approve.
- Ask "what needs me today?" If your real brief comes back, you are done.
About a minute, with nothing to install or host. On Team or Enterprise, an owner adds the same URL once under Settings -> Organization settings -> Connectors; everyone else then clicks Connect and signs in as themselves.
One failure has a non-obvious fix: if Claude says the connector was "set up as not requiring sign-in", it kept a stale setting - remove it and add it again rather than reconnecting. Anything else, mail hello@infioo.com.
Try it first, with no account
Follow the same six steps with this URL and skip the sign-in entirely:
https://infioo.ai/api/mcp/demo
A fictional plumbing company with a normal week's mess in it - overdue invoices, jobs today, someone waiting on a reply. Read-only, and Claude is told the numbers are invented the moment it connects.
Permissions match the person
You grant from three permissions - read, write, approve - and your role caps what you may hand over, so connecting an assistant is never a promotion. Owners and managers may grant all three; staff cannot grant approve; an accountant can grant nothing.
Access tokens last fifteen minutes and refresh tokens rotate. The role ceiling is re-checked on every call against live membership, so a change in infioo narrows a live Claude connection on the next question - nothing to remember, nothing to revoke by hand.
Not from chat yet
Booking a job and proposing an invoice are built but not offered here. Both belong in the owner's approval queue, which today assumes a pending item came from one of your agents - so a proposal from chat would fail on Approve. That code guards real money, so it waits.
INFIOO in ChatGPT
INFIOO in Grok