Skip to main content
Glama
tallyprime-mcp

tallyprime-mcp

by rkparupudi

tallyprime-mcp

A read-only MCP server that lets Claude answer questions from the books in a locally running TallyPrime: ledgers, vouchers, outstanding bills and the trial balance.

It runs on the same Windows machine as TallyPrime and talks to Tally's local HTTP server. The books never leave the machine except as the answers Claude reads in the conversation.

Status: early version, not yet verified against a real TallyPrime. It has only been tested against the included mock Tally server, which was written from Tally's documentation. Expect parsing fixes on first contact with real data, especially in get_outstanding.

Tools

Tool

What it answers

list_companies

Which companies are loaded; doubles as a connection check

list_ledgers

Ledger balances, optionally by group or name

get_vouchers

Transactions in a date range, with totals by voucher type

get_outstanding

Receivables or payables with ageing, per bill and per party

get_trial_balance

Debit and credit totals by group, and whether they balance

Every request sent to Tally is an Export. The client refuses to send anything else, so this version cannot create or change data.

Related MCP server: Tally MCP Server

Setup

1. Turn on Tally's HTTP server

In TallyPrime: F1 (Help) > Settings > Advanced Configuration, enable the HTTP server and keep port 9000. Restart TallyPrime and load a company.

Check it from a browser: http://localhost:9000 should answer with a short "TallyPrime Server is Running" message.

2. Install

Needs Python 3.10 or newer.

cd tallyprime-mcp
pip install -e .

3. Add it to Claude Desktop

Settings > Developer > Edit Config, then add:

{
  "mcpServers": {
    "tallyprime": {
      "command": "tallyprime-mcp",
      "env": {
        "TALLY_URL": "http://localhost:9000",
        "TALLY_COMPANY": ""
      }
    }
  }
}

Restart Claude Desktop. If tallyprime-mcp is not found, use "command": "python", "args": ["-m", "tallyprime_mcp.server"] instead.

Settings

Variable

Default

Meaning

TALLY_URL

http://localhost:9000

Where Tally's HTTP server listens

TALLY_COMPANY

empty

Company to query; empty means the active company

TALLY_TIMEOUT

60

Seconds to wait for Tally

Keep TALLY_URL pointed at a machine you trust. Tally's HTTP server has no authentication, so do not expose port 9000 beyond the local machine.

Try it without Tally

A mock Tally with sample data is included:

python tests/mock_tally.py 9000

Then point the server at it and ask things like:

  • "Which customers have bills older than 60 days?"

  • "Summarise October's sales and purchases."

  • "Does the trial balance tally?"

Tests

pip install -e ".[dev]"
pytest

Conventions

  • Balances are returned as an amount plus a side (debit / credit). Internally Tally stores debits as negative numbers.

  • get_outstanding ages bills from the bill date, and reports days_overdue from the due date when Tally provides one. It only covers ledgers that maintain bill-wise details.

  • get_trial_balance groups by each ledger's immediate parent group, not by Tally's primary groups.

Not yet done

  • Voucher creation (needs a confirm-before-write step).

  • Stock and inventory, GST reports, profit and loss, balance sheet.

  • Packaging as a one-click desktop extension.

Licence and disclaimer

MIT; see LICENSE.

This is an independent project. It is not affiliated with, endorsed by or supported by Tally Solutions Pvt. Ltd. "Tally" and "TallyPrime" are trademarks of their respective owner and are used here only to describe what this software connects to.

Available Tools

5 tools
get_outstandingB

Pending bills: what customers owe (receivable) or what is owed to suppliers (payable), with ageing.

min_days_outstanding: only bills at least this many days old, counted from the bill date (e.g. 60 for "older than 60 days"). as_of: date to age against, YYYY-MM-DD. Defaults to today.

Only covers ledgers that use bill-wise details in Tally.

Inputs: kind, as_of, company, party_contains, +1 more.

get_trial_balanceB

Trial balance built from ledger closing balances, grouped by each ledger's parent group, with debit and credit totals.

'balanced' is false when total debits and credits differ by more than one rupee, which usually points at an unposted opening-balance difference.

Inputs: company.

get_vouchersA

Fetch vouchers (transactions) in a date range, oldest first.

from_date / to_date: inclusive, YYYY-MM-DD. voucher_type: e.g. "Sales", "Purchase", "Receipt", "Payment", "Journal". party_contains: case-insensitive filter on the party ledger name. limit: maximum vouchers to return. Totals by type always cover the full matching set, so narrow the range or filters if results are truncated.

Inputs: to_date (required), from_date (required), limit, company, +2 more.

list_companiesA

List the companies currently loaded in TallyPrime. Also works as a connection check: an error here means Tally is not reachable.

Inputs: no named parameters.

list_ledgersA

List ledgers with opening and closing balances.

group: restrict to ledgers under this group, including sub-groups (e.g. "Sundry Debtors", "Bank Accounts", "Indirect Expenses"). name_contains: case-insensitive filter on the ledger name. nonzero_only: drop ledgers whose closing balance is zero. limit: maximum ledgers to return (largest closing balances first). company: company name; defaults to the configured or active company.

Inputs: group, limit, company, nonzero_only, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool maps to a distinct reporting concept: companies, ledgers, vouchers, outstanding bills, and trial balance. The only mild overlap is list_ledgers (per-ledger closing balances) versus get_trial_balance (the same balances aggregated by parent group); descriptions clarify the difference, but an agent could occasionally hesitate between them.

    Naming Consistency5/5

    All names follow a clean verb_noun pattern (list_companies, list_ledgers, get_vouchers, get_outstanding, get_trial_balance). The list_/get_ split is semantically meaningful rather than inconsistent.

    Tool Count5/5

    Five tools is well-scoped for a read-only TallyPrime reporting surface; every tool covers a real accounting workflow (connectivity, ledgers, transactions, receivables/payables, trial balance) with no filler.

    Completeness3/5

    Core read paths are covered, but the surface stops at trial balance: no P&L, balance sheet, stock/inventory summary, or single-voucher/ledger detail retrieval. Write operations (posting vouchers, creating ledgers) are absent, which may be deliberate but limits agents to reporting only.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      This read-only MCP Server allows you to connect to Tally data from Claude Desktop through CData JDBC Drivers. For full CRUD support, check out our MCP Server for Tally (https://www.cdata.com/drivers/tally/download/mcp).
      2
      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
      26 npm
      3
      MIT
    • A
      license
      A
      quality
      B
      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.
      39
      68 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      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.
      68 npm
      MIT