Skip to main content

Finance · MCP connector

Six years of books moved through an MCP connector, with a dry run, a journal and an undo

Running since August 2026, on our own books and a partner company'sWorking case · under NDA

It connects an AI assistant to an in-house finance system that had no connector. We don't name the system or the company. Bulk rows stay on the machine, and a person runs every write.

A walkthrough with sound. It's a reconstruction with invented figures, because these are real books. The steps and the headline numbers are real.

In numbers

Years of books moved
6
Days to migrate
4
Transactions reconciled
7,512

August 2026, from the migration files and the reconciliation report.

What it produces

  • Diagram: a file of 3,000 rows goes from the user's machine straight to the finance system, around the AI agent, which gets one short call and a count back. Invented figures.
    Illustration · invented figuresRows stay on the machineThe agent gets one short call and a count. The rows go straight to the finance system.
  • A dry run card: would write 2,987, invalid 13, with the invalid rows highlighted and a note that nothing has been written yet. Invented figures.
    Illustration · invented figuresDry run firstWhat would be written and what's invalid, before anything changes.
  • An import that stopped at 1,640 rows after a lost connection, then ran again: 1,640 skipped by the journal, 1,347 written, no duplicates. Invented figures.
    Illustration · invented figuresResume without duplicatesAfter a dropped connection, the journal skips the rows already written.
  • A reconciliation of 7,512 transactions across 3 companies, with three critical defects found in the finance system listed in red.
    Illustration · invented figuresReconciled to the source7,512 transactions across three companies. Three critical defects found in the finance system itself.

How it works

  1. Step 1: Dry run

    Shows what would be written and which rows are invalid. Nothing changes.

  2. Step 2: A person says go

    Nothing is written until someone runs it for real, in a session they can see.
    A person

  3. Step 3: Write in slices

    Resumes where it stopped. The journal skips what's already there.

  4. Step 4: Reconcile

    Totals are compared with the source. A mismatch is a finding, not a footnote.

Works with

  • Finance system API
  • Claude, through MCP
  • Local machine

Want a connector like this?

We start with read-only access to your system and show the connector working before anything writes.

Request a free assessmentSee all cases