Skip to main content

Uku MCP server — your AI assistant, working inside your practice.

MCP is the open standard that lets an AI assistant use an application's tools directly. Nothing to install, no terminal, no credential on your laptop: you connect Uku once and the assistant you already use runs your firm's work in it, under your permissions, showing you any change that carries weight before it makes one.

85 tools across 16 areas of the firm's work

In beta on the Elite plan. Works with Claude, ChatGPT, Cursor — or an agent you built yourself.

Claude Cowork Uku

What can I do in Uku from here?

Here is what I can reach in your firm:

See the firm clients, tasks, time, projects, notes
Report profitability, utilization, the billing gap
Do the work create a task, log time, tick a checklist
Handle money raise, send, mark paid, contracts
Run the firm roll a workflow onto 200 clients, teams
Explain the help center, and who changed what

I act with your permissions. Anything with real reach waits for your OK first.

An example conversation. The firms, names and numbers are made up.

What your assistant actually does.

Not summaries of your data. The work itself, in your firm's own system, from a sentence you type.

Runs the firm's BI reports and ranks every client by profitability, so the ones quietly losing money surface on their own.

Sends an invoice to a client, after showing you exactly what goes out and waiting for your OK.

Applies a workflow template to 200 clients in one action, and tells you how many landed.

Logs two hours on Acme's VAT return, for you or for a colleague.

Tells you who is overloaded next week, and which work is already running late.

Explains how any Uku feature works, citing the help center article it read.

Every one of these runs under the same permissions as you, logged in. Your assistant reaches exactly as far as you do, and no further.

The tools we ship today.

85 tools across 16 areas, most of them read-only. The surface grows most weeks, so read this as what your assistant can do today rather than a fixed list.

Identity 2
whoami

Tells you which person and firm the assistant is acting as.

read
my_tasks

Lists what is on your own plate right now.

read
Company setup 3
get_setup_status

Says how far along the firm's Uku setup is.

read
activate_app

Switches on one of Uku's apps for the firm, after showing you which.

write · previews first
set_billing_defaults

Sets the firm's default billing settings, after showing you what changes.

write · previews first money
Search 9
search_uku

Finds a thing by name when you have not said what kind of thing it is.

read
search_tasks

Finds tasks by client, assignee, status or title.

read
list_clients

Lists the firm's clients, or finds one by name.

read
get_client

Opens one client's full record.

read
get_task

Opens one task, with its dates, status and who is on it.

read
list_contacts

Lists the people you deal with at a client.

read
list_projects

Lists the projects running for a client, or across the firm.

read
list_notes

Lists the notes written on a client, project or supplier.

read
list_time_entries

Lists individual time entries by person, client, task or date.

read
Reports 7
get_bi_metrics

Lists which business figures are available to report on, and what each one means.

read money
get_bi_summary

Gives the firm's headline numbers for a period: production, profit, utilization.

read money
get_bi_series

Tracks a figure month by month, so you can see the trend.

read money
get_bi_breakdown

Ranks clients, people, topics or services by any figure you choose.

read money
build_bi_view_link

Builds a link that opens the report in Uku, already filtered, for you to look at yourself.

read money
get_time_report

Totals the hours logged in a period, by client or by person.

read
refresh_bi_data

Rebuilds the firm's reporting data after something it depends on changed.

write money
Audit trail 2
search_activity

Shows who did what, and when.

read
get_activity_detail

Shows exactly what one change altered, from what to what.

read
Help 2
search_help

Searches Uku's own help center to answer “how do I…?”

read
get_help_article

Reads a help article in full, so the answer comes with a link you can open.

read
Task actions 9
create_task

Creates a task for a client, dated and assigned.

write
log_time

Logs hours worked on a task, for you or for a colleague.

write
add_checklist_item

Adds a step to a task's checklist.

write
toggle_checklist_item

Ticks or unticks a step on a task's checklist.

write
complete_task

Marks a task done, after showing you which one.

write · previews first
reopen_task

Puts a finished task back into progress, after showing you which one.

write · previews first
add_task_comment

Comments on a task. An internal note posts straight away; a message your client will see is shown to you first.

write · previews first
set_task_recurrence

Puts a task on a repeating schedule, after showing you what it will generate.

write · previews first
bulk_task_action

Applies one change to up to 200 tasks at once, after showing you the list.

write · previews first
Client actions 2
create_client_documents_folder

Sets up a client's cloud document folder ahead of the first upload.

write · previews first
send_email

Sends an email to a client from Uku, after showing you exactly what goes out.

write · previews first
Invoicing 9
list_invoices

Lists invoices, including every one still unpaid.

read money
get_invoice

Opens one invoice, with its lines, total and status.

read money
get_missed_billing

Finds work that was done but never billed.

read money
create_invoice

Raises an invoice, showing you the client, every line and the real total before it exists.

write · previews first money
add_invoice_row

