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:
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:
https://infioo.ai/api/mcp
- Open Claude on the web or in the desktop app and sign in.
- Go to Customize -> Connectors.
- Click + Add, then Add custom connector.
- Name it infioo, paste the URL and click Continue. Then check the settings Claude detected: under Authentication keep a sign-in option (not No sign in); under OAuth client keep Claude's recommended option or pick Register automatically, the one we tested - not Use your own OAuth client; leave Request headers empty. Click Continue where asked, then Add.
- Sign in to infioo when Claude sends you there (if it doesn't, click Connect next to the connector), choose which business and which permissions, 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 Claude asks. Don't pick Use your own OAuth client, and leave Request headers empty - Claude identifies itself, and infioo issues no client ID or secret to paste.
About a minute, with nothing to install or host. On Team or Enterprise, an owner adds the same URL once under 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 was saved without sign-in - remove it and add it again with a sign-in option under Authentication, rather than reconnecting. Anything else, mail hello@infioo.com.
Try it first, with no account
Use this URL at step 4 instead, and choose No sign in under Authentication if Claude hasn't already. There is nothing to sign in to.
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
On the sign-in screen you tick which permissions to hand over - read and write, plus approve only if the assistant asks for it (it starts unticked, and nothing on this connection uses it yet) - 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.
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 Claude calls an infioo tool, the answer - customer names, messages, amounts - goes to Anthropic and becomes part of that chat, kept under Anthropic's terms and your settings there. infioo doesn't copy your records anywhere else.
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.