PNPC-MCP-Tally-Prime
Related Servers
Alternatives to PNPC-MCP-Tally-Prime
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn 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.MIT
- AlicenseAqualityCmaintenanceAn MCP server that lets Claude read from and write to TallyPrime via its built-in XML/HTTP gateway.2326 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 gradedqualityDmaintenanceConnects Tally Prime ERP data to AI assistants via MCP, enabling natural language queries for financial reports, stock summaries, and ledger balances.MIT
- 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
- 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
Despite 87 tools, most have a sharply distinct role: each Tally voucher type gets its own create_/update_ pair (Sales Invoice, Purchase Invoice, Credit/Debit Note, Delivery/Receipt Note, Material In/Out, Rejections In/Out, Physical Stock, Stock Journal, Orders, Job Work, Quotation) and the descriptions actively contrast them. A few genuine overlaps remain: delete_master duplicates delete_stock_item's capability, create_vouchers_batch overlaps create_voucher, and adjacent pairs like create_delivery_note vs create_sales_invoice or create_material_in vs create_receipt_note require careful reading to avoid misselection.
The set follows a strongly predictable verb_noun convention (get_*, create_*, update_*, delete_*, set_*, sync_*), with create_/update_ pairs named identically per voucher type. Minor deviations exist (create_vouchers_batch is plural while its sibling is create_voucher, delete_master is a generic escape hatch alongside delete_stock_item, and preview_write/confirm_write sit outside the CRUD verb set), but none are confusing.
87 tools is an extreme surface for one server, well past the point where an agent can hold the set in mind or reliably pick among near-sibling voucher types. Much of the volume comes from exhaustive create_/update_ permutations across ~17 voucher types, which could have been collapsed into a parameterized voucher tool with a type discriminator.
The surface is remarkably thorough for TallyPrime: masters (ledgers, groups, stock items/groups, units, godowns, cost centres/categories, voucher types), the full voucher lifecycle across every major voucher type, delete_voucher/delete_master, financial reports, tax summaries, SQL sync/query, preview/confirm write safety, and an audit log. Gaps are minor but real: there are create tools for units, godowns, and cost centres without corresponding list/get tools, and rename support is uneven across masters (create_ledger/create_group/create_voucher_type accept oldName but create_godown/create_unit/create_cost_centre/create_stock_group do not document it).