ComplyEaze Bridge MCP server

ComplyEaze Bridge

<!-- llms:begin --> ComplyEaze Bridge is an MCP server that connects Claude Desktop to the TallyPrime running on your own computer. It is built for CA firms and accountants. You can ask about outstanding receivables and payables with ageing, the trial balance, ledger movement and vouchers. It checks ledger names before you post, and it prepares Journal, Payment, Receipt and Contra vouchers as a file. If you turn posting on in the extension, it posts them one at a time, after you approve each one.

Current release: <!-- managed:current-release -->mcp-v0.4.1 (2 October 2026)<!-- /managed:current-release -->, for Windows x64 and Apple Silicon Macs. We check each release before we publish it: the release check confirms that each package launches, lists its tools and parses a synthetic encrypted bank statement. It does not run against TallyPrime, and nothing we can run covers every Tally edition, set of books or setting. What has been run against a real TallyPrime, and what has not, is listed below. Install it · What changed · Security and privacy

Not yet code-signed; your computer may warn you before opening it.

Try asking (on a test company first):

• "List the loaded companies."
• "Show the outstanding receivables and payables, with ageing, as of 31 March."
• "Show the trial balance for 1 April to 31 March."
• "Check these ledger names against the book before I post: …"

How it handles your books

a loopback address, so it cannot be pointed at a remote Tally host. It cannot tell whether that local port is forwarded to another machine; do not forward one across the internet. The Tally connection sends nothing to a ComplyEaze server.

• Local connection only. It talks to Tally's own XML gateway on

rest of the conversation: company names, party names and amounts. You can mask party names or drop narration. Amounts are always sent. See Before you use it with client data below.

• Your AI provider sees what the assistant reads, just as it sees the

earlier version, check the setting: an earlier default may still be saved as on. When you turn posting on, each voucher waits for your approval in a separate ComplyEaze Bridge window. No Bridge tool lets the assistant approve it, and an approval counts only when that window returns a fresh one-time token. After posting, the voucher is read back from Tally so you can see what landed. Three known limits remain: ComplyEaze Bridge cannot undo a posted voucher (you correct it in Tally); a company renamed to, or loaded under, the target company's name (or one differing only in case or spacing) just after its last check could still receive the voucher, if it has the voucher's ledgers, and ComplyEaze Bridge cannot always say where it went or prevent it; and a ledger renamed and replaced in that same moment could receive the entry, and not every such change is noticed. Read Before you turn on posting first.

• Posting is off by default in the extension. If you installed an

identifier, and a fingerprint of what was asked and of what came back, written whether the call succeeds or is refused.

• Tool calls leave receipts in a log on your computer: the company's Tally

ComplyEaze Bridge Terms of Use (version 2026-10) in its settings, and every tool refuses with termsnotaccepted until you do.

• You accept the Terms of Use first. The extension asks you to accept the

• Open source under Apache-2.0.

What has been run against a real TallyPrime

Shortened. The full README is on GitHub.