ComplyEaze Bridge: TallyPrime MCP server for Claude Desktop

ComplyEaze Bridge: TallyPrime MCP server for Claude Desktop

ComplyEaze Bridge is an open-source (Apache-2.0) TallyPrime MCP server forClaude Desktop. It connects Claude Desktop to the TallyPrime running on yourown computer, and it is built for chartered accountants, CA firms andaccountants. What Claude reads from your books goes to your AI provider as partof the chat. You can ask about the trial balance, outstanding receivables andpayables with ageing, ledger movement and vouchers, the purchase and salesregisters, the stock summary,and the Profit and Loss and Balance Sheet (a book with stock items is expectedto be refused for these two). It checks ledger names before you post. For bankstatement to TallyPrime vouchers, it proposes Payment, Receipt and Contravouchers from a password-protected SBI, HDFC or Union Bank of India statementPDF, and it prepares Journal, Payment, Receipt and Contra vouchers as an importfile that you review and import into TallyPrime yourself. Posting is off bydefault, so as installed it never posts to TallyPrime: it reads from it andprepares files on your computer. If you turn posting on in the extension, itposts vouchers one at a time, after you approve each one.

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. ComplyEazeBridge is not made by, or affiliated with, Tally Solutions, and we have not runthe two side by side. TallyPrime also has its own Bank Statement import, whichtakes statement files in the formats Tally lists for each bank.

Current release:

for Windows x64 and Apple Silicon Macs. We check each release before wepublish it: the release check confirms that each package launches, lists itstools and parses a synthetic encrypted bank statement. It does not run againstTallyPrime, and nothing we can run covers everyTally edition, set of books or setting. What has been run against a realTallyPrime, 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.

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: …"

Its tools. Release 0.4.2 installs these 22, in name order. None of them changes your TallyPrime books, and every call adds a receipt line,with no figures, to a log on this computer.

With posting turned on in the extension, two more appear: post_import posts one saved voucher after you approve it in aComplyEaze Bridge window, and acknowledge_post_review asks you, in its own window, to record that you reviewed a posted voucherwhose ledger now points to a different master.

How it handles your books

• Local connection only. It talks to Tally's own XML gateway ona loopback address, so it cannot be pointed at a remote Tally host. It cannottell whether that local port is forwarded to another machine; do not forwardone across the internet. The Tally connection sends nothing to a ComplyEazeserver.
• Your AI provider sees what the assistant reads, just as it sees therest of the conversation: company names, party names and amounts. You canmask party names or drop narration. Amounts are always sent. SeeBefore you use it with client data below.
• Posting is off by default in the extension. If you installed anearlier version, check the setting: an earlier default may still be saved ason. When you turn posting on, each voucher waits for your approval in aseparate ComplyEaze Bridge window. No Bridge tool lets the assistant approveit, and an approval counts only when that window returns a fresh one-timetoken. After posting, the voucher is read back from Tally so you can see whatlanded. Four known limits remain: ComplyEaze Bridge cannot undo a postedvoucher (you correct it in Tally); a company renamed to, or loaded under, thetarget company's name (or one differing only in case or spacing) just afterits last check could still receive the voucher, if it has the voucher'sledgers, and ComplyEaze Bridge cannot always say where it went or prevent it;a ledger renamed and replaced in that same moment could receive theentry, and not every such change is noticed; and the approval window coversonly ComplyEaze Bridge, so another Tally connector in the same Claude Desktopthat can change entries can do so without it. Read Before you turn onposting first.
• Tool calls leave receipts in a log on your computer: the company's Tallyidentifier, 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 theComplyEaze Bridge Terms of Use (version 2026-10.1) in its settings, and everytool refuses with terms_not_accepted until you do.
• 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 pullrequest, unless marked as reported by the owner. Each ran on licensedTallyPrime Silver 7.1 and synthetic companies unless stated. TheMCP guide andADR 0004 hold the full record.

