MCP for Accountants — What It Is and How to Use It

There is a new line item quietly appearing in accounting software, and almost nobody is explaining it.

The Model Context Protocol, MCP, is an open standard that lets an AI assistant use an application’s tools directly. Not a chatbot bolted onto a sidebar, and not another integration you configure field by field. You connect the application once, and the assistant can then read your firm’s data and do work in it, the same way it already reads your files or your calendar.

For a firm owner, the practical difference is this: instead of exporting a report and pasting it into a chat window, you ask “which clients had no time logged this month?” and the assistant goes and looks.

This article explains what an MCP server does inside a practice, shows what Uku’s does in concrete terms, and compares it with what the other practice-management vendors have shipped. It ends with the seven questions to ask any vendor before you connect their server to client data.

What an MCP server actually does inside a practice

Strip away the protocol talk and an MCP server is a list of things an assistant is allowed to do, published in a format the assistant can read for itself. That is the whole trick. With a normal API, a developer reads the documentation and writes code for your firm. With MCP, the assistant reads the tool list and works out the call on its own.

So the useful question is not “does it have MCP” but “what is on the list, and what does each item wait for”.

A practice-management MCP server exposes tools in a few families:

• Reading the firm. Clients, tasks, time entries, workflows, documents, the audit trail. This is the bulk of the value for most firms, and the least frightening.
• Doing work. Creating and completing tasks, logging time, adding comments, applying a workflow to a client, uploading a document.
• Money. Drafting and sending an invoice, reading a contract, checking a budget, exporting to the ledger. This is where the sharp edges live.
• Reporting. Margins, utilisation, unbilled work, whatever your system already computes.

The level of detail you should expect before you connect anything to client records is the full list, tool by tool, with a mark on each one saying whether it reads, writes, or stops and asks. In this category, only one vendor publishes that today.

What Uku’s MCP server does

Uku’s MCP server gives Claude or ChatGPT 88 actions across 17 areas of a firm’s work. 40 of them read. 48 write or delete. Every one is listed by name on the page, so you can see the whole surface before you connect.

Here is what that looks like in a normal week at a firm:

• “Which clients have no time logged this month?” The assistant reads time entries and answers with a list.
• “Show me unbilled work for August.” It reads missed billing and gives you the figures by client.
• “Create a task for Nordic Foods: VAT return, due the 20th, assign to Mari.” It creates the task straight away, in Uku, under your name.
• “Log two hours on the Baltic Retail year-end.” Logged, as you.
• “Apply the monthly bookkeeping workflow to the three clients we signed last week.” It shows you the three clients and the workflow, and waits for your yes.
• “Add a new service to my clients’ contracts: monthly finance report with forecasting in the client portal, fixed fee $25 a month.” It adds the service to your price list and shows you the change on every client’s contract before it applies. Say yes, and Uku bills the new line from the next invoicing run automatically.
• “And raise the consultation hourly rate to $85 for those clients.” It shows you current and new for every client, then sets the new rate from the date you name. The next invoices carry $85 without anyone touching them. Invoices already sent stay as they are.

The rule is simple. Reading never needs your permission. Small everyday actions do not either: a new task, a time entry, a checklist tick, a file upload. Everything else shows you what it is about to do first. You say yes, and only then it happens. Money, changes to many records at once and deleting anything are always in this second group.

Money is a separate permission. When you sign in from Claude or ChatGPT, financial data is its own checkbox on the consent screen. Only a person with account-management rights in Uku sees the box. Leave it unticked and the assistant runs tasks, time, clients and workflows all day, and says no when you ask about invoices or prices. Tick it, and the assistant can read and draft the firm’s invoices, contracts and budgets, still waiting for your yes on anything it sends.

Some things are not on the list at all. An assistant cannot delete a client or a project. It cannot invite or remove members, change roles, edit the subscription, change team permissions or manage API keys. Those stay in Uku, where a person does them on purpose.

Every action lands in the audit trail. The assistant acts as the person who connected it. Uku records which action ran, when, by whom and through which connection. Nothing an assistant does is invisible or attributed to a robot.

Connect it in three steps

You do not need a developer, an API key or anyone from Uku.

1. Add Uku in your assistant. In Claude, open Settings, then Connectors, add a custom connector and paste https://app.getuku.com/mcp. In ChatGPT, turn on Developer mode and add a connector with the same address.
2. Sign in to Uku and click Allow. Tick the financial box only if you want the assistant to see money.
3. Ask something. Start with a read: “What is on my task list this week?”

Any active member of a firm on the Elite plan can connect their own account. The step-by-step guides with screenshots are in the help center for Claude and ChatGPT, and the full list of what an assistant can do is there too.

How the other practice-management vendors compare

We connected to each vendor’s MCP address directly on 11 September 2026, rather than reading their marketing pages, and then looked for any public description of what the server can do. The addresses are below so you can try them in your own assistant.

Two things are worth saying plainly about that table.

