BUSY MCP Server

Ask Claude, ChatGPT, Cursor or any AI assistant about your BUSY Accounting books in plain language:

"How is the business doing this year?" "Which customers are overdue by more than 60 days, and what are their phone numbers?" "Show stock in the Branch godown and the batches expiring this quarter." "Who deleted vouchers last month?"

busy-mcp is a read-only Model Context Protocol server. It reads BUSY's own company files directly; it cannot change anything in BUSY.

Status 1.1. This release is built on BUSY's schema as decoded from real BUSY databases and production integrations (docs/busy-internals.md). It has been verified against a test company that uses BUSY's exact table layout, but not yet against every BUSY release. Run busy-mcp doctor and compare one trial balance with BUSY before relying on it.

Install (Windows, about 5 minutes)

1. Install Python 3.10 or newer from python.org. Tick Add python.exe to PATH.

   • BUSY usually uses 32-bit Access drivers, so the 32-bit ("Windows installer (32-bit)") Python is the easiest choice.

2. Download this project (green Code button on GitHub → Download ZIP), unzip it (e.g. to C:\Busy_MCP), and double-click install.cmd.

The installer sets everything up and then runs busy-mcp setup, which:

• finds your BUSY data folder (or SQL Server) automatically and checks it can be read;

• asks which company to use by default, if you have several;

• adds BUSY to Claude Desktop for you, after backing up the existing settings.

Restart Claude Desktop and ask: "Show my BUSY dashboard for this year."

If anything goes wrong, run busy-mcp doctor. It explains in plain words what works and what to fix. For Cursor, VS Code, Claude Code or ChatGPT, see docs/clients.md.

Related MCP server: HLedger MCP Server

What it can read

That's 44 tools and 5 ready-made workflows (health check, receivables follow-up, month-end, stock, audit). Full list: docs/tools.md. Coverage by BUSY feature: docs/feature-coverage.md.

Fast by design

The first question builds an in-memory index of every account's and item's daily movements. After that, trial balances, P&L, balance sheets, aging and stock summaries for any period take milliseconds. The index is rebuilt automatically within seconds of anyone saving a voucher in BUSY. On a 50,000-voucher test company, reports drop from about 320 ms each to 4–40 ms (docs/performance.md).

Safe by design

• Nothing can be written. Every tool is read-only, and connections are opened read-only.

• Free-form SQL is limited to one SELECT, with no external files and no system calls.

• Tables and columns that can hold passwords (e.g. BUSY's Config, where GST portal credentials may be stored) are blocked or masked.

• The HTTP mode for remote clients requires a token.

Details in SECURITY.md.

Known limitations

• Stock value: closing-stock value follows BUSY's valuation method and isn't computed. Quantities are exact. P&L and balance sheet are ledger-based and say so.

• Labels: a few voucher-type labels are single-source and shown as "(inferred)". Override them with BUSY_VCH_TYPE_NAMES.

• Opening balances: if BUSY's year-end carry-forward wasn't run, the new year's opening balances are zero. The trial balance warns about this.

For developers

pip install -e ".[dev]"
ruff check src tests && mypy && bandit -q -r src -c pyproject.toml
pytest --cov
python scripts/benchmark.py

• Architecture: docs/architecture.md

• Contributing: CONTRIBUTING.md

• Release notes: CHANGELOG.md

This is an independent project, not affiliated with Busy Infotech Pvt. Ltd. BUSY is their trademark. Check important figures against BUSY before you use them for filings.