Now your agent knows too.
She is in your browser. She is in your pocket. Now she is inside the document you are actually writing. Connect VibeCFO to Claude or any MCP client, and your agent reads the same reconciled numbers EVA works from, along with the Buckets, Pulses and reports she has already built.
The Model Context Protocol (MCP) is an open standard for connecting AI assistants to external systems. The VibeCFO MCP is a server that lets Claude, or any MCP client, query your reconciled financial data from Xero, MYOB, XPM and every other system you have connected to VibeCFO.
Stop leaving the room to get the number.
You are mid-sentence in a client’s strategy paper. You need last quarter’s WIP recovery. So you stop, switch, find it, paste it, come back - and by then you have lost the sentence.
The number should come to you. Not the other way around.
And it should still be right tomorrow.
Your numbers, inside the document you are writing.
VibeCFO is where your numbers become true. Four years of pipeline work, every system reconciled, every figure traceable to the row it came from.
But the board paper is not in VibeCFO. Neither is the client email, the proposal, or the strategy memo you are three drafts into. Those live where they have always lived.
The MCP is how the true numbers get into them. Your agent asks. The figures arrive with their source. You keep writing.
You are drafting a three-year plan for a client. In the same window you have the last board pack, their email thread, and the industry benchmark you pulled this morning. You ask your agent for the last eight quarters of gross margin by service line. It arrives, from VibeCFO, reconciled. Two paragraphs later you ask what happens to that trend if headcount goes up fifteen percent. Nobody built a dashboard for that question, because nobody knew you were going to ask it.
A dashboard answers the questions someone thought of in advance. A conversation answers the one you just had.
Every other finance MCP hands your agent an API. Ours hands it a schema.
One gives your agent a pile of endpoints and hopes it works out which number is right. The other gives it your actual numbers, already reconciled across every system you connected.
How the VibeCFO MCP differs from Xero’s MCP
“Which of our clients are we losing money on this year?”
Claude, pointed at a ledger’s own MCP
All it can reach is one system’s API surface. So it answers the question it can answer, not the one you asked.
- ·Invoiced revenue per client - from one entity
- ·No time, no WIP, no recoverable rate
- ·Cost of delivery is simply not in scope
- ·So the answer is revenue ranked by size, presented confidently
Claude, pointed at the VibeCFO MCP
Same session, same prompt. It reaches a reconciled schema, so it can answer the question as asked.
- Time and WIP out of XPM, row by row
- Invoiced revenue out of the ledger, joined to it
- Every entity you connected, already consolidated
- Margin per client, and the source row behind each figure
Both agents were asked which clients the firm is losing money on this year. The one connected to a ledger’s own MCP can only reach that ledger, so it answered with invoiced revenue for a single entity and ranked clients by size - it never saw the cost of delivery, because time and WIP do not live in the ledger. The one connected to the VibeCFO MCP read the reconciled schema instead: time and WIP out of XPM joined to invoiced revenue, consolidated across every entity, with the source row behind each figure. The first cannot answer the question as asked. The second can.
| Capability | Raw accounting MCP | The VibeCFO MCP |
|---|---|---|
| What your agent gets | The vendor's API surface | A reconciled canonical schema |
| Coverage | One system | Every system you connected |
| Aged debtors, WIP, stock on hand | Whatever that endpoint exposes | Already mapped, row by row |
| When two systems disagree | Your agent picks one | Traceable to the source row |
| Multi-entity | Query each, stitch by hand | Already consolidated |
| What EVA has already built | Nothing | Your Buckets, Pulses and pinned reports |
The hard part was never the connection. It was making the data mean the same thing twice.
So why not just use Claude?
You still can. That is the point.
What comes down the wire is not a shortcut around the engineering. It is the engineering. The ETL, the canonical schema, the isolation. That is what makes the answer worth putting in front of a board.
What stays in VibeCFO is the making. Building a Bucket, shaping a report, setting a Pulse to watch overnight, editing the numbers in the grid, pushing the engagement letter into Ignition. VibeCFO is where the work gets built and kept.
Your agent reads what she has built. She keeps building while you sleep. Use both.
If your firm has already standardised on Claude, VibeCFO connects to what you have already rolled out.
Ask it where you already are.
What you can ask an accounting MCP
“Which of this client's debtors are over 60 days?”
The rows, not a summary figure. Straight out of the reconciled schema.
“What's WIP by partner for last quarter?”
Row-level, out of XPM, joined to the ledger.
“Pull the numbers from their last board pack and bring them up to today.”
Reads the report already pinned in VibeCFO, then refreshes the figures.
“What did my Pulses find this week?”
The overnight monitors, and anything unread.
“Where should I focus with this client?”
EVA's advisory view, assembled from their full profile.
“Build me a Bucket tracking cash conversion, then chart it here.”
EVA proposes it, you confirm, and she builds it in VibeCFO while you keep writing. Your agent charts the result in the document.
Same numbers EVA reads. Same governance. In whatever you had open.
Reaching in is not the same as letting go.
Security and governance for external agent access
It cannot touch your ledger.
Your agent reads your numbers. Writing outward does not happen over this connection - it cannot push to Xero, MYOB or any connected accounting system.
It asks before it acts.
If you ask your agent to build something in VibeCFO, EVA proposes it first and waits for your yes. Nothing is created off the back of a model deciding on its own.
Scoped to one business.
Each connection is linked to one accounting business and reaches only the clients that login can already see. Connect a second business and it is a separate connection, authorised separately.
Every call logged.
What was asked, by which agent, and what came back. The same trace as a question asked inside the app.
One connection. Under a minute.
How to connect Claude to VibeCFO
There is no token to generate. It is a standard OAuth login with the VibeCFO credentials you already have.
mcp.vibecfo.au- 1
Add VibeCFO as a connector in Claude, using mcp.vibecfo.au.
- 2
Log in with your VibeCFO credentials. If you have more than one business, pick the one you want this connection to reach.
- 3
Ask it something.
One connection reaches one business. Firms handling several businesses add a connector for each, and each one is authorised separately.
The VibeCFO MCP is in beta and hosted in Australia only. Firms on our New Zealand, UK, US and Canada regions cannot connect to it yet - talk to us and we will tell you where your region sits.
Verified clients
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.
Other MCP-compatible clients use the same OAuth login, but we have not tested them yet - and we will not list one until we have. During beta, connect it in Claude.
EVA reaches into your tools. Now your tools can reach into her.
Last updated 28 July 2026
The tools EVA reaches into are Action MCPs. This page is the other direction.
The VibeCFO MCP, explained
What is an MCP server for accounting data?
An MCP server lets an AI assistant query an external system directly. The VibeCFO MCP is a server that gives Claude, or any MCP client, access to your reconciled financial data from Xero, MYOB, XPM and every other system connected to VibeCFO. Your agent asks. The numbers come back reconciled, row level, with their source.
How is this different from connecting Xero's MCP straight to Claude?
Xero's MCP gives your agent Xero's API surface. One system, raw endpoints, and your agent works out which number is right. The VibeCFO MCP gives it a reconciled canonical schema across every system you connected. Time and WIP out of XPM joined to invoiced revenue out of the ledger, consolidated across entities, traceable to the row it came from.
Does this replace EVA?
No. VibeCFO is where the work gets built and kept. Building a Bucket, shaping a report, setting a Pulse to watch overnight, editing the numbers in the grid. The MCP is how your agent reads what EVA has already built, inside the document you are writing. She does the building. Your agent does the reading. Use both.
Can my agent change my data?
It cannot write to Xero, MYOB or any connected accounting system. Pushing outward does not happen over this connection. It can ask EVA to build something inside VibeCFO, a Bucket or a report, and when it does, EVA proposes it and waits for your yes. Nothing is created off the back of a model deciding on its own, and every call is logged.
Which AI clients does it work with?
Claude on the web and Claude Desktop are verified today. Any MCP client can connect using the same standard OAuth login, but we have not tested others end to end yet - and a client only appears on this list once we have.
Which regions can connect?
Australia only for now. The MCP is in beta on an AU-hosted server, and there is no New Zealand, UK, US or Canada equivalent yet, unlike the regional platform logins. Ask us and we will tell you where your region sits.
Can different staff connect to different businesses?
Yes, per business. Each connection is authorised against one accounting business and reaches only the clients that login can already see. Someone handling three businesses adds three connectors, authorised separately. There is no per-client token, so a connection cannot be cut down to a single client.
Is this included in my plan?
Yes. There is no additional charge for the MCP. It uses your existing VibeCFO login, so a connection reaches exactly what that login already reaches - you pay for your integrations and seats as you already do.
Does my data get used to train anyone's model?
No. The model providers do not train on customer data. Under our partnership obligations with Xero we are contractually prohibited from using Xero-sourced data to train AI models, and as a matter of policy we do not use any customer financial data, numerical results or client information to train models, regardless of source. Read more on our privacy and security pages.
Your numbers are already telling a story.
Let EVA read it, and act on it. Out of the box, governed and secure, ready the moment you ask.