Skip to main content
Glama
lokesh-sparrow

PNPC-MCP-Tally-Prime

Related Servers

Alternatives to PNPC-MCP-Tally-Prime

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      An 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 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that lets Claude read from and write to TallyPrime via its built-in XML/HTTP gateway.
      23
      28 npm
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP 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.
      21
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Connects Tally Prime ERP data to AI assistants via MCP, enabling natural language queries for financial reports, stock summaries, and ledger balances.
      28 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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 npm
      AGPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      Read-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.
      13
      1
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 87 tools

    Disambiguation3/5

    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.

    Naming Consistency5/5

    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.

    Tool Count1/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessNo issues