ComplyEaze Bridge: TallyPrime MCP server for Claude Desktop
OfficialRelated Servers
Alternatives to ComplyEaze Bridge: TallyPrime MCP server for Claude Desktop
- AlicenseNot gradedqualityBmaintenanceEnables Large Language Models to access and query Tally Prime ERP data, including financial reports, masters, and inventory summaries, via the Model Context Protocol.85MIT
- AlicenseNot gradedqualityDmaintenanceConnects Tally Prime ERP data to AI assistants via MCP, enabling natural language queries for financial reports, stock summaries, and ledger balances.MIT
- AlicenseNot gradedqualityAmaintenanceBridges Tally Prime ERP with AI assistants, enabling querying financial reports, managing masters, creating vouchers, and analyzing GST data through natural language.AGPL 3.0
- AlicenseAqualityBmaintenanceRead-only MCP server that lets AI assistants query a locally running TallyPrime installation through its HTTP-XML gateway, exposing companies, ledgers, vouchers, trial balance, P&L, balance sheet, receivables, payables, and stock reports as clean typed JSON. All processing stays on the user's own machine, with no write access and no cloud backend.13Apache 2.0
Related Servers
- FlicenseAqualityDmaintenanceEnables natural language interaction with TallyPrime accounting software via Claude AI, allowing querying reports, creating vouchers, and managing ledgers without manual navigation.17-
- FlicenseNot gradedqualityDmaintenanceGives AI models native-level control over TallyPrime ERP, covering 169+ tools across all functional modules including masters, vouchers, reports, GST, payroll, and more.-
- AlicenseNot gradedqualityBmaintenanceEnables LLMs like Claude and ChatGPT to access and interact with Tally Prime ERP data through MCP, including financial reports, ledgers, trial balance, balance sheet, profit and loss, and stock summary.AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables read-only interaction with TallyPrime accounting data, letting users ask accounting questions and retrieve live company information, financial reports, and ledgers without altering anything in Tally.25 npmMIT
- FlicenseAqualityAmaintenanceThis MCP server enables users to read from and write to TallyPrime via its XML/HTTP gateway, supporting operations like ledger management, voucher creation, and financial report retrieval through natural language.871-
- AlicenseAqualityBmaintenanceConnects Claude Desktop, Claude Code, and other MCP-compatible clients to cloud accounting and GST billing records, enabling GST-compliant invoice creation, ledger and voucher management, balance queries, and real-time financial reporting through natural language with role-based tenant isolation.2224 npmMIT
TDQS
Scored across 20 tools
Most tools target clearly distinct TallyPrime resources or workflows, such as balance_sheet, profit_and_loss, trial_balance, vouchers, and the GST registers. The main overlap is between egress_log and read_evidence, which both report local tool-call receipts, and tally_status also returns company identity tuples alongside list_companies. These are distinguishable from their descriptions, but not entirely free of potential misselection.
All tool names use snake_case, which is consistent and readable. However, the set mixes noun-style names (balance_sheet, masters, vouchers, outstandings) with verb_noun names (list_companies, validate_masters, verify_import), so the pattern is not uniformly predictable. This is a minor deviation rather than a coherence problem.
Twenty tools is on the heavy side for an MCP server, but the domain—TallyPrime accounting, GST registers, import verification, and local evidence—is broad enough that most tools serve distinct workflows. The count is slightly over the ideal range rather than excessive. No obvious duplicate tools inflate the count.
The surface covers read/reporting, masters, vouchers, GST registers, outstandings, validation, presence checks, and import verification well. However, descriptions repeatedly reference post_import and build_import_xml, yet neither tool appears in the exposed set, leaving a notable gap in the import dispatch lifecycle. This is a meaningful missing operation for a bridge that otherwise supports import validation and verification.