Adds a line to an invoice, after showing you what it adds.

write · previews first money
generate_client_invoices

Generates the period's invoices from the clients' contracts, after showing you what would be raised.

write · previews first money
send_invoice

Sends an invoice to the client, after showing you exactly what goes out.

write · previews first money
mark_invoice_paid

Records an invoice as paid, after showing you which one.

write · previews first money
mark_invoice_unpaid

Reverses a payment recorded by mistake, after showing you which one.

write · previews first money
Billing reference 7
list_contracts

Lists the firm's billing contracts and which are active.

read money
get_contract

Opens one contract, with its lines and billing dates.

read money
list_products

Lists the services the firm sells.

read money
get_product

Opens one service, with how it is priced.

read money
create_contract

Creates a billing contract for a client, showing you the period and every line first.

write · previews first money
create_product

Adds a service to the firm's catalogue, after showing you how it is priced.

write · previews first money
create_tax

Adds a tax rate the firm can bill with, after showing you the rate.

write · previews first money
Budgets & flextime 5
get_budget_status

Says how much of a client's budget is used and how much is left.

read money
get_flextime_balance

Says how far above or below expected hours someone is.

read money
confirm_flextime_period

Approves someone's overtime for a period, after showing you the effect on their balance.

write · previews first money
decline_flextime_period

Declines someone's overtime for a period, after showing you the effect on their balance.

write · previews first money
set_member_cost_rate

Sets a team member's cost or billing rate from a given date, after showing you the change.

write · previews first money
Teams 6
list_teams

Lists the firm's teams.

read
get_team

Opens one team, with its lead and its members.

read
create_team

Creates a team, after showing you who will be on it.

write · previews first
update_team_members

Sets who is on a team, after showing you exactly who joins and who leaves.

write · previews first
set_team_lead

Makes someone the lead of a team, after showing you what that changes.

write · previews first
delete_team

Removes a team that is no longer used, after showing you what goes.

write · previews first
Workflow templates 10
list_client_workflow_templates

Lists the firm's templates for recurring work, like monthly VAT or annual reports.

read
get_client_workflow_template

Opens one recurring-work template and every task on it.

read
get_client_workflow

Says who is responsible for what on a client, and what recurring work it carries.

read
create_client_workflow_template

Creates a new template for recurring work, after showing you what it will contain.

write · previews first
save_client_template_task

Adds or edits one task on a template, after showing you the before and after.

write · previews first
delete_client_template_task

Removes a task from a template, after showing you which one.

write · previews first
set_client_manager

Puts a named person in charge of a client, after showing you who holds it now.

write · previews first
set_client_roles

Sets who holds which role on a client, after showing you exactly what changes.

write · previews first
apply_client_workflow

Rolls a template out onto up to 200 clients in one action, after showing you the scale of it.

write · previews first
push_client_template_changes

Pushes an edited template onto the clients already using it, after showing you the reach.

write · previews first
Project workflows 4
list_project_workflows

Lists the firm's templates for one-off engagements, like onboarding or a year-end close.

read
get_project_workflow

Opens one engagement template and how its task dates hang off the project's own schedule.

read
apply_project_workflow

Starts a project per client from a template, after showing you what will be created.

write · previews first
push_project_workflow_changes

Pushes an edited engagement template onto projects already running from it.

write · previews first
Background jobs 1
get_job_status

Says whether a large rollout has finished, and whether any client was skipped.

read
Generic records 7
list_records

Lists anything the named tools do not cover: suppliers, topics, custom fields, and the rest.

read
get_record

Opens one record of any kind the named tools do not cover.

read
create_record

Creates a record of any kind the named tools do not cover, after showing you the fields.

write · previews first
update_record

Changes fields on any record, after showing you which values move and to what.

write · previews first
delete_record

Deletes a leaf record such as a duplicate task or a stray note, after showing you what goes. Clients and people are not deletable at all.

write · previews first
get_capabilities

Tells you what the assistant can and cannot do in Uku, before it tries.

read
bulk_member_action

Adds, swaps or removes people and roles across many clients at once, after showing you the full reach of the change.

write · previews first

Five small, reversible actions run straight away: logging time, creating a task, adding or ticking a checklist item, and refreshing your reports. Everything with real blast radius previews first. Prefer to build on it directly? The same surface is available as Uku API v3 and the Uku CLI, on the same plan.

One block of config, and you are connected.

No glue code, no integration project. Your assistant reads the tool list itself and gets to work.

MCP client configuration
{
  "mcpServers": {
    "uku": {
      "url": "https://app.getuku.com/mcp",
      "headers": {
        "X-Uku-Company": "<company id>",
        "X-API-Key": "<personal API key>"
      }
    }
  }
}

Both values come from Settings & Apps → Public API in Uku, where owners and admins create keys. The endpoint at https://app.getuku.com/mcp opens for your firm once access is granted.

