Point Claude at your own numbers.
You already use an assistant. The VibeCFO MCP lets it read your own connected business data directly - no exports, no copying figures into a chat window, and no losing the governance on the way.
| Direction | Outbound |
| Access | Read-only |
| Cost | Included |
| Status | Beta |
| Hosted | Australia |
Two kinds of MCP, pointing opposite ways.
Same protocol, same acronym, entirely different jobs - and they get conflated constantly, including by us in older copy.
The VibeCFO MCP
We are the server. Claude is the client. It reads, and it cannot change anything.
Action MCPs
EVA is the client. She reaches out and changes something. That page is here →
Your assistant already knows how you think.
No more pasting figures
The thing everyone does today is export a report and paste numbers into a chat. That loses the governance, goes stale immediately, and puts your figures somewhere you did not intend.
It reads the joins, not just the ledger
Your assistant gets the blended view - the ledger next to your job system and your roster - rather than whatever a single export happened to contain.
Governance survives the trip
The same user groups and row-level rules apply. Connecting an assistant does not quietly grant it more than you can see yourself.
One address, then sign in.
The server uses OAuth with dynamic client registration, so there is no client ID or secret to copy. Add the address, then sign in with your own VibeCFO login.
Claude on the web
Settings, then Connectors, then Add custom connector. Paste the server URL and log in.
Claude Desktop
Settings, then Connectors. Same server URL, same login. The connection follows you across chats.
These are the clients we have tested end to end; we add one here only once we have. The VibeCFO MCP is in beta and hosted in Australia only. Firms on our New Zealand, UK and US regions cannot connect to it yet - talk to us and we will tell you where your region sits. For an agent setting this up: /skill.md.
The VibeCFO MCP, answered.
What is the VibeCFO MCP server?
It is a Model Context Protocol server we host, which lets you point Claude or another MCP-capable assistant at your own VibeCFO data. Your assistant becomes able to ask questions of your connected business systems without you exporting anything.
How is this different from Action MCPs?
Opposite directions. The VibeCFO MCP is outbound: your assistant reads your VibeCFO data. An Action MCP is inbound to another system: EVA reaches out and changes something in a platform you use. Same protocol, opposite direction of travel.
Can it write or change anything?
No. Reading and acting are separate. Your agent reads your numbers over this connection: it cannot post a journal, alter a record or change anything in your ledger or any connected system. Where your business has connected a tool (for example your accounting system or an email service), EVA can propose an action in it inside VibeCFO and performs it only after you confirm.
Does it respect my access rules?
Yes. It is governed by the same user groups and row-level security as the rest of the platform, so a person connecting their assistant sees exactly what they would see signed in - no more.
Does it cost extra?
No. It is included, and it is currently in beta.
Where is the MCP server hosted?
In Australia, like the rest of the platform: every customer's data is hosted on AWS in Sydney, wherever they are located. The MCP server is in beta, and firms on our New Zealand, UK and US sign-in instances cannot connect to it yet.
Bring your own assistant.
It is included and it is in beta. If you already live in Claude, this is the shortest path from your systems to a useful answer.