ComplyEaze Bridge: TallyPrime MCP server for Claude Desktop
ComplyEaze Bridge is an open-source (Apache-2.0) MCP server that connects Claude Desktop to the TallyPrime (also written Tally Prime) running on your own computer. It is built for chartered accountants, CA firms and accountants. It reads your books; from a password-protected SBI, HDFC, Union Bank of India or Bank of Baroda statement PDF it proposes Payment, Receipt and Contra vouchers, and once every ledger name is exact and every question is answered it writes them to a file that you import in TallyPrime yourself. What Claude reads from your books goes to your AI provider as part of the chat. You can ask about the trial balance, outstanding receivables and payables with ageing, ledger movement and vouchers, the purchase and sales registers, the stock summary, and the Profit and Loss and Balance Sheet (a book with stock items is read only when Tally's own closing stock closes every gap). It checks ledger names before you post, and prepares Journal, Payment, Receipt and Contra vouchers as an import file that you review and import into TallyPrime yourself. Posting is off by default in a new install, so as installed it never posts to TallyPrime: it reads from it and prepares files on your computer. If you turn posting on in the extension, it posts one voucher at a time, or a saved batch of up to 50, after you approve each post.
Tally Solutions also offers its own TallyPrime MCP plug-in for Claude Desktop; its help pages (last updated 18 September 2026) list tools in six groups: company, master, accounting, inventory, outstanding and transaction. ComplyEaze Bridge is not made by, or affiliated with, Tally Solutions, and we have not run the two side by side. TallyPrime also has its own Bank Statement import, which takes statement files in the formats Tally lists for each bank.
Current release: mcp-v0.6.1 (27 October 2026),
for Windows x64 and Apple Silicon Macs, as a Claude Desktop extension (an .mcpb
file); it has not been run in other MCP clients. 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 ·
How to connect Claude to TallyPrime ·
How to choose a TallyPrime MCP server safely
Not yet code-signed; your computer may warn you before opening it.
Get it: the Download page
offers the file for your computer; compare it with its .sha256 file as
the install guide says. ComplyEaze Bridge does not
update itself, so look for a newer version on the
releases page.
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: …"
At a glance, release 0.6.1.
- You can ask for outstanding receivables and payables with ageing, the trial balance, the vouchers in a date range (found by number, reference, narration or amount, and added up by ledger, month, voucher type, group or primary group; checked on one synthetic book, not a large one), Tally's own Cash Flow for whole months (shown only when its net total ties to the trial balance; not a cash flow statement under AS 3; tried on two synthetic books), one ledger's movement, Tally's own month-wise Sales or Purchase Register for whole months (not tied to the vouchers; read on one synthetic book), Tally's own Negative Stock and Negative Ledgers lists for a window (being listed is not a finding; synthetic books only), and the vouchers of one type that Tally marks Uncertain in its GSTR-1 (a Sales type, measured on one synthetic book).
- Partly: profit and loss and the balance sheet (a book with stock items is read only when Tally's own closing stock closes every gap, measured on one synthetic book; a book with several currencies is refused); closing stock value at 31 March, and its closing quantity where Tally's own Stock Summary shows the item on a line of its own, on small books, and only the year to 31 March 2026 has been checked; and a file of Payment, Receipt and Contra vouchers from a password-protected SBI, HDFC, Union Bank of India or Bank of Baroda PDF statement, which you check and import in Tally yourself. It creates no ledger, it cannot build onto a Cash-in-Hand ledger, and it has not yet been run on a real bank statement.
- Not in this release: GST returns or GSTR-2B matching, making sales or purchase invoices or GST entries, tax-audit flags (one test, the cash share of receipts and payments against the s.44AB(a) limit, is off by default and not yet run against a live TallyPrime), and Tally's Funds Flow and Ratio Analysis reports.
"You can ask" means it answered on the books and builds we ran it on; the program inside the published Windows x64 0.6.1 file (checked against its .sha256 file) has had one read-only run against a live TallyPrime 7.2 Silver, on one Windows computer on 27 October 2026, started directly by our test client rather than installed in Claude Desktop (it reported version 0.6.1, read Tally's status, the company list and the ledger masters of one synthetic company; nothing was posted); the macOS file has not been run against TallyPrime; our one recorded run of the published 0.6.0 file against a live TallyPrime posted one Contra to a synthetic company on one Windows computer on 16 October 2026 (#1780) and read it back; the other 0.6.0 posts ran on a release-candidate build and a rehearsal build. Very large books can fail or take longer than the assistant waits, and a book with several currencies is read only in part. Check any figure you rely on against Tally. The Questions page has the full table and its limits.
Its tools. In name order; release 0.6.1 installs 32 of them, 31 offered by default (audit_test_run appears only when its setting is on), and gst_by_counter_ledger is in source, not yet in a published build. None of them changes your TallyPrime books; with posting on, two more appear, described below the table. Every call adds a receipt line,
with no figures, to a log on this computer.
| Tool | What it gives you | What it writes besides that receipt |
|---|---|---|
audit_test_run |
Off by default (setting Allow tax-audit test runs). One tax-audit test run on the company's own books for a date range, today only the cash share of receipts and payments against the s.44AB(a) limit: figure and finding ids with their values, confidence and clauses, and the count of any failed book check; no ledger name, no voucher, and refused while a redaction setting is on. You name the cash and bank groups; the period must lie in 2025-26. Books only, not a tax opinion | Nothing |
balance_sheet |
The Balance Sheet for a date range, by primary group, from TallyPrime’s Trial Balance (a book with stock items is read only when Tally’s own closing stock closes every gap) | Nothing |
build_import_xml |
Checks a Journal, Payment, Receipt or Contra batch and writes an import file | An import file and a ledger record on this computer |
cash_flow |
Tally’s own Cash Flow for whole months: the month-wise movement of the cash and bank ledgers, returned only after its net total matches the trial balance; the split into months is Tally’s own and is not checked (not a cash flow statement under AS 3) | Nothing |
company_features |
Three settings the company’s record in Tally holds today (cost centres, GST and batch-wise stock; each yes, no or not reported) and the currency symbol; no ledger, voucher, amount or narration. Each of the three settings equalled Tally’s F11 screen on three synthetic books, not on this company; a setting changed inside a sitting has not been measured | Nothing |
egress_log |
The receipts ComplyEaze Bridge keeps of its own tool calls, with no figures | Nothing |
gst_by_counter_ledger |
For a period, the GST the books record on ledgers under Duties & Taxes, totalled per counter ledger: the one Purchase Accounts, Direct Expenses, Indirect Expenses or Fixed Assets ledger on a purchase, debit note, journal or payment with a supplier on it, named with its GUID, debit and credit side apart, per head; every other voucher with GST is set aside under a named reason with its own totals. Books only, not a return figure or an eligibility decision; measured on fourteen vouchers typed on Tally's screen in one synthetic book | Nothing |
gst_status |
Tally’s own GSTR-1 status flags on the vouchers of one voucher type in a period of at most 93 days: for each voucher its number, date, a status (included, uncertain, excluded, not in return, cancelled, optional or post-dated; for the last three also what the three status flags read) and whether a person accepted it as it stands; no amount, party, ledger or narration. A status is Tally’s own flag and not a judgement of ComplyEaze Bridge. Measured on one synthetic book of TallyPrime 7.1 Silver, where excluded has not been observed |
Nothing |
gst_uncertain_vouchers |
The vouchers of one voucher type (a Sales type is what was measured) in a period of at most 93 days that Tally marks Uncertain in its GSTR-1, and the ones a person accepted as they stand: for each its number, date, party ledger, invoice total (without its sign, with the side) and Tally’s identifiers, and the line a CA reads before filing, which names the voucher type it covers and is withheld when no voucher was read, none is uncertain, or a voucher it depends on could not be read. The party and the total are returned to the assistant, and mask_parties masks the party and not the total. The reason for uncertainty is not read, and bills missing an HSN/SAC are not split out. Measured on one synthetic book of TallyPrime 7.1 Silver, before and after one Accept As Is; item invoices, a registered buyer, credit notes, foreign currency and several accepts at once are not measured |
Nothing |
ledger_masters |
Ledgers with their opening balances; optionally GSTIN, PAN and other party details | Nothing |
ledger_movement |
A ledger’s opening, debits, credits and closing for a period | Nothing |
list_companies |
The companies loaded in TallyPrime (start here) | Nothing |
local_data_report |
What ComplyEaze Bridge keeps on this computer | Nothing |
masters |
Voucher types, godowns, units, stock groups, stock items, cost centres, cost categories or account groups | Nothing |
month_register |
Tally’s own month-wise Sales Register or Purchase Register for whole months: one row per month with Tally’s debit, credit and closing columns exactly as printed; not tied to the vouchers or the trial balance, and not compared with Tally’s register screen | Nothing |
negative_ledgers |
Tally’s own Negative Ledgers list for a window, as Tally returns it and compared with no other report; an empty list is not a finding | Nothing |
negative_stock |
Tally’s own Negative Stock list for a window, each item with its quantity, rate and value as Tally prints them, compared with no other report; being listed is not a finding, and an empty answer is not one either | Nothing |
outstandings |
Receivables and payables with ageing, the top parties and the open bills | Nothing |
parse_bank_statement |
Reads a password-protected SBI, HDFC, Union Bank of India or Bank of Baroda statement PDF and proposes Payment, Receipt and Contra vouchers | A private proposals file on this computer |
profit_and_loss |
The Profit and Loss for a date range, by primary group (a book with stock items is read only when Tally’s own closing stock closes every gap) | Nothing |
purchase_register |
Purchase and Debit Note vouchers that touch a ledger under Duties & Taxes, as the books record them (not a GST return) | Nothing |
read_evidence |
ComplyEaze Bridge’s own recent reads, as fingerprints, with no figures | Nothing |
sales_register |
Sales and Credit Note vouchers that touch a ledger under Duties & Taxes, as the books record them (not a GST return) | Nothing |
statement_tie_out |
Whether the bank ledger stands where a parsed bank statement says it stood at the start and at the end of the statement's dates, or of whole calendar months of it: three gaps and the dates; the balances themselves are not returned | Nothing |
stock_summary |
The closing stock value of each item as of a 31 March, and its closing quantity where Tally's own Stock Summary shows the item on a line of its own; an item inside a stock group returns no quantity; small books only (a book with many masters of any kind is refused, and so is any other date); only the year ending 31 March 2026 has been checked | Nothing |
tally_status |
Whether TallyPrime’s gateway answers, and which companies are loaded | Nothing |
trial_balance |
The ledger-wise Trial Balance for a date range | Nothing |
validate_masters |
Checks ledger names against the live book before you build an import file | Nothing |
verify_import |
Reads back a batch you imported by hand in TallyPrime | Proof files and status records on this computer |
voucher_presence |
Which proposed vouchers are already in the book | Nothing |
voucher_read_cost |
Before a call to vouchers, ledger_movement or verify_import: the most counting reads (reads that count the period’s vouchers by walking the whole book, before any voucher is fetched) it will make, and the least time the gaps between them take. It follows how many voucher changes the book has seen (Tally’s counter, its voucher mark), not the period, so a narrower period does not lower it and N one-day calls pay it N times. Derived and not measured, and not an estimate of how long the call takes |
Nothing |
voucher_schema |
The voucher-file format, without asking TallyPrime | Nothing |
vouchers |
The vouchers in a period. Search by voucher number, reference, narration or amount, and summaries by ledger, month, voucher type, group or primary group, are in release 0.5.0 and not in 0.4.2 (search and the first three summaries checked once, and the group and primary-group summaries in a second run, on a synthetic book of 67 vouchers; not checked on a large book) | Nothing |
With posting turned on in the extension, two more appear: post_import posts one saved voucher, or a saved batch of 2 to 50,
after you approve it in a ComplyEaze Bridge window (for a batch, its summary), and acknowledge_post_review asks you, in its own window, to record that you reviewed a posted voucher
whose ledger now points to a different master.
How it handles your books
- Local connection only. It talks to Tally's own XML gateway on 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.
- Your AI provider sees what the assistant reads, just as it sees the rest of the conversation, including company, party and ledger names, amounts, dates, narrations, references, GSTINs and, when it reads ledger details, PAN, bank account numbers, IFSC, MSME or Udyam registration numbers, email, phone and address, and, when it builds a voucher file, that file's local path (which can include your computer user name). The setting takes one value, not both: shorten party and ledger names and bank account numbers to their first two and last two characters (four or fewer become “…”), or drop narrations. Neither hides amounts, company names, PAN, GSTIN, IFSC, MSME or Udyam registration numbers, contact details or references, or the last four digits of a bank statement's account number, and a shortened name can still be identified, not least from the GSTIN or PAN sent beside it. See Before you use it with client data below.
- Posting is off by default in the extension. Note that this is a new setting: if you turned posting on in an earlier version, turn it on again. When you turn posting on, each post waits for your approval in a separate ComplyEaze Bridge window (for a batch, its summary). On Windows that window also takes the keyboard: in a test of the published 0.6.0 (a full-screen Tally, one screen, #1780) a typed n declined it and a typed y approved it, so when you ask for a post, stop typing in Tally until you have answered it with the mouse. 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. Four 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; a ledger renamed and replaced in that same moment could receive the entry, and not every such change is noticed; and the approval window covers only ComplyEaze Bridge, so another Tally connector in the same Claude Desktop that can change entries can do so without it. Read Before you turn on posting first.
- Tool calls leave receipts in a log on your computer: the company's Tally identifier, and a fingerprint of what was asked and of what came back, written whether the call succeeds or is refused.
- You accept the Terms of Use first. The extension asks you to accept the
ComplyEaze Bridge Terms of Use (version 2026-10.1) in its settings, and every
tool refuses with
terms_not_accepteduntil you do. (In 0.5.0, after an update from 0.4.2, Claude Desktop may not start the extension: on a Mac with an error that does not mention the Terms, on one Windows computer with no error; #1413.) - Open source under Apache-2.0.
What has been run against a real TallyPrime
Each line below is recorded in the repository or on the linked issue or pull request, unless marked as reported by the owner. Each ran on licensed TallyPrime Silver 7.1 and synthetic companies unless stated. The MCP guide and ADR 0004 hold the full record.
- Reads: 27 checks on an unpublished macOS arm64 build (PR #228), recorded in the 6 September 2026 assessment. Some later reads were also run live on development builds, for example the trial balance on a debug build with synthetic companies (#246, whose record does not name the Tally release or licence tier). Not every read has its own recorded live run.
- Posting one Journal, on a de
