Why I built a headless accounting engine and why MCP changes everything

The problem I kept hitting

Every accounting system I tried locked me into their UI. As someone running multiple businesses, I needed consolidated financials across entities, but every tool wanted me to work the way they designed it — not the way my businesses actually operate.

So I built Crane Ledger: a full double-entry accounting engine with no UI attached. You access it via REST, GraphQL, or MCP and build whatever interface makes sense for your use case.

Why MCP is the part that excites me most

With MCP support, any AI assistant — Claude, Cursor, Windsurf — gets native access to the accounting engine. You can say “create a journal entry for the $5,000 rent payment” or “show me the P&L for Q1” and it just works. No API docs to read, no SDK to learn. Natural language accounting.

For anyone vibe-coding a product, this means you can embed a full accounting system into your app without building one from scratch.

What I would love feedback on

I am curious what this community thinks about a few things:

1. If you could build an accounting system for a specific niche (farming, real estate, construction) — what would you build?

2. For those managing multiple entities or LLCs — how are you handling consolidated financials today?

3. What is holding you back from replacing QuickBooks with something custom?

Docs are at https://craneledger.ai/docs if you want to dig in. Happy to answer any technical questions.