Skip to main content
Glama
tally-prime-mcp

tally-prime-mcp

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TALLY_HOSTNoHost or IP of the PC running TallyPrimelocalhost
TALLY_PORTNoPort number for the TallyPrime server9001
TALLY_COMPANYNoThe company name to use
TALLY_READONLYNoSet to true to block all write tools (read-only mode)false
TALLY_BACKUP_DIRNoDirectory where backups are storedDesktop\Tally Backups
TALLY_TIMEOUT_MSNoTimeout in milliseconds180000
TALLY_AUTO_BACKUPNoSet to false to disable automatic backups before changestrue
TALLY_BACKUP_KEEPNoNumber of automatic backups to keep per company (0 = keep all)30

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
tally_statusA

Check the connection to TallyPrime, list loaded companies and show backup settings.

list_ledgersB

List ledgers with their group and opening/closing balance (positive = Cr, negative = Dr as Tally reports).

list_stock_itemsC

List stock items with group, base unit and closing quantity/value.

list_mastersB

List masters of a type: group, stock_group, godown, unit, cost_centre (also ledger / stock_item, names only).

get_masterB

Full details of one master. Ledger: group, opening balance, bill-wise, address, state, pincode, GSTIN, PAN, contacts. Stock item: group, unit, opening stock, GST rate, HSN. Others: parent etc.

list_voucher_typesB

List voucher types with their base type (e.g. "SALES GST-RD" -> Sales).

list_vouchersA

List vouchers in a date range with their entries. Each row has master_id, which alter_voucher / delete_voucher use. Roughly 5 seconds per month of data, so keep ranges short.

get_voucherB

Get one voucher in full by master_id (or guid, or date + voucher_number + voucher_type).

list_backupsA

List the automatic/manual data backups (newest first) with their folders.

backup_dataA

Take a backup of the company data folder now (copied to Desktop\Tally Backups). Write tools already do this automatically.

create_voucherA

Create a voucher in Tally (Payment, Receipt, Journal, Contra, Sales, Purchase, Credit/Debit Note, Stock Journal or any custom type). Accounting vouchers: give ledger_entries only (Debits must equal Credits). Item invoices: give inventory_entries (stock items, each posting to a sales/purchase ledger) plus ledger_entries for the party and any tax / round-off ledgers; items count as Cr when going out (sales) and Dr when coming in (purchase). Stock Journal (godown transfer, manufacturing, adjustment): give stock_out (source/consumption) and/or stock_in (destination/production). GST is not computed automatically: pass CGST/SGST/IGST ledger lines with amounts.

alter_voucherA

Modify an existing voucher. Identify it with master_id (preferred). Only the fields given in changes are modified; everything else (GST details, bank details, addresses...) is sent back unchanged. changes.ledger_entries REPLACES all ledger lines (for item invoices: the party/tax lines); changes.inventory_entries REPLACES all item lines; changes.stock_in / stock_out REPLACE the Stock Journal lines. Totals must still balance. An existing single bill reference on a ledger is kept automatically if you omit bill_allocations for it.

delete_voucherA

Permanently delete a voucher from Tally (a backup is taken first). Identify it with master_id (preferred). Requires confirm: true. Show the user the voucher (get_voucher) and get their approval before calling this.

create_ledgerC

Create a ledger (party, bank, expense, income, tax...).

alter_ledgerA

Modify a ledger: rename (new_name), group, opening balance, bill-wise, address, state, pincode, GSTIN, PAN, contacts. Only given fields change. Opening balance changes are two-step: the first call only returns current vs new values for the user to approve.

create_stock_itemC

Create a stock item with unit, group, opening stock, GST rate and HSN.

alter_stock_itemA

Modify a stock item: rename (new_name), group, unit, opening stock, GST rate, HSN, description. Only given fields change. Opening stock changes are two-step: the first call only returns current vs new opening figures; ask the user, then repeat with confirm_opening_change: true.

create_masterA

Create an account group, stock group, godown, unit (name = symbol, e.g. "KG") or cost centre.

alter_masterA

Modify / rename an account group, stock group, godown, unit or cost centre. Only given fields change.

delete_masterA

Permanently delete a ledger, group, stock item, stock group, godown, unit or cost centre (a backup is taken first). Tally refuses if it is still used by vouchers or other masters. Requires confirm: true; get the user's approval first.

import_raw_xmlA

Advanced escape hatch: import raw Tally XML objects (the content that goes inside ), e.g. a or with ACTION="Create"/"Alter"/"Delete". Prefer the specific tools.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 21 tools

Disambiguation4/5

Most tools map cleanly to a distinct resource plus action, so an agent can usually choose correctly. Minor overlap exists because list_masters can also list ledger/stock_item names only, and delete_master spans ledger/stock item deletion while create/alter use dedicated tools, but the descriptions make this workable.

Naming Consistency5/5

The set follows a strong verb_noun convention throughout: list_*, get_*, create_*, alter_*, delete_*, backup_data, import_raw_xml. The only slight deviation is tally_status, but it remains clear and readable.

Tool Count4/5

Twenty-one tools is on the heavy side, but the domain is broad: vouchers, ledgers, stock items, masters, backups, status, and a raw XML escape hatch. Most tools earn their place, though the set is near the upper end of what feels comfortable.

Completeness5/5

The surface covers full lifecycle operations for vouchers, ledgers, stock items, and other masters, plus list/get, backups, status, and an advanced raw XML fallback. No obvious CRUD dead ends are present for the core accounting workflows.

Maintenance

ActivityMaintained
ResponsivenessSyncing