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

    • F
      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.
      -
    • F
      license
      A
      quality
      A
      maintenance
      An MCP server that lets Claude read from and write to TallyPrime via its built-in XML/HTTP gateway.
      23
      2
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects Tally Prime ERP data to AI assistants via MCP, enabling natural language queries for financial reports, stock summaries, and ledger balances.
      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.
      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
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      A read-only MCP server that connects Claude Desktop to TallyPrime, enabling natural-language auditing and analysis of accounting data directly from the local Tally installation.
      26
      351 npm
      MIT

    TDQS

    A3.6/5.0

    Scored across 87 tools

    Disambiguation4/5

    Each tool targets a specific Tally entity, report, or voucher type, and the extensive descriptions explicitly cross-reference distinctions between similar tools (e.g., create_voucher vs create_sales_invoice, get_vouchers vs get_ledger_vouchers). However, with 87 tools and many nearly parallel create/update pairs, an agent will occasionally need to read carefully to pick the right one, and the sheer volume increases the chance of mis-selection.

    Naming Consistency5/5

    Naming follows a strict, predictable verb_noun pattern throughout: get_*, create_*, update_*, delete_*, sync_*, set_*, preview_write/confirm_write. All tool names are lowercase snake_case with consistent GRPC-style prefixes, making the surface feel uniform and navigable despite its size.

    Tool Count1/5

    87 tools is far beyond even the 'too many (25+)' threshold and squarely in the 'extreme mismatch (50+ tools)' band. While the TallyPrime domain is broad, this count will overwhelm agent context windows, increase selection cost, and make the API impractical to use without aggressive filtering.

    Completeness4/5

    The surface is exceptionally thorough for TallyPrime: CRUD for most master types, a wide range of voucher types, reports, SQL cache syncs, preview/confirm write flow, and audit/health tools. Minor gaps exist—there are no direct listing tools for godowns, units, stock groups, or cost categories, and no dedicated order/register listing beyond generic voucher queries—but these are workable via existing tools or error messages.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues