ComplyEaze Bridge is an open-source (Apache-2.0) TallyPrime MCP server designed for Claude Desktop, aimed at chartered accountants, accounting firms, and bookkeepers. It connects to your locally running TallyPrime, allowing Claude to read ledger data and assist in preparing vouchers.
Purpose It is mainly used to read TallyPrime ledgers locally and answer questions about trial balance, receivables and payables and their aging, ledger movements and vouchers, purchase and sales registers, inventory summaries, profit and loss statements, and balance sheets. Among these, ledgers containing inventory items are expected to be rejected when querying the profit and loss statement and balance sheet. It also checks whether ledger names are correct before posting.
Main capabilities For the scenario of converting bank statements into TallyPrime vouchers, it can extract information from password-protected SBI, HDFC, or Union Bank of India statement PDFs, propose Payment, Receipt, and Contra voucher suggestions, and prepare Journal, Payment, Receipt, and Contra vouchers as import files for you to review and import into TallyPrime yourself. The posting feature is disabled by default, so after installation it will never post vouchers to TallyPrime; once enabled, each voucher requires your approval in a separate ComplyEaze Bridge window, the approval window returns a one-time token, and no Bridge tool allows the assistant to approve on its own. After posting, vouchers are read back from Tally so you can confirm what was actually written.
How to use he current version is mcp-v0.5.1 (October 9, 2026), available for Windows x64 and Apple Silicon Mac, provided as a Claude Desktop extension (.mcpb file), and has not yet been run in other MCP clients. During installation, the extension will ask you in settings to accept the ComplyEaze Bridge Terms of Use (version 2026-10.1); until accepted, all tools will reject calls with terms_not_accepted. It communicates with Tally's XML gateway via the local loopback address and cannot point to a remote Tally host. Tool calls leave a receipt in the local log, including the company's Tally standardidentifiers and fingerprints of requests and responses, whether the call succeeds or is rejected.
Use cases Suitable for accountants and firms that need to read TallyPrime data locally and want AI-assisted generation of voucher import files. All operations are performed locally, but the content Claude reads from the books is sent to the AI provider, including company, party and ledger names, amounts, dates, narrations, reference numbers, GSTIN, and, when reading ledger details, PAN, bank account numbers, IFSC, MSME or Udyam registration numbers, email, phone and address, as well as local paths when building voucher files. In settings, party and ledger names and bank account numbers can be shortened (keeping only the first two and last two characters, with four or fewer shown as "..."), or narrations can be removed, but these settings cannot hide amounts, company names, PAN, GSTIN, IFSC, MSME or Udyam registration numbers, contact details, reference numbers, or the last four digits of bank statement account numbers, and shortened names may still be identifiable.
Limitations The posting feature is off by default, and once enabled each voucher requires separate approval. Known limitations include: posted vouchers cannot be undone (they must be corrected in Tally); a company that is renamed or loaded as the target company name (or differs only in case or spaces) at the moment after the last check may still receive vouchers; a ledger that is renamed and replaced at the same moment may also receive entries; the approval window covers only ComplyEaze Bridge, and other Tally connectors in the same Claude Desktop can still modify entries without its approval. In addition, the tool is not yet code-signed, and the system may warn during installation.
Release status and verification Current release is mcp-v0.5.1, installing 23 tools, of which company_features, gst_status, statement_tie_out and voucher_read_cost exist in the source code but are not yet included in the released build. When the posting feature is enabled, two additional tools appear: post_import and acknowledge_post_review. Release checks confirm that each package can start, list tools and parse a synthetic encrypted bank statement, but they do not run against TallyPrime. Some features have been tested on real TallyPrime; for specific test records and limitations, please refer to the notes in the repository.
Security and privacy It communicates only with the Tally XML gateway on the local loopback address, and cannot determine whether that local port is forwarded to another machine, so do not forward that port over the internet. The Tally connection does not send anything to ComplyEaze servers. Please read the terms of use before use, and try it first on a test company.
