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.28 npm109MIT
- AlicenseNot gradedqualityDmaintenanceConnects Tally Prime ERP data to AI assistants via MCP, enabling natural language queries for financial reports, stock summaries, and ledger balances.28 npmMIT
- AlicenseNot gradedqualityBmaintenanceBridges Tally Prime ERP with AI assistants, enabling querying financial reports, managing masters, creating vouchers, and analyzing GST data through natural language.28 npmAGPL 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.131Apache 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-
- AlicenseNot gradedqualityDmaintenanceGives AI models native-level control over TallyPrime ERP, covering 169+ tools across all functional modules including masters, vouchers, reports, GST, payroll, and more.28 npmMIT
- 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.28 npmAGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query BUSY Accounting books in plain language through read-only tools covering ledgers, outstanding bills, banking, vouchers, inventory, GST/TDS, and audit trails.MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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.23 npmMIT
- AlicenseAqualityBmaintenanceThis 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.872ISC
TDQS
Scored across 30 tools
Most tools map to a distinct report or resource (profit_and_loss, balance_sheet, cash_flow, trial_balance, stock_summary), but several pairs overlap enough to cause misselection: read_evidence vs egress_log both answer 'what has ComplyEaze Bridge read/seen' with near-identical caveats, gst_status vs gst_uncertain_vouchers both read GSTR-1 per-voucher flags, and ledger_masters vs masters vs validate_masters vs trial_balance all deal with the ledger catalogue. The prose eventually distinguishes them, but an agent must read pages of caveats to recover the boundary.
All names are snake_case and mostly report-named nouns (profit_and_loss, trial_balance, sales_register, stock_summary) with a small set of verb_noun tools (list_companies, validate_masters, verify_import), which is a readable, predictable convention. Minor inconsistency remains: some tools are pure nouns with no verb, and stray names referenced in the text (post_import, build_import_xml, gst_by_ledger) do not match the shipped names (gst_by_counter_ledger).
30 tools is heavy, but TallyPrime's surface genuinely spans statements, registers, GST, masters, stock, bank tie-out, vouchers and local bookkeeping, so most tools have a real domain niche rather than being padding. Still, several (read_evidence/egress_log, gst_status/gst_uncertain_vouchers, the three register tools) are close enough that a leaner set of ~20 would have earned its place better.
The read-side coverage is unusually thorough (P&L, balance sheet, cash flow, trial balance, registers, GST, masters, stock, outstandings, vouchers, presence checks), but the tool surface has documented dead ends: post_import, build_import_xml, parse_bank_statement and acknowledge_post_review are repeatedly referenced as prerequisites (statement_tie_out reads proposals_id from build_import_xml; validate_masters says only 'exact' is admitted by build_import_xml) yet are absent from this server, leaving the whole import-posting and bank-reconciliation flow unreachable.