Remote-connector clients such as Claude.ai need no key at all: they sign in with OAuth, and you approve the connection at that moment. Financial data is its own checkbox on that screen, offered only to someone who already administers the account.

Building something of your own instead? The API v3 reference is public and needs no key to read.

Your AI cannot touch money unless you say so.

The hard part of putting an assistant near a client ledger is not what it can do. It is knowing what it cannot. So that answer is built into the server, not left to the prompt.

Every write of consequence waits for you

Money, bulk changes, deletions, permissions: anything with real reach previews exactly what it is about to do and waits for an explicit yes. You approve a described action, never a guess.

Financial access is a separate, admin-only consent

Money is not part of the general grant. When you connect over OAuth it is its own checkbox, and that checkbox is only offered to someone who already administers the account — so it never widens what that person can already see in Uku.

An assistant cannot ask itself into your money

The scope a connecting client requests is discarded. The server rebuilds the granted scope from its own constants, so no assistant can widen its own reach by asking for more. Admin is never granted over OAuth at all.

The governance plane is permanently out of reach

Inviting or removing a member, changing anyone's role or status, editing the subscription, creating or deleting a company: none of it is exposed to an assistant. Not gated behind a permission — absent by design, for security.

It acts as you, with your rights

A connection is bound to one firm, and inside it the assistant sees precisely what the person who connected it sees. A client they cannot open in Uku, it cannot open either. Connecting an AI never widens anyone's access, every action lands in the audit trail under that person's name, and content coming back out of Uku is treated as data, never as instructions.

Written for the way US firms are now told to use AI.

In June 2026 the IRS Office of Professional Responsibility published its first guidance on AI in federal tax practice. It named four risks. Uku's answer to each one is a product decision, not a policy page.

RiskNo human oversight

Every write of consequence stops and shows you what it is about to do. Review is not a habit someone has to remember: it is where the tool stops. Circular 230 §10.22 asks for human review before AI output reaches a client or the IRS.

RiskClient data spillover

A connection is bound to one firm, and over OAuth that firm comes from the key itself — a connecting client cannot point it elsewhere. Inside the firm the assistant inherits one person's permissions and sees no further.

RiskPrivacy breaches

Financial data is a separate consent, offered only to someone who already administers the account, and the connecting client cannot request it for itself. Account administration is not reachable at all. §10.36 asks firms for secure data handling and vetted vendors.

RiskHallucination

The assistant answers from your firm's own records rather than from memory, and when it explains a feature it cites the help center article it read. You can check what it read.

These describe what the software does. The professional judgment stays where Circular 230 puts it, with the practitioner. Read the IRS bulletin.

Common questions.

What is MCP?

The Model Context Protocol is an open standard that lets an AI assistant use an application's tools directly, instead of you copying data between them. You connect Uku 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.

Which AI assistants does it work with?

Any MCP-capable client: Claude, ChatGPT, Cursor, or an agent you built yourself. That is the point of an open standard — you keep the assistant you already use, and Uku is one of the applications it can operate.

Which plan includes the Uku MCP server?

The Elite plan, the same gate as Uku API v3. Owners and admins create and manage the keys in Settings & Apps → Public API.

Can my AI see our money?

Only if you grant financial access on purpose. Invoices, contracts, product prices, budgets and pay rates all sit behind it. A key without it runs tasks, time, clients and workflows all day and is refused the moment it reaches for an invoice. Over OAuth that access is a separate checkbox, and it is only offered to someone who already administers the account.

Can it delete a client?

No. Deleting a client or a project carries its tasks, portal access, files and billing history with it, which is too much to hang on a chat confirmation, so it is not offered to an assistant. That one is a product-safety call and could be revisited. Account administration — inviting or removing members, changing roles, the subscription itself — is a different thing: it is absent by design and stays that way.

What can I use today?

Uku API v3 and the Uku CLI are available now on the Elite plan, and between them they already give Claude, ChatGPT, Cursor and your own agents a way to operate Uku. See https://getuku.com/agents/ for how firms set that up.

Can one client's data end up in another client's work?

No. A connection is bound to one firm, and over OAuth the firm comes from the key itself — a connecting client cannot point it at anyone else. Inside your firm the assistant inherits the permissions of the person who connected it, so a client that person cannot open in Uku is a client the assistant cannot open either.

Does this cut our billable hours?

It changes what you bill for, and it makes that easier to show. The assistant logs its time in Uku like anyone else, and every action it takes is in the audit trail, so the work is visible rather than absorbed. Circular 230 §10.27 asks that savings from automation be passed on openly; a firm that can show exactly what was automated is in a better position to have that conversation than one that cannot.

How do I get access to the MCP server?

It is in beta, and we are adding firms one at a time so we can watch how it behaves on real data. Ask us and we will walk you through connecting it — the endpoint opens for your firm once access is granted.

Let your AI run the firm's work — your money stays yours.

On the Elite plan, alongside Uku API v3. Compare the plans