The first is that Karbon shipping an MCP server with both read and write access is a real piece of engineering, and it is ahead of most of the category. Their developer documentation is genuinely good. A firm’s IT person handed that file has what they need.

The second is that a firm owner will never find it. There is no page describing what the server does, which tools it exposes, or what an assistant connected to it is permitted to change in your clients’ records. The public references are one sentence in an event recap and a URL in a file written for developers and their coding agents.

Client Hub is further along the same road: a live server with no discoverable documentation at all. TaxDome’s address answers today, while their own site still describes MCP as coming. That may simply be a server ahead of its announcement, and it is worth asking them what it does before you connect it.

On the ledger side

The general-ledger vendors have been more open about it. Xero runs a hosted server at https://mcp.xero.com/mcp, which signs you in with your Xero account and grants access per area, such as invoices, contacts and reports. Xero also publishes the code as an open-source repository, XeroAPI/xero-mcp-server, alongside an AI developer hub. Intuit publishes a QuickBooks Online server at intuit/quickbooks-online-mcp-server. In both cases you can read the code before you decide.

This is the shape most firms will end up in, and it is worth planning for: an assistant can hold several servers at once, each with its own permissions. The ledger’s server for the books, Uku’s for the tasks, the time, the deadlines and the margins. Uku’s server also exports invoices to the accounting software and reads payment status back, so the two sides meet in the middle.

What firms actually want from this

When we surveyed accounting firms for our 2026 AI report, the answers were more grounded than the sales pitches around them.

The single most requested job for an autonomous AI agent was not analysis or forecasting. Nearly 7 in 10 firms said the first thing they would hand over is chasing clients for missing documents, the dull recurring chore that eats a junior’s week and never quite finishes.

And the number that should shape every buying decision in this category: 0% of firms said they already fully trust AI to act on its own. Not one respondent. Almost all of them want a person to approve before anything is sent or filed.

That is not a vote against AI. It is a specification. Firms will hand over the work the moment they keep the final say. So the interesting question about any MCP server is not how many tools it has, but which of them stop and ask. That is why Uku’s server previews every invoice, every bulk change and every deletion before it acts, and why the count of tools that wait is printed on the page next to the count of tools that do not.

Seven questions to ask before you connect one

Take these to your vendor. The answers are more revealing than the feature list. After each question is how Uku answers it, so you have something to compare against.

1. Whose permissions does the assistant act with? The right answer is “the person who connected it, exactly”. If an assistant can open a client that the person who connected it cannot open in the software, connecting an AI has just widened someone’s access, and your access-control model is now fiction. Uku: the assistant sees exactly what the signed-in member sees, nothing more.

2. Which actions wait for an explicit confirmation? Money, bulk changes and deletions should preview precisely what they are about to do and wait for a yes. Ask for the number, not the reassurance. Uku: 43 of the 48 write tools preview first, and the page marks each one.

3. Can the assistant widen its own reach? An assistant asks for the access it wants when it connects. A well-built server ignores that request and grants access from its own rules, so an assistant cannot simply ask for more and be given it. Uku: the assistant gets what the member has, and financial access is a box a person ticks, never something the assistant can request.

4. Is financial access separate? Invoices, contracts, pay rates and budgets are a different category of exposure from tasks and deadlines. They should be their own consent, granted deliberately by someone who already administers the account. Uku: a separate checkbox, visible only to people with account-management rights.

5. What is not exposed at all? Some things should be absent rather than gated. Ask what is off the list entirely, and be suspicious if the answer is “nothing”. Uku: deleting a client or project, members, roles, the subscription, team permissions and API keys are not available to an assistant.

6. Does every action land in the audit trail, under a name? An assistant acting as you should be as visible as you clicking the button. If actions arrive attributed to a robot, or do not arrive at all, you have lost the thread you will need during a review. Uku: every action is recorded with the person, the time and the connection it came through.

7. Where is this written down? If the only answer is a URL in a developer file, that is worth pressing on. Ask for the tool list. A vendor who can hand you one has thought about the question. A vendor who cannot may not yet know what their own server permits. Uku: the MCP page lists every tool, and the help center has the full capabilities guide.

Where this is going

The firms getting value from AI right now are not the ones with the most impressive demo. They are the ones whose systems let an assistant see real data and act on it under real constraints, which is exactly what MCP standardises.

The category will catch up quickly. What will separate vendors within a year is not who has a server, because most will, but who is willing to tell you in plain language what theirs is allowed to do to your clients’ records.

If you want to see what that looks like written out, the Uku MCP server page lists every tool by name, marks which ones write, and marks which ones stop and ask first. The AI agents page covers the API and CLI underneath it for firms that want to build their own automations. Both come with the Elite plan. You connect by signing in from Claude or ChatGPT, and the first useful answer is about two minutes away.

If you would rather watch it than read it, Get Growing, our September 30 event, shows billing, BI and the AI assistant in one sitting. The recording stays on the same page afterwards.