← The work

Accounting integration Beta

Billy MCP

Connect an AI client to your Billy account through local MCP tools and a skill that guides the accounting workflow.

An independent, unofficial project. Not affiliated with, endorsed by or sponsored by Billy.

A read-only example with sample data

Start with a question you can check.

“List invoices from my test account with their due dates and remaining balances.”

The client can use the invoice read tools to retrieve the records, then present the fields for inspection. For example:

First establish what we are looking at.

For this example, the scope is one test account and invoices dated in November 2026, shown in DKK. In a real session I would identify the account, company and period before reading the records. If several profiles exist, each read needs the intended profile.

Keep the records and the conclusion apart.

The rows below are invented. They show the sort of fields an invoice read can return, not a completed check of an account.

A read-only example with sample data
InvoiceDue dateRemaining balance (DKK)
10071,250.00
10080.00

Fictional invoices shown to explain the workflow. This is not a live response, an account reconciliation or a judgement about payment status.

What these two rows show

Invoice 1007 has a displayed remaining balance of DKK 1,250.00 and a due date of 20 November. Invoice 1008 has a displayed zero balance. Those observations stay attached to those records.

What they do not establish

Two rows do not establish that every relevant invoice was read, that a bank statement agrees, or that a balance reflects the latest payment. I would follow pagination, record what was covered and check the result in Billy.

The tools fetch data. The skill guides the work.

An accounting question can need more than a convenient table. The bundled skill tells the assistant to preserve the account and period, track its sources and make missing evidence visible.

  1. Read the whole relevant set

    If another page of results is unexamined, say the result is incomplete. Not finding a record in a partial response is different from checking all relevant records and finding none.

  2. Explain a discrepancy

    Keep the invoice record, the bank evidence and any interpretation distinct. If they disagree, identify what needs checking before proposing a correction.

  3. Make a separate decision about a change

    A read-only question authorizes no bookkeeping update. Any proposed change needs a specific account and intended effect, the relevant tools enabled, local approval and verification afterwards.

That is the useful combination for me: access to the records, plus a working method that makes the assistant explain what it knows. It still needs independent checking by the person responsible for the books.

Read the bundled accounting workflow ↗

A local connection to your Billy account.

I built the Billy Plugin around API MCP, combining a local MCP server with an accounting workflow skill. A compatible AI client can use the Billy API through those tools.

The beta targets macOS on Apple Silicon. It reads your Billy credential from the local credential store and calls Billy directly. This project runs no hosted intermediary; the AI client is a separate part of the workflow.

Keep accounting judgment with a person.

Start with a non-production Billy account and the default read-only policy. If you need to make a change, enable only the relevant tools. Policy changes and every create, update or delete request require local native approval.

Check every accounting result and change independently against Billy itself. This beta’s automated checks and approval dialog do not establish bookkeeping correctness. Leave write tools disabled when you do not need them, and follow the repository’s current operating guidance.

Ask me about Billy MCP →