PNPC-MCP-Tally-Prime
Related Servers
Alternatives to PNPC-MCP-Tally-Prime
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that connects Claude to TallyPrime, allowing natural language queries for reading ledgers, trial balances, and daybooks, and creating vouchers with a dry-run and confirmation safety model.285 npmMIT
- AlicenseAqualityCmaintenanceAn MCP server that lets Claude read from and write to TallyPrime via its built-in XML/HTTP gateway.2328 npm3MIT
- AlicenseAqualityBmaintenanceMCP server that lets Claude read, create, alter and delete TallyPrime data (vouchers, GST invoices, ledgers, stock items) over Tally's XML port, with an automatic backup before every change.21MIT
- AlicenseNot gradedqualityFmaintenanceConnects Tally Prime ERP data to AI assistants via MCP, enabling natural language queries for financial reports, stock summaries, and ledger balances.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
- 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
TDQS
Scored across 87 tools
Many create_*/update_* pairs and multiple voucher-type tools (e.g., sales invoice vs delivery note vs sales order vs quotation, purchase invoice vs receipt note vs purchase order) are subtly distinct; descriptions provide guidance, but the sheer breadth makes misselection likely. Retrieval tools like get_*, sync_*, and query_sql also overlap in purpose. Boundaries are described, but the set-level ambiguity remains substantial.
Tools follow a highly consistent snake_case verb_noun pattern: get_, create_, update_, delete_, sync_, set_, etc. Minor names like preview_write, confirm_write, and query_sql still fit the convention. No chaotic mixed casing or verb styles.
87 tools is an extreme mismatch for an agent-facing interface, far beyond the typical 3-15 well-scoped range. The surface is inflated with near-duplicate create/update pairs for many voucher subtypes, causing overwhelming tool selection and discovery burden. This exceeds even the 50+ 'extreme mismatch' threshold.
Coverage is broad and deep: masters, vouchers, reports, sync/SQL, audit, health, preview/confirm, and many Tally voucher types. Minor gaps exist, such as no dedicated update/delete for some masters (e.g., cost centre, cost category), though generic delete_master and query_sql provide workarounds. The surface is close to complete for the stated TallyPrime domain.