• Reads: 27 checks on an unpublished macOS arm64 build (PR #228), recorded inthe 6 September 2026 assessment.Some later reads were also run live on development builds, for example thetrial balance on a debug build with synthetic companies (#246, whose recorddoes not name the Tally release or licence tier). Not every read has its ownrecorded live run.
• Posting one Journal, on a development build from 22 September 2026(issue #579),and a Payment, a Contra and two Receipts (one of three entries) with theapproval dialog on macOS (PR #600),each read back as posted. These builds predate the release published on26 September 2026 (version 0.3.0).
• Native posts of ten batches on licensed TallyPrime Gold 7.1, in one sessionon 28 September 2026, on a development build and one client book (the importrequest was captured for nine of them); their approval step was not recorded(protocol reference).
• The published 0.3.0 package on Windows x64, in Claude Desktop (with no paid plan;we make no claim about other plans): reads only, against licensed TallyPrimeGold 7.1 with one client book, on 28 September 2026, in a session separatefrom the development-build posting above (reported by the owner; no logs werekept).
• A candidate build of 0.4.0 on Windows 11, on 1 October 2026 (the build CIproduced for the version pull request: the same code as the release apartfrom a comment in one test file). The maintainer installed it in ClaudeDesktop with a new Claude account that has no paid plan, against licensedTallyPrime Silver 7.1 holding one synthetic company. With the Terms settingoff, a call was refused and nothing was read. With it on, tally_status,vouchers, validate_masters, purchase_register, stock_summary andlocal_data_report answered. One voucher post was declined in the Windowsapproval window and nothing was sent; one was approved, and one Journal wasposted and then verified by verify_import. The same candidate's macOS buildwas started and read the company list, and in Claude Desktop on macOS itstools loaded in a chat. The record is the maintainer's dated notes andscreenshots, kept privately. This was one run, not a controlled test of eachkey of the window.
• A build of 0.4.1 on a Mac, on 2 October 2026. What was run: the package CI builtfor the version pull request, not the published file. The maintainer installedit in Claude Desktop over an installed 0.4.0, as an upgrade; the Terms settingand the other settings carried over, and the extension's server processstarted again on its own after the upgrade (its start time was read from theprocess list). tally_status and list_companies then answered againstlicensed TallyPrime Silver 7.1 holding the lab's own synthetic companies.The record is our dated notes, kept privately. What was not run:the published file is built again on another runner, and its program filediffers from the one tested. We ran both builds without Tally: each reportsversion 0.4.1, lists 21 tools and gives the same answer to tally_status. Wehave not installed the published file in Claude Desktop.
• A build of 0.4.2 on a Mac, on 3 October 2026. What was run: the package CIbuilt for the release candidate, not the published file. The maintainerinstalled it in Claude Desktop on a Mac that had 0.4.1: it did not replace0.4.1 but installed as a second extension (the author line changed in 0.4.2,and Claude Desktop builds an extension's identity partly from it); thesettings did not carry over. tally_status and list_companies thenanswered against licensed TallyPrime Silver 7.1 holding the lab's owncompanies. The record is our dated notes, kept privately. What was not run:the published file is built again on another runner, and its program filediffers from the one tested. We ran the published Mac file without Tally: itreports version 0.4.2, lists 22 tools with posting off (24 with it on), andrefuses a call with the Terms setting off. We have not installed thepublished file in Claude Desktop, and nobody on our side has installed theWindows package in Claude Desktop on a Windows PC.
• The bank-statement path through its fourth step, on a Mac, on 4 and 5 October2026, with that same CI-built 0.4.2 candidate (installed on 3 October; not thepublished file), against licensed TallyPrime Silver 7.1 holding the lab's ownsynthetic companies. The synthetic HDFC-format statement parsed (six rows, itstotals matched the figures supplied); the name check found no "Suspense" ledgerand building the file was refused, with no file written; after "Suspense" wascreated in Tally by a separate one-ledger import, outside this tool, a file ofsix vouchers was built. We have not importedthat file or read it back, and no real statement has been run. The record is ourdated notes, kept privately.

Not yet run by us in a controlled test: posting with a published packageagainst a live TallyPrime; each way of declining in the Windows approval window(one was tried); the tools answering through Claude Desktop on macOS after theTerms are accepted (tally_status and list_companies answered on a CI buildof 0.4.1 and again on a CI build of 0.4.2); posting on TallyPrime Education; posting on TallyPrime Goldwith its approval step recorded. Each release package is built and launched,its tool list checked and a synthetic encrypted bank statement parsed, onhosted CI runners for Windows x64 and Apple Silicon Mac.

Not in the latest release

• Stock quantities, and stock reads on books with many masters of any kind; sales,purchase or tax posting; creating masters; bill-wise allocation
• TallyPrime Education mode: the trial balance, the stock summary and the list ofmasters are refused; so is a read of vouchers, ledger movement, either registeror another date-window read whose window starts or ends on a day other than the1st, 2nd or 31st; so is an import file or a post with a voucher dated on anyother day (posting on Education has not been run)
• The stock summary on a book with inventory turned off, and on a company split byyear into year-wise companies
• Deleting or undoing a posted voucher (correct it in Tally)
• Reads on very large books can fail or take longer than the assistant waits(#485, #703)
• A base currency other than INR. On a book with several currencies: theforeign-currency ledgers and vouchers themselves (they are set aside orwithheld, and named), ledger movement, Profit and Loss and Balance Sheet,the purchase and sales registers (each refuses the whole read, with no rows, ifone voucher in it names a set-aside ledger), and posting
• Tally Cloud Access or any remote Tally host
• Intel Macs, and a code-signed installer

Is this for you

It is aimed at a practising accountant or a CA firm that already keeps clientbooks in TallyPrime and wants to ask questions of them, or post entries intothem, through an AI assistant such as Claude Desktop.

What it does today

• Reads the loaded companies, ledger masters, trial balance, vouchers in adate window, outstanding receivables and payables, and ledger movement.
• Checks ledger names before you post. Give it the names from a bankstatement or an invoice and it reports which exist in the book and which arenear-misses needing your decision. Reading the ledger list first is the singlebiggest cause of an import being rejected wholesale when it is skipped.
• Records what it did. Every tool call Bridge runs — read or write, andwhether it succeeds or is refused — appends a receipt to a log on your ownmachine, identifying the company it touched and fingerprinting what was asked andwhat came back. Reads keep those fingerprints as evidence alongside. Aprepared batch records the local endpoint it was built for, and a native postingis refused if that endpoint has changed since; that is a safety check kept inBridge's internal import ledger, not a line in the proof report a revieweropens. A reviewer can read the log rather than take a summary on trust.

Before you turn on posting

Whether writing is on depends on how you installed it. Everything above isreading. When writing is off, the write tools do not merely refuse — they areabsent from the tool list entirely, so an assistant cannot see that theyexist.

• The Claude Desktop extension turns voucher posting off by default. Fourknown limits in posting remain. Tally aims an import at a company by its name and cannot bind it to a company's GUID. Bridge's last request before the post checks that exactly one loaded company has the target's GUID and name, and that no other loaded company has the same name ignoring case and spacing; otherwise it refuses the post (#607). A company renamed to, or loaded under, the target's name (or one differing only in case or spacing) in the moment after that check could still receive the voucher, if it has the voucher's ledgers. Bridge may flag afterwards that the loaded companies changed, but cannot always say where the voucher went, and cannot prevent it (accepted residual, #574). A ledger renamed and replaced in that same moment means the post can land in the replacement ledger. Bridge marks the result as needing reconciliation when it sees that the ledger now resolves to a different master; a change that leaves the company's master mark unmoved, or is reverted before that check, is not seen, and a regroup in that moment is not detected (#623). And Bridge has no tool to delete or undo a voucher it has posted, so a wrong post must be corrected by hand in Tally. It records the REMOTEID each post sends, but no delete tool exists yet (#579, #582). And the approval window covers only ComplyEaze Bridge: another Tally connector in the same Claude Desktop that can change entries can do so without it. Turning onAllow voucher posting (Journal, Payment, Receipt, Contra) in the extensionsettings adds post_import, which posts one saved voucher of those types; everyposting still waits for your approval in a separate Bridge dialog. Leave itoff unless you accept those risks. Voucher file preparation and bank-statementparsing, which write nothing to Tally, stay available with the setting off.If you installed an earlier version, check the setting: an earlier defaultmay still be saved as on.
• A source build turns writing off by default. Preparing a file needsBRIDGE_AGENT_ENABLE_IMPORT; posting additionally needsBRIDGE_AGENT_ENABLE_WRITES, which grants both.
• A source build also needs BRIDGE_TERMS_ACCEPTED=true. The extension asksfor that as its "I accept" setting; without it every tool refuses.

With writing on:

• Prepares vouchers as a local file — Journal, Payment, Receipt andContra. Bridge writes the file; it does not send it.
• Posts one saved Journal, Payment, Receipt or Contra per approval, andonly after you approve that exact voucher in a dialog on your own machine.The assistant cannot approve it. Bridge then reads the voucher back so youcan see what actually landed. You can also import a prepared file throughTally yourself; verify_import then reads that back.
• Posting has limits. It creates no masters, posts no sales, purchase, taxor inventory entries, and never alters or deletes a voucher. A company withmore than one currency defined is refused.

What it does not do

• The Tally path uploads nothing to ComplyEaze. Bridge reads it over a localconnection and hands it to the assistant you are talking to; nothing in theTally path sends it to a server of ours.
• It will not post anything without a separate, explicit step after the file isprepared.
• It is not a Tally replacement, a reporting suite, or a filing tool.

The desktop app

The extension is built from the same source library as the desktop app.Packages up to 0.3.0 contained an unfinished document-upload feature and anAXAL sign-in, which no tool of the extension reached. That code was removed(#914) and releases from 0.4.0 on donot contain it; the only network client in ComplyEaze Bridge's own codeconnects to Tally on your own computer. No desktop installer is published.See Security and privacy.

Before you use it with client data

One thing to understand before you use it. When you ask an AI assistant forfinancial data through Bridge, the assistant's provider sees what it reads —company names, party names and amounts. That is a property of using a hostedassistant, not of Bridge. Bridge can mask party names or drop narration first(BRIDGE_AGENT_REDACTION), but neither setting removes amounts — figuresalways go with the answer. Decide this deliberately for client data.

What it costs

ComplyEaze has not set a price for ComplyEaze Bridge and does not sell licencesto it; there is no account with us, subscription or licence key. The code of arelease you download stays under the licence it was published with (Apache-2.0for current releases). We have not decided whether to charge for anything in future.

What you pay or provide today:

• TallyPrime: your own licence.
• Claude Desktop: Anthropic's plans. On 1 October 2026 we ran a candidatebuild of 0.4.0 (not the published file) on Windows with a Claude account thathad no paid plan, on one synthetic company; we make no claim about otherplans or larger books.
• Your clients' data: what Claude reads goes to Anthropic, underAnthropic's terms for your plan; through ComplyEaze Bridge, ComplyEaze doesnot receive it(Privacy Policy, sections 4 to 6).
• Your checking: check results in Tally before you rely on them.

Support and updates are not guaranteed(Terms of Use, section 4.4). Ourliability is limited as section 14 sets out, including its fallback andexceptions; read it before client work.

Installing it

Before you install, turn on Tally's HTTP gateway. TallyPrime does notlisten for ComplyEaze Bridge by default. In Tally's own connectivity / client-serverconfiguration settings, set Tally to act as a server ("acts as Both" inTally's own words) and note its HTTP gateway port — 9000 by default, butconfigurable. To check it is actually on, open http://localhost:9000/status(substitute your port) in a browser: a running gateway answers with a shortTally XML response, and a browser that cannot connect means the gateway isstill off — unless Tally is running in a Windows virtual machine on a Mac,in which case run this check inside that VM, or only once your localforwarding is working. A Mac browser that cannot connect may mean theforwarding described below is missing rather than that the gateway is off.If instead it hangs without answering, Tally may simply be busy behindanother request — wait and retry rather than changing the setting.

The latest published releaseof the Claude Desktop extension is the one to install.Follow the installation guide to install and configureit. Before you do, know what it is and is not:

• Bridge is still being developed. A release may contain errors, so try iton test data first and keep current backups. It is not yet code-signed ornotarized, so your operating system may warn before opening it.Each package has a .sha256 file and a provenance record so you can confirmexactly which bytes and which source commit you downloaded.
• Checked only as far as launching. The release build confirms the packagestarts and lists its tools. It does not establish that it works againstyour Tally, or in conversation inside Claude Desktop. What has been runagainst a real TallyPrime, and on which builds, islisted above; the published0.4.2 package itself has not been run by us against a live TallyPrime.
• Windows x64 and Apple Silicon Macs only. Intel Macs are not supported.
• On a Mac, Tally must run on that same Mac, in a local Windows virtualmachine or through approved local forwarding. Bridge only talks to Tally onyour own computer, so a separate PC or a Tally elsewhere on your networkcannot be reached by typing its address.
• It does not update itself. To upgrade, install a newer release fromClaude Desktop's Extensions settings. Release 0.4.2 installs beside an olderrelease instead of replacing it (seen on a Mac; not tried on Windows): removethe older extension first, do not delete the data folder, and enter yoursettings again, including Response redaction, which starts at none.

The Bridge desktop application is a separate program and has no publishedinstaller; building it from source is described under Contributor quick startbelow.

The rest of this file is for people working on Bridge. The repository isself-contained: build and development commands resolve files relative to theclone, not to a developer-specific directory. It holds a Tauri desktopapplication and the MCPB packaging path for Claude Desktop, withReact/TypeScript and Rust components for Tally and local databaseoperations.

First useful result

Install the latest published releaseof the Claude Desktop extension with the installation guide. For sourceuse, the contributor quick start below builds the desktop app; to run the MCPserver from source, follow the source MCP setup.

Before requesting financial data through an MCP client, the client may send the selectedTally result to its AI provider, including companyidentity, party or open-bill details, and amounts. Source installations defaultto BRIDGE_AGENT_REDACTION=none; set it to mask_parties or drop_narrationbefore launch when that better fits the workflow. These settings mask partynames or drop narration; they do not remove amounts. The package installationsettings expose the same choices.

For a first result, run tally_status to check that TallyPrime and its Licensedor Education mode are observed, then list the loaded companies. Select acompany with exactly one observed INR currency master and request receivablesor payables. In Education mode, explicitly supply an as_of date on day 1, 2,or 31; an omitted date defaults to today and may be refused. Bridge rechecksproduct, mode, dates and currency for the financial read; other or unobservedproducts/modes, no currency master, non-INR, or multiple currency masters arerefused.

The desktop also offers local XML draft preparation through Prepare file. It preserves source observations beside editable proposals and saves a local draft for later review.

For contributors, use the setup and development path below.

Supported development hosts

Bridge is intended to build and run on Windows and macOS 12.4 or later. Runplatform checks on a native host for each operating system; a successful buildon one operating system does not verify the other.

Shared prerequisites:

• Node.js 24 (>=24.15.0) and Corepack (.node-version pins the CI baseline)
• the Rust toolchain pinned by rust-toolchain.toml
• Perl 5 with Locale::Maketext::Simple for the bundled SQLCipher/OpenSSL build
• LLVM/libclang for SQLCipher binding generation (LIBCLANG_PATH may be required)
• the operating-system dependencies listed in theTauri prerequisites

On Windows, install the Microsoft C++ build tools, WebView2 components, and acomplete Perl distribution such as Strawberry Perl. If another incompleteperl.exe appears first on PATH, set OPENSSL_SRC_PERL to the complete Perlexecutable. Install LLVM as well; if libclang.dll is not discoverable, setLIBCLANG_PATH to its directory (commonly C:\Program Files\LLVM\bin). OnmacOS, install Xcode Command Line Tools. Bridge's macOS bundles require macOS12.4 or later.

Contributor quick start

Run these commands from the repository root in PowerShell, Command Prompt, or aPOSIX-compatible shell:

corepack pnpm install --frozen-lockfile
corepack pnpm exec playwright install chromium webkit
corepack pnpm test
corepack pnpm run build
corepack pnpm run cargo:check
corepack pnpm run tauri:dev

pnpm test includes Chromium and WebKit evidence-drawer focus suites; installingthe lock-pinned browsers after dependencies is therefore required once for eachdeveloper environment. tauri:dev starts the Vite development server anddesktop application. It does not require a fixed checkout location. The firstRust build can take several minutes.

For a release build, run corepack pnpm run tauri:build on each target host.CI-produced bundles are unsigned smoke artifacts only. Do not redistribute adesktop installer until the signing, notarization, provenance, and rollbackgates in the release runbook are complete.

Platform verification

Before claiming support for a platform, run the following on that platform:

corepack pnpm install --frozen-lockfile
corepack pnpm run build
corepack pnpm run cargo:check
corepack pnpm run tauri:build

Also manually exercise the affected Tally workflows.Vendor integrations may require host-specific software even though repositorypaths and project commands are portable.

Integration trust boundaries

Bridge restricts native network and file access even if the renderer iscompromised:

• Tally connections are loopback-only (localhost, 127.0.0.0/8, or ::1).Remote plaintext Tally hosts are intentionally rejected.
• Showing an export in the file manager accepts only a file ComplyEaze Bridgeexported since it started; any other path the renderer sends is refusedbefore anything is launched.

Privacy and safe diagnostics

Do not commit or attach real customer, company, tax, certificate, credential,financial, or document data. Before sharing logs, screenshots, fixtures, orreproduction steps, replace personal and customer data with synthetic valuesand remove local usernames and absolute paths. See SECURITY.mdfor private reporting and handling requirements.

Repository map

• src/ - React UI and API bindings
• src-tauri/ - Rust core and Tauri configuration
• docs/ - architecture, roadmap, and operational guidance
• .github/ - issue and pull-request templates plus CI configuration

Governance

• Agent responsibilities
• Contributor guide
• Review checklist
• Security policy
• Rectification guidelines
• Roadmap
• Managed Git guidance
• Source and asset provenance
• Release process

License

Bridge is licensed under the Apache License, Version 2.0.Attribution notices are provided in NOTICE.The ComplyEaze logo and icon files are not licensed under Apache-2.0; seeNOTICE and TRADEMARKS.md.The historical v0.1.0 release remains under the MIT license shipped withthat tag; current development source is version 0.4.2 under Apache-2.0.