MCP

ComplyEaze Bridge: An MCP Server That Connects Claude Desktop to TallyPrime on Your Own Machine

ComplyEaze Bridge is built for accounting firms and accountants who want Claude Desktop to read the TallyPrime data on their own computer and prepare voucher import files from bank statements. Before you start, you must enable Tally's HTTP gateway and accept the extension's terms of use (version 2026-10.1) in the extension settings; otherwise every tool refuses to run with terms_not_accepted.

Official source · ComplyEaze Bridge

Install

Install the latest release of the Claude Desktop extension (an .mcpb file), current release mcp-v0.6.0, then follow the installation guide to install and configure it.

Who it's for

ComplyEaze Bridge is an open-source MCP server that connects Claude Desktop to TallyPrime running on your own computer. The official positioning is for accounting firms and accountants: the assistant can read the company data from your local books directly and prepare voucher import files from bank statements. It reads the books on your own machine, and that is exactly what sets it apart from cloud-based finance tools. For a firm, checking the books, matching bank lines and tidying vouchers are the everyday work; this extension moves all three into a conversation.

It is a good fit for you if:

  • you do your day-to-day bookkeeping in TallyPrime, and it is installed on your own computer;
  • your client is Claude Desktop, running on Windows x64 or an Apple Silicon Mac;
  • you want the assistant to help you check the books and prepare vouchers from bank statements, so you spend less time entering entries by hand.

First, confirm the cases where it does not fit:

  • it targets TallyPrime only, not other accounting software;
  • the official source lists only the two platforms above and says nothing about other systems;
  • it is currently distributed as a Claude Desktop extension, and the official source states plainly that it has not been run in any other MCP client, so whether other clients work with it is unconfirmed.

Your first attempt in 3 minutes

Two things must be done first, or the tools will not respond:

  • enable Tally's HTTP gateway before installing: TallyPrime does not listen for this extension by default, and without the gateway the tools cannot reach the books;
  • after installation, accept the extension's terms of use (version 2026-10.1) in the extension settings; until you accept them, every tool refuses to run with terms_not_accepted.

There is only one recommended main path: install the latest version of the Claude Desktop extension. The current version is mcp-v0.6.0 (October 16, 2026), shipped as an .mcpb extension file; follow the official installation guide for installation and configuration.

Start your first attempt with a read: none of the 28 tools installed in this version changes your TallyPrime books. Once it is installed, ask the assistant to use its tools to pull up any single record from the books on your machine. The success signal to look for is the tool returning real content from the books, not a terms-not-accepted or connection-failed message. If you see an error, go back to the two prerequisites above and check them one by one: gateway on, terms accepted. The whole first attempt involves reads only, so there is nothing to undo.

Distinguish two states carefully: read tools perform no write operations, but that only means they do not write; it does not mean there are no other boundaries. Real posting is a different matter. Posting is off by default; once you turn it on, two extra tools appear, and every voucher must be confirmed by you one at a time before it is written.

Use cases

Case 1: check your local books in conversation. Scenario: you want to ask about the state of the accounts directly instead of clicking through the TallyPrime interface screen by screen. How: once you have completed the two prerequisites (gateway and terms), ask the assistant in the client to read the data in your local books through the Bridge tools. Expected result: the assistant calls one of the tools to complete the read, and the books stay unchanged; the official source does not list the individual tool names, so go by what the client actually shows. Use this step first to confirm that the assistant is really connected to your books before moving on to more involved tidying.

Case 2: prepare a voucher import file from a bank statement. Scenario: you have a bank statement and want it turned into a voucher file that TallyPrime can import, instead of entering each voucher by hand. How: hand the statement to the assistant in the client and let it use the voucher-preparation capability. Expected result: you get an import file rather than entries posted to the books, because posting is off by default; if you do turn posting on, the two new tools still only write after you confirm each voucher individually. The official documentation gives no specific parameters or step-by-step procedure; what can be confirmed today is that it gets as far as preparing the import file. How to use the import file once you have it should follow the official instructions too.

Limits and boundaries

  • Read/write nature: none of these tools changes the books; posting is off by default, and turning it on adds two tools that write only after you confirm each voucher. In other words, your books stay exactly the same during the first attempt. gst_uncertain_vouchers and negative_stock exist only in the source code, have not yet made it into a built release, and cannot be used at the moment.
  • Prerequisites and confirmation points: Tally's HTTP gateway must be enabled first (TallyPrime does not listen for this extension by default); the terms of use (version 2026-10.1) must be accepted in the extension settings, otherwise every tool refuses to run.
  • Where the data lives: it connects to TallyPrime running on your own computer, so the books on that machine must be reachable while you use it.
  • Not yet confirmed: the official source does not specify the names and parameters of the 28 tools, nor availability on other systems or in other clients; check the official documentation before you rely on them.