Skip to main content
Glama
PNPC-MCP-Tally-Prime

PNPC-MCP-Tally-Prime

PNPC Global이 구축하고 유지 관리합니다. 누구나 사용하거나 자신의 TallyPrime 설정에 맞게 자체 호스팅할 수 있도록 공개되어 있습니다.

전제 조건

  • TallyPrime (Silver / Gold — Educational Edition은 피하세요. 날짜 범위 제한으로 인해 LLM에 부분적/잘못된 데이터가 제공되어 성능이 저하되고 부정확한 답변이 발생합니다.)

  • Claude Desktop (Pro / Team / Max / Enterprise 권장 — MCP는 질문당 Tally에 많은 호출을 하여 Free 플랜의 한도를 빠르게 소진할 수 있습니다.)

  • TallyPrime의 XML/HTTP 게이트웨이 활성화: F1 (Help) → Settings → Connectivity → Client/Server configuration

    • TallyPrime 작동 모드 = Server (또는 Both)

    • 포트 = 9000

이것을 실행하기 위해 Node.js를 설치할 필요는 없습니다 — Claude Desktop은 확장 기능을 위한 자체 Node.js 런타임을 번들로 제공합니다. 소스에서 빌드하는 경우에만 Node.js가 필요합니다(소스에서 빌드 참조).

Related MCP server: Tally MCP Server

다운로드

최신 빌드 패키지를 이 저장소에서 바로 받으세요. 복제나 빌드가 필요 없습니다.

지원 플랫폼

플랫폼

로컬

원격

Claude Desktop

✔️

✔️

(원격/클라우드 배포는 HTTP 엔트리 포인트를 통해 가능합니다 — docs/HTTP_DEPLOYMENT.md 참조 — 하지만 로컬이 대부분의 사용자에게 지원되고 권장되는 방법입니다.)

설정 (로컬)

Claude Desktop과 TallyPrime이 동일한 PC에 있을 때 사용하세요. Claude Desktop이 내부적으로 MCP 서버를 실행합니다.

원클릭 설치 (확장 프로그램 통해)

  1. Claude Desktop → 메뉴 → File → Settings

  2. Extensions → Advanced settings

  3. Install Extension 클릭

  4. (위에서 다운로드한) PNPC-MCP-Tally-Prime.mcpb 파일을 찾아 선택

  5. "PNPC-MCP-Tally-Prime을 설치하시겠습니까?" 라는 대화 상자가 나타납니다 — Install 클릭

  6. TallyPrime Gateway URL을 묻는 메시지가 표시됩니다 — 게이트웨이가 다른 곳에서 실행 중이지 않으면 http://localhost:9000 그대로 두세요.

  7. 채팅에서 Tools(망치) 아이콘을 클릭하여 확인하세요 — PNPC-MCP-Tally-Prime이 목록에 나타나야 합니다.

4~5단계에서 확인 대화 상자가 나타나지 않으면(조용히 수락되어 아무것도 보이지 않음), 아래 문제 해결을 참조하세요 — 동일한 화면에서 Install Unpacked Extension을 이 저장소의 루트 폴더를 가리키도록 선택하는 것이 안정적인 대체 방법입니다.

구성 파일을 통한 설치 (개발자 메뉴 통해)

  1. Claude Desktop → 메뉴 → File → Settings → Developer

  2. 구성 위치에서 파일 탐색기 창이 열립니다 — **claude_desktop_config.json**을 마우스 오른쪽 버튼으로 클릭 → Edit(Notepad)

  3. 추가:

    {
      "mcpServers": {
        "PNPC-MCP-Tally-Prime": {
          "command": "node",
          "args": ["D:\\Path\\To\\PNPC-MCP-Tally-Prime\\dist\\index.js"]
        }
      }
    }

    (경로에는 표시된 대로 이중 백슬래시를 사용하세요.)

  4. 저장한 후 Claude Desktop을 완전히 종료(File → Exit)하고 다시 실행하세요.

  5. 위와 동일하게 Tools 아이콘을 통해 확인하세요.

Perplexity Desktop / 기타 MCP 클라이언트

로컬 stdio 서버 구성을 허용하는 모든 MCP 클라이언트는 위에 표시된 것과 동일한 command/args JSON을 사용합니다. 해당 구성이 정확히 어디에 있는지 클라이언트 자체 문서를 참조하세요.

설정 (클라우드)

로컬 PC에서 실행 중인 TallyPrime 인스턴스에 연결할 수 없는 브라우저 기반 또는 모바일 LLM 클라이언트의 경우, 서버는 대신 OAuth로 보호된 액세스가 있는 소규모 웹 서비스로 실행될 수 있습니다. 이는 더 복잡합니다 — docs/HTTP_DEPLOYMENT.md를 참조하세요.

사용 가능한 도구 (총 28개)

날짜는 Tally의 자체 규칙에 따라 DD-MM-YYYY 형식을 사용합니다. 전체 기계 판독 가능 스키마: docs/TOOLS.md.

읽기

도구

입력

출력

get_ledgers

—

모든 원장(계정)

get_stock_items

—

모든 재고 품목

get_groups

—

계정 그룹(예: Sundry Debtors, Fixed Assets)

get_voucher_types

—

구성된 바우처 유형(Payment, Sales, Journal, ...)

get_cost_centres

—

모든 원가 중심

get_company_info

—

현재 열려 있는 회사의 세부 정보

get_vouchers

from, to

Day Book — 해당 날짜 범위의 바우처

get_ledger_vouchers

ledgerName, from, to

하나의 원장에 게시된 바우처 항목

get_profit_and_loss

from, to

P&L 명세서

get_trial_balance

from, to

시산표

get_balance_sheet

asOf

특정 날짜의 대차 대조표

get_stock_summary

asOf

특정 날짜의 재고 요약

get_bills_receivable

asOf

미수금 청구서

get_bills_payable

asOf

미지급금 청구서

쓰기

도구

입력

출력

create_sales_voucher

voucherData

바우처 번호를 포함한 확인 메시지

create_purchase_voucher

voucherData

바우처 번호를 포함한 확인 메시지

create_payment_voucher

voucherData

바우처 번호를 포함한 확인 메시지

create_receipt_voucher

voucherData

바우처 번호를 포함한 확인 메시지

create_journal_voucher

voucherData

바우처 번호를 포함한 확인 메시지

delete_voucher

voucherNumber

삭제 확인

도구

입력

출력

create_ledger

name, oldName?, parent, openingBalance?, maintainBillWise?, trn?, email?, website?, phone?, mobile?, billCreditPeriod?, creditLimit?, extraFields?

주어진 그룹 아래에 원장을 생성합니다. 또는 oldName이 전달되면 해당 기존 원장을 변경/이름 변경합니다. extraFields는 정확한 태그 이름으로 다른 모든 네이티브 Tally 원장 필드에 대한 이스케이프 해치입니다. 알려진 제한사항: 이 Tally 버전에서는 Address/State/Country/Pincode가 일반 태그를 통해 적용되지 않습니다 (실제 테스트로 확인됨).

create_voucher

voucherType, date, narration?, debitLedger, creditLedger, amount, debitBillName?, debitBillType?, creditBillName?, creditBillType?, debitCostCentre?, creditCostCentre?, costCategory?

하나의 차변 + 하나의 대변 항목으로 지급/수취/판매/구매/분개 바우처를 생성합니다. Bill-wise 할당(New Ref / Agst Ref)을 사용하려면 원장에 maintainBillWise가 설정되어 있어야 합니다. 원가 센터 할당은 단독으로 작동합니다.

update_voucher

voucherType, voucherNumber, date, narration?, debitLedger, creditLedger, amount, debitCostCentre?, creditCostCentre?, costCategory?

기존 바우처의 항목을 대체합니다. 유형 + 날짜 + 바우처 번호로 일치하며, 해당 바우처는 이미 존재하고 고유해야 합니다.

delete_voucher

voucherType, voucherNumber, date

바우처를 영구적으로 삭제합니다. 흔적이 남지 않으며 취소(보이기는 하지만 '취소됨'으로 표시됨)와는 다릅니다.

create_stock_journal

date, narration?, sourceItem, sourceQty, sourceRate, destItem, destQty, destRate, unit, godown?

하나의 재고 항목에서 다른 항목으로 재고를 이동하는(전송 또는 단순 변환) 재고 분개 바우처를 생성합니다. 재고 전용이며 원장 항목은 없습니다.

create_group

name, parent

상위 그룹 아래에 하위 계정 그룹을 생성합니다.

create_stock_item

name, group, unit, openingBalance?, openingRate?, description?, rateOfVat?, ignoreNegativeStock?, extraFields?

재고 항목을 생성합니다. extraFields는 정확한 태그 이름으로 다른 모든 네이티브 필드에 대한 이스케이프 해치입니다.

update_stock_item

name, group, unit

기존 재고 항목의 그룹/단위를 업데이트합니다.

delete_stock_item

name

재고 항목을 삭제합니다(거래가 게시된 경우 실패).

delete_master

collection, names

LEDGER, GROUP, STOCKITEM, VOUCHERTYPE, UNIT, GODOWN, COSTCATEGORY, COSTCENTRE 등 모든 유형의 마스터를 정확한 이름으로 하나 이상 삭제합니다.

⚠️ create_ledger / update_voucher / delete_stock_item / delete_master / delete_voucher는 기존 데이터를 수정하거나 제거합니다. 모델이 중요 데이터에 대해 이러한 도구를 사용하도록 허용하기 전에 Tally 백업을 유지하세요. 특히 delete_master와 delete_voucher는 실행 취소가 불가능합니다.

컨텍스트 전환

도구

입력

출력

set_company

companyName

TallyPrime의 활성 회사를 전환합니다. 다시 변경될 때까지 이후의 모든 호출에 영향을 미칩니다.

set_period

from, to

TallyPrime의 활성 보고 기간을 전환합니다. 다시 변경될 때까지 이후의 모든 보고서에 영향을 미칩니다.

이 도구들은 Tally 자체의 전역적이고 영구적인 상태를 변경합니다 (Tally 자체 UI에서 회사/기간을 전환하는 것과 동일) — 호출별 매개변수가 아닙니다. 동일한 Tally 인스턴스에 대해 여러 도구/세션을 실행 중인 경우, 한 번의 set_company/set_period 호출이 다른 모든 호출자가 다음에 보는 내용에 영향을 미칩니다.

set_company는 이미 Tally에서 열려 있는 회사로만 전환할 수 있습니다 (여러 회사를 동시에 열 수 있음) — 성공을 반환하지만 로드되지 않은 회사를 지정하면 효과가 없습니다. 먼저 Tally에서 회사를 열고 (파일 → 회사 선택), 그런 다음 이 도구를 통해 전환하세요.

SQL 캐시

도구

입력

출력

sync_to_sql

—

원장, 그룹, 재고 항목 및 바우처(최근 365일)를 로컬 인메모리 SQL 캐시로 가져옵니다.

query_sql

sql (SELECT만)

해당 캐시에 대해 읽기 전용 쿼리를 실행합니다. 테이블: ledgers(name, parent, closing_balance), groups(name, parent), stock_items(name, parent, closing_balance), vouchers(date, voucher_type, ledger, amount, narration)

환경 변수

변수

기본값

목적

TALLY_URL

http://localhost:9000

Tally의 HTTP 게이트웨이 주소

PORT

3939

npm run start:http의 포트 (원격 모드만)

TALLY_MCP_TOKEN

(설정 안 됨)

설정된 경우 HTTP 서버의 /mcp 엔드포인트에 필요한 Bearer 토큰 (원격 모드만)

이것을 다른 Tally MCP 커넥터와 함께 실행 중이신가요? 각 커넥터는 TallyPrime에서 고유한 게이트웨이 포트가 필요합니다 (F1 → 설정 → 연결) — 두 커넥터가 포트 9000을 공유할 수 없습니다. 이미 다른 커넥터가 9000을 사용 중이라면 이 커넥터를 위해 예를 들어 9001에 두 번째 게이트웨이를 열고, 패킹하기 전에 manifest.json의 mcp_config.env.TALLY_URL을 그에 맞게 편집하거나, MCP 클라이언트가 이 서버의 환경 구성을 허용하는 곳에 TALLY_URL을 직접 설정하세요.

소스에서 빌드하기

다운로드한 .mcpb를 사용하는 대신 코드를 수정하는 경우에만 필요합니다.

npm install --omit=dev   # production deps only
npm run build             # compiles src/ -> dist/

Node 버전 참고: 시스템의 node --version이 오래된 버전을 보고하는 경우, where node (Windows) / which -a node (macOS/Linux)로 PATH 상의 다른 위치에 최신 설치가 있는지 확인하고 위 명령어에 명시적으로 사용하세요. Claude Desktop 자체에 번들된 Node는 시스템 PATH와 관계없이 설치된 확장 프로그램을 실행하므로, 이는 빌드에만 영향을 미칩니다.

직접 .mcpb 패킹하기

npm install -g @anthropic-ai/mcpb   # one-time
mcpb validate manifest.json
mcpb pack . PNPC-MCP-Tally-Prime.mcpb

문제 해결

  • "Could not reach TallyPrime" — Tally가 실행 중이 아니거나, 포트 9000에서 게이트웨이가 활성화되지 않았습니다.

  • "Tally returned an empty response" — Tally는 실행 중이지만 열려 있는 회사가 없습니다.

  • create_ledger / create_voucher 실패 — 상위 그룹/원장 이름이 Tally와 정확히 일치해야 합니다(대소문자 및 공백 구분).

  • "Install Extension"을 클릭하고 .mcpb 파일을 선택했지만 대화상자나 오류 없이 동일한 화면만 표시됨: 일부 Claude Desktop 빌드에서 일관되지 않은 동작이 발생했습니다. 시도 직후 %APPDATA%\Claude\logs\main.log에서 새로운 Handling DXT/MCPB file: <path> 줄을 확인하세요:

    Select-String "Handling DXT/MCPB file" "$env:APPDATA\Claude\logs\main.log" | Select-Object -Last 5
    • 로그에 기록되었지만 다른 작업이 발생하지 않는 경우, 확인 대화상자가 화면 밖에서 렌더링되고 있을 수 있습니다(드물게, 다중 모니터/원격 데스크톱 설정) — 다른 창을 확인하세요.

    • 로그에 전혀 기록되지 않은 경우, 동일한 Extensions → Advanced 설정 화면에서 Install Unpacked Extension을 대신 사용하여 이 저장소의 루트 폴더를 지정하세요 — 해당 경로가 더 안정적인 방법입니다.

프로젝트 구조

src/
  tally.ts        Tally HTTP client: sends XML, handles connection/timeout errors
  clean.ts        Normalizes Tally's raw XML->JSON into predictable JSON
  templates.ts    Renders the Nunjucks XML templates in templates/
  db.ts           PGLite SQL cache: sync_to_sql / query_sql
  tools.ts        MCP tool definitions + XML request builders
  server.ts       Shared MCP Server construction (used by both entry points)
  index.ts        stdio entry point (local Claude Desktop)
  http-server.ts  HTTP entry point (remote clients)
templates/
  *.xml.njk       Nunjucks templates for each Tally XML request shape
manifest.json     Claude Desktop Extension manifest (manifest_version 0.3)

문서

로드맵 / 아직 지원되지 않는 기능

  • create_ledger의 원장 주소/주/국가/우편번호 필드 — Tally가 요청을 수락하지만 이러한 필드를 적용하지 않습니다. 여러 번의 시도와 Tally 자체 문서의 구조를 포함하여 이 TallyPrime 버전에 대한 올바른 XML 구조를 아직 찾지 못했습니다.

  • GST/VAT 관련 법정 보고서(예: GSTR-1, GSTR-3B, VAT 신고 형식)

  • 다른 MCP 호환 AI 클라이언트(예: OpenAI Codex)와의 테스트/패키징된 통합 — 서버 자체는 표준 MCP 서버(stdio/HTTP)이므로 본질적으로 Claude 전용은 아니지만, 위의 .mcpb 패키징 및 설치 단계는 Claude Desktop 전용이며 다른 클라이언트에 대해서는 아직 확인되지 않았습니다.

라이선스

ISC — LICENSE를 참조하세요. 초기 개발은 vaijaaaaa/Tally-MCP-Server 및 dhananjay1405/tally-mcp-server의 아이디어에서 영감을 받았습니다.


Available Tools

87 tools
confirm_writeA
Destructive

Post a previously-built preview to Tally — this is the only tool that actually writes, when the batch went through preview_write first. Takes the previewId from a prior preview_write call and sends that exact XML, unchanged, to Tally. A previewId can only be confirmed once — reusing an already-confirmed or expired one fails rather than silently reposting or reusing stale data.

Inputs: previewId (required).

create_cost_categoryA

Create a new Cost Category in TallyPrime (a grouping of cost centres, e.g. 'Branch', 'Project'). Required before creating a cost centre under a category that doesn't exist yet.

Inputs: name (required), allocateToRevenue, allocateToNonRevenue.

create_cost_centreA

Create a new Cost Centre in TallyPrime (e.g. a department, branch, or project used to tag voucher entries for cost tracking — see create_voucher's costCentre fields).

Inputs: name (required), parent, category.

create_credit_noteA

Create an item-invoice Credit Note in TallyPrime — a Sales return, reversing stock and revenue for returned items. Same shape as create_sales_invoice but with the debit/credit convention flipped, matching Purchase's sign pattern (a Credit Note is structurally a reverse Sales entry). Confirmed live on a real company: returning 5 units correctly increased the item's book quantity by exactly 5. Same godown and dual-role deletion caveats as create_sales_invoice apply.

Inputs: date (required), items (required), partyLedger (required), billName, +14 more.

create_debit_noteA

Create an item-invoice Debit Note in TallyPrime — a Purchase return, reversing stock and expense for returned items. Same shape as create_purchase_invoice but with the debit/credit convention flipped, matching Sales's sign pattern (a Debit Note is structurally a reverse Purchase entry). Confirmed live on a real company: returning 3 units correctly decreased the item's book quantity by exactly 3. Same godown and dual-role deletion caveats as create_purchase_invoice apply.

Inputs: date (required), items (required), partyLedger (required), billName, +14 more.

create_delivery_noteA

Create a Delivery Note in TallyPrime — an item-line inventory voucher recording goods dispatched to a customer before or without a full Sales invoice (e.g. against a Sales Order). Same item-line shape as create_sales_invoice (stock item, quantity, rate, Sales ledger per line) but ISINVOICE is set to No and there's no VAT/tax line — a Delivery Note doesn't invoice the customer, it just moves stock out and records the reference. Distinct from create_rejections_out, which has no party/ledger amount at all. IMPORTANT (confirmed live): the Delivery Note voucher type must be active in the company first — check in Tally's UI (voucher types can be turned off per company) — otherwise the API still reports CREATED:1 even though the voucher won't show up in any report or be findable by get_vouchers/delete_voucher until the type is turned on. Once active, get_vouchers and delete_voucher find it correctly. get_ledger_vouchers will still never show it, by design, not a gap — that tool deliberately excludes inventory-classified vouchers (see its own description). ALSO confirmed live: Delivery Note can silently stop auto-numbering via the gateway, same failure mode as item-invoice types (Sales/Purchase/Credit Note/Debit Note) — symptom is a blank EXCEPTIONS:1 with no useful error text (the real cause, 'Voucher No. is missing', only shows in Tally's own Import Data UI). If creation fails this way, pass voucherNumber explicitly (check get_vouchers for the next free number of this voucher type).

Inputs: date (required), items (required), partyLedger (required), buyerTrn, +8 more.

create_godownA

Create a new Godown/Location in TallyPrime, optionally nested under a parent godown (e.g. a sub-location under a main warehouse). Required before referencing a godown that doesn't exist yet on an invoice/voucher line — those fail with 'Godown does not exist!' otherwise. Pass the parent's plain name, not a dotted path (confirmed live: 'MAIN LOCATION.DUBAI' is invalid, 'MAIN LOCATION' as parent + 'DUBAI' as name is correct).

Inputs: name (required), parent.

create_groupA

Create a new account group in TallyPrime, nested under a parent group, or rename/reparent an existing one by passing oldName.

Inputs: name (required), parent (required), oldName.

create_job_work_in_orderA

Create a Job Work In Order in TallyPrime — used when this company is the job worker, booking an order to process raw materials a customer will supply, into a finished item the company will deliver back. Each item line is the finished item expected to be delivered eventually, plus a nested list of components — the raw materials the customer is expected to supply for that item. Reverse-engineered from a real manually-created Job Work In Order's own export (same technique used for Sales Order): the component list lives nested two levels deep, inside each item's own order allocation (VOUCHERCOMPONENTLIST.LIST inside BATCHALLOCATIONS.LIST inside ALLINVENTORYENTRIES.LIST), each component carrying its own nested BATCHALLOCATIONS.LIST with a PARENTITEM back-reference to the item it belongs to. Confirmed live: this structure creates cleanly (no VAT/tax lines, no per-item ledger allocation — just the one balancing party ledger entry for the total). Same voucher-type-active prerequisite as other Order-class vouchers, and orderNumber + each item's dueDate are REQUIRED (same reasoning as create_sales_order). Distinct from create_job_work_out_order, which is for the opposite direction (sending materials out to a job worker).

Inputs: date (required), items (required), orderNumber (required), partyLedger (required), +2 more.

create_job_work_out_orderA

Create a Job Work Out Order in TallyPrime — used when this company is the principal, sending raw materials out to a job worker (subcontractor) and expecting a finished item back. Mirror image of create_job_work_in_order: each item line is the finished item expected to be received from the job worker, plus a nested list of components — the raw materials this company will send out for that item. Same nested XML structure as create_job_work_in_order, with the accounting direction flipped (matching the existing Sales-side vs Purchase-side sign convention already used by create_sales_order vs create_purchase_order in this connector) since this voucher represents an inward expected receipt rather than an outward delivery. Confirmed live: creates cleanly with no exceptions. Same voucher-type-active prerequisite and required orderNumber/dueDate as create_job_work_in_order.

Inputs: date (required), items (required), orderNumber (required), partyLedger (required), +2 more.

create_ledgerB

Create a new ledger (account) in TallyPrime, or rename/update an existing one by passing oldName

Inputs: name (required), parent (required), pan, trn, +21 more.

create_material_inA

Create a Material In voucher in TallyPrime — records stock received back from a job worker (or any party holding your material for processing), tracked against that party's ledger without a real accounting posting (this is Tally's job-work memorandum tracking, not a purchase). Uses Tally's native 'Multi Consumption Voucher View' shape. EXTRAPOLATED from a genuine Tally-exported XML template for this exact voucher type, not verified against a real manually-created example in this project — verify carefully after use, especially on a company with godown/batch tracking enabled (pass godown on every item). If creation fails with LINEERROR 'Voucher date is missing' even though the date field is set correctly, the date is outside Tally's active period (Alt+F2) — call set_period to cover it and retry (confirmed live).

Inputs: date (required), items (required), partyLedger (required), narration, +1 more.

create_material_outA

Create a Material Out voucher in TallyPrime — records stock sent out to a job worker for processing, tracked against that party's ledger without a real accounting posting (job-work memorandum tracking, not a sale). Mirror of create_material_in. Same EXTRAPOLATED caveat and godown requirement apply. If creation fails with LINEERROR 'Voucher date is missing' even though the date field is set correctly, the date is outside Tally's active period (Alt+F2) — call set_period to cover it and retry (confirmed live).

Inputs: date (required), items (required), partyLedger (required), narration, +1 more.

create_physical_stockA

Create a Physical Stock voucher in TallyPrime — records a physical count and updates the stock item's book quantity to match it (that's the point of the voucher). Confirmed live against a real Tally-exported XML template (uses DIFFACTUALQTY=Yes at voucher level, not a per-line flag) after an earlier version of this tool was found to corrupt the closing balance to a nonsensical negative number — fixed and re-verified: counting 95 of an item that had 100 correctly closed the item at 95. It does not post any monetary/ledger write-off for the resulting shortage or excess value — do that separately with create_voucher if needed.

Inputs: date (required), items (required), narration, voucherNumber.

create_purchase_invoiceA

Create an item-invoice Purchase voucher in TallyPrime — mirror of create_sales_invoice for the buying side. A real invoice with stock item lines (quantity, rate), each posted to its own Purchase ledger, plus one optional VAT/tax line on the total. WARNING (confirmed live, same as create_sales_invoice): if the same party ledger or stock item is used in BOTH a Sales and a Purchase item-invoice, it can become undeletable via the API afterward — using it in only one of the two is fine and stays deletable. If it does happen, running Company Data → Rewrite in Tally itself clears it (confirmed live) — this is not a permanent lock.

Inputs: date (required), items (required), partyLedger (required), billName, +14 more.

create_purchase_orderA

Create a Purchase Order in TallyPrime — a future commitment to buy, before any goods move or invoicing happens. Same item-line shape as create_purchase_invoice/create_receipt_note but VCHTYPE is 'Purchase Order' and Tally classifies it as an Order-class voucher. Follow up with create_receipt_note (goods in) and/or create_purchase_invoice (billing) against the same party once goods actually arrive. Same voucher-type-active prerequisite as create_delivery_note (confirmed live). orderNumber and each item's dueDate are REQUIRED — same reasoning as create_sales_order: reverse-engineered from a real Sales Order export, confirmed the same live errors and Auto Retain numbering behavior apply here too.

Inputs: date (required), items (required), orderNumber (required), partyLedger (required), +2 more.

create_receipt_noteA

Create a Receipt Note in TallyPrime — an item-line inventory voucher recording goods received from a supplier before or without a full Purchase invoice (e.g. against a Purchase Order). Same item-line shape as create_purchase_invoice (stock item, quantity, rate, Purchase ledger per line) but ISINVOICE is set to No and there's no VAT/tax line — mirror of create_delivery_note on the buying side. Same caveat as create_delivery_note: the voucher type must be active in the company first, or it won't show up in get_vouchers/delete_voucher until it is. get_ledger_vouchers will still never show it, by design. If creation fails with LINEERROR 'Voucher date is missing' even though the date field is set correctly, the date is outside Tally's active period (Alt+F2) — call set_period to cover it and retry (confirmed live).

Inputs: date (required), items (required), partyLedger (required), buyerTrn, +9 more.

create_rejections_inA

Create a Rejections In voucher in TallyPrime — records goods rejected and returned to you (e.g. by a customer or a job worker returning defective components). Inventory movement only, same shape as a Sales/Purchase item line but with no party ledger. EXTRAPOLATED: no confirmed real-world XML example was available for this exact voucher type — built by analogy to Tally's other inventory-only voucher shapes (Physical Stock). Verify carefully after use — godown is required on every item unless the company has exactly one godown, in which case it auto-fills. If creation fails with LINEERROR 'Voucher date is missing' even though the date field is set correctly, the date is outside Tally's active period (Alt+F2) — call set_period to cover it and retry (confirmed live).

Inputs: date (required), items (required), narration, voucherNumber.

create_rejections_outA

Create a Rejections Out voucher in TallyPrime — records goods you're rejecting and returning outward (e.g. back to a supplier, or components you're sending back to a job worker as defective). Mirror of create_rejections_in. Same EXTRAPOLATED caveat and godown requirement apply. If creation fails with LINEERROR 'Voucher date is missing' even though the date field is set correctly, the date is outside Tally's active period (Alt+F2) — call set_period to cover it and retry (confirmed live).

Inputs: date (required), items (required), narration, voucherNumber.

create_sales_invoiceA

Create an item-invoice Sales voucher in TallyPrime — a real invoice with stock item lines (quantity, rate), each posted to its own Sales ledger, plus one optional VAT/tax line on the total. Distinct from create_voucher, which only supports plain ledger-to-ledger entries with no stock items. WARNING (confirmed live): if the same party ledger or stock item is used in BOTH a Sales and a Purchase item-invoice, it can become undeletable via the API afterward (returns 'Cannot be deleted!' even with zero balance) — using it in only one of the two is fine and stays deletable. If it does happen, running Company Data → Rewrite in Tally itself clears it (confirmed live) — this is not a permanent lock.

Inputs: date (required), items (required), partyLedger (required), billName, +14 more.

create_sales_orderA

Create a Sales Order in TallyPrime — a future commitment to sell, before any goods move or invoicing happens. Same item-line shape as create_sales_invoice/create_delivery_note but VCHTYPE is 'Sales Order' and Tally classifies it as an Order-class voucher, structurally different from Delivery Note's inventory-class. Follow up with create_delivery_note (dispatch) and/or create_sales_invoice (billing) against the same party once goods actually move. Same voucher-type-active prerequisite as create_delivery_note (confirmed live) — check it's on in the company before relying on this. orderNumber and each item's dueDate are REQUIRED (unlike other item-invoice tools, where the equivalent fields are optional): confirmed live that Tally rejects an Order-class voucher with 'Order No. is missing in Item Allocations' and separately 'Due Date of Order is missing in Item Allocations' without them. Reverse-engineered from a real manually-created Sales Order's own export: the UI's 'Order no.' field is backed by the voucher-level REFERENCE tag (independent of the voucher number — the real example had voucherNumber '1' and Order no. '12345' as genuinely different values), while the per-item Order No. and Due Date both live nested inside each item's BATCHALLOCATIONS.LIST, not as direct ALLINVENTORYENTRIES fields as their names might suggest. Also confirmed live: Tally silently reassigns its own voucher number for Order-class vouchers regardless of an explicit voucherNumber passed in (its 'Auto Retain' numbering style for this voucher type) — check the actual assigned number via get_vouchers after creating one, don't assume the value you passed was used.

Inputs: date (required), items (required), orderNumber (required), partyLedger (required), +2 more.

create_sales_quotationA

Create a Sales Quotation in TallyPrime — a pre-order price quote to a prospective customer, one step before create_sales_order. Same item-line shape as create_sales_order, including the same orderNumber (REFERENCE) and per-item dueDate requirements — confirmed live that Tally classifies Sales Quotation as an Order-class voucher (PARENT 'Sales Order' in get_voucher_types) and rejects it the same way without them. Same voucher-type-active prerequisite as create_delivery_note. Follow up with create_sales_order once the customer accepts.

Inputs: date (required), items (required), orderNumber (required), partyLedger (required), +2 more.

create_stock_groupA

Create a new Stock Group in TallyPrime, nested under a parent stock group. Distinct from create_group (account groups like Sundry Debtors) — this is the category stock items are filed under (create_stock_item's 'group' field). Required before creating a stock item under a brand-new category that doesn't exist yet.

Inputs: name (required), parent (required).

create_stock_itemC

Create a new stock item in TallyPrime

Inputs: name (required), unit (required), group (required), hsnCode, +13 more.

create_stock_journalA

Create a Stock Journal voucher in TallyPrime, moving inventory from one or more source stock items to one or more destination stock items (transfer, manufacturing-style conversion with multiple raw materials consumed and/or multiple finished/by-products produced, etc). Inventory-only — no ledger entries. Every source/destination line's godown is auto-filled only when this company has exactly one godown; if it has more than one (e.g. Dubai/Sharjah/Ajman), godown is required on each line and the call fails naming the available godowns rather than guessing (previously an omitted godown was silently dropped — blank EXCEPTIONS:1, no error text — this is now caught explicitly instead of guessing wrong).

Inputs: date (required), sources (required), destinations (required), narration, +3 more.

create_unitA

Create a new Unit of Measure in TallyPrime — a simple unit (e.g. 'Kg', 'Box', 'Ltr') by default, or a compound unit (e.g. 'Box of 12 Nos') by passing baseUnit/additionalUnit/conversion. Required before creating or invoicing a stock item in a unit that doesn't exist yet — stock item/invoice tools fail with 'Unit does not exist!' otherwise. For a compound unit, both baseUnit and additionalUnit must already exist as simple units first (confirmed live pattern: create both simple units, then the compound unit referencing them). A simple unit's symbol (and baseUnit/additionalUnit, since those reference existing simple units' symbols) cannot contain whitespace — confirmed live: Tally rejects that with 'Master name contains invalid characters', checked client-side before this ever reaches Tally. A compound unit's own display name (e.g. 'Box of 12 Nos') can still contain spaces.

Inputs: symbol (required), baseUnit, conversion, formalName, +2 more.

create_voucherA

Create a new voucher (e.g. Payment, Receipt, Sales, Purchase, Journal) in TallyPrime. Either pass debitLedger/creditLedger/amount for a simple 2-leg voucher, or pass 'entries' for a voucher with 3+ lines (e.g. one payment split across several expense ledgers). Normally omit voucherNumber and let Tally auto-number — but if Tally's numbering series doesn't pick up correctly (confirmed live: a company on a 'PNPC/2026/...' series silently restarted from '1' instead of continuing it), pass voucherNumber explicitly to force the value you want; check get_vouchers for the correct next number first.

Inputs: date (required), voucherType (required), mode, amount, +23 more.

create_vouchers_batchA

Post many vouchers (Journal, Payment, Receipt, etc. — same shape as create_voucher, one entry per voucher) in one call, for bulk work where posting one at a time is impractical (e.g. hundreds of balance-confirmation adjustment journals). Internally splits into chunks (default 10, max 50 — Tally's own gateway has a 10-second timeout per request, and a bigger single import risks silently exceeding it) and, after each chunk posts, runs ONE bulk query to confirm exactly which vouchers in that chunk actually exist in Tally now — this always runs, even if the post itself errored or timed out, because a client-side timeout does not mean Tally didn't still create some or all of them server-side; retrying without checking first risks posting duplicates. Verification matches each voucher back by (voucherType, narration) — NOT voucherNumber, confirmed live to be unreliable even when set explicitly (Tally silently reassigned its own auto-series number instead for a Journal voucher); reference was tried next and also came back empty on read. narration is what's confirmed live to persist exactly as sent, so it's REQUIRED and must be non-empty on every voucher, and must be unique per voucherType across the whole batch — two vouchers sharing the same (voucherType, narration) can't be told apart afterward and are rejected up front as invalid rather than silently mismatched (e.g. embed each row's own reference/id in the narration text). The result names exactly which vouchers were confirmed and which were not, per chunk, so a partial failure can be retried by resending only the ones that didn't land — never blindly resend the whole batch. Does not go through preview_write/confirm_write given the scale involved; sending a small batch (2-3 vouchers) first to confirm shape/ledger names before a large run is recommended.

Inputs: vouchers (required), chunkSize.

create_voucher_typeA

Create a new custom Voucher Type in TallyPrime (e.g. 'Bank Payment' as a sub-type of 'Payment', with its own numbering series/abbreviation) — or rename/reconfigure an existing one by passing oldName. Base types to derive from: 'Payment', 'Receipt', 'Journal', 'Contra', 'Sales', 'Purchase', 'Credit Note', 'Debit Note', 'Stock Journal', 'Physical Stock', etc. — must be an exact existing voucher type name (check get_voucher_types first). Setting numberingMethod explicitly is useful given the confirmed-live issue where some Tally configurations stop auto-numbering item-invoice-mode voucher types via the XML gateway unless a voucherNumber is supplied on every create call — see create_sales_invoice's voucherNumber note. Confirmed live separately: a brand-new custom voucher type created WITHOUT numberingMethod set can accept vouchers with a completely blank voucher number (not even '1') — pass numberingMethod: 'Automatic' explicitly to avoid ending up with unreferenceable vouchers you can only look up/delete by date.

Inputs: name (required), parent (required), oldName, extraFields, +4 more.

delete_masterA
DestructiveIdempotent

Delete one or more masters (ledger, group, stock item, voucher type, unit, godown, cost centre, etc.) from TallyPrime by name. If a master was used in a voucher you're also deleting, delete the voucher first and confirm it succeeded before calling this — doing both in the same parallel batch can race (the master delete reaching Tally before the voucher delete has committed), confirmed live. If a ledger/stock item was used in both a Sales AND a Purchase item-invoice, it may return 'Cannot be deleted!' permanently even with no transactions left — this is fixed by running Company Data → Rewrite in Tally itself (confirmed live), not by retrying or sequencing.

Inputs: names (required), collection (required).

delete_stock_itemA
DestructiveIdempotent

Delete a stock item from TallyPrime. Fails if it has transactions posted against it. If deleting a voucher that used this item in the same turn, delete the voucher first and confirm it succeeded before calling this — doing both in parallel can race (confirmed live). If this item was used in both a Sales AND a Purchase item-invoice, it may return 'Cannot be deleted!' even with zero balance and no transactions left — fixed by Company Data → Rewrite in Tally itself (confirmed live), not by retrying.

Inputs: name (required).

delete_voucherA
DestructiveIdempotent

Permanently delete an existing voucher from TallyPrime — removes it entirely with no trace (distinct from cancelling, which keeps it visible but marked Cancelled). The voucher is matched by type + date + voucher number, so that combination must be unique and must exactly match an existing voucher (use get_ledger_vouchers or get_vouchers first to confirm it). This has no undo. Refuses if another voucher type shares the same number on that date (confirmed live: Tally's lookup ignores voucher type and can silently target the wrong one) — resolve the collision in Tally first.

Inputs: date (required), voucherType (required), voucherNumber (required).

get_audit_logA
Read-only

Read this connector's append-only audit log — every tool call made through it (read or write), with timestamp, arguments, outcome (success/error/denied), and a best-effort Tally company tag. Entries older than 90 days are permanently deleted (checked once per server startup, not kept indefinitely) — this is not a full historical record beyond that window. Use this to review what an agent actually did against this Tally company, e.g. before trusting a session's claimed results, or to hand a reviewer a plain record of every write made in a given period.

Inputs: limit, format, toDate, company, +3 more.

get_balance_sheetB
Read-only

Get the Balance Sheet from TallyPrime as of a given date

Inputs: asOf (required).

get_bills_payableA
Read-only

Get outstanding Bills Payable from TallyPrime as of a given date

Inputs: asOf (required).

get_bills_receivableA
Read-only

Get outstanding Bills Receivable from TallyPrime as of a given date

Inputs: asOf (required).

get_cash_flowA
Read-only

Get the Cash Flow statement from TallyPrime for a date range — Tally's own canned report, reachable directly via a plain Export Data request (confirmed live, unlike the VAT/GST return reports). Returns Tally's native monthly-period breakdown shape (DSPPERIOD/DSPACCINFO arrays) as-is.

Inputs: to (required), from (required).

get_company_infoA
Read-only

Get the currently open company info from TallyPrime

Inputs: no named parameters.

get_cost_centresA
Read-only

Get all cost centres from TallyPrime

Inputs: no named parameters.

get_funds_flowA
Read-only

Get the Funds Flow statement from TallyPrime for a date range — Tally's own canned report, reachable directly via a plain Export Data request. Returns Tally's native monthly-period breakdown shape as-is.

Inputs: to (required), from (required).

get_groupsA
Read-only

Get all account groups (e.g. Sundry Debtors, Fixed Assets) from TallyPrime

Inputs: no named parameters.

get_gst_liability_summaryA
Read-only

Get an India GST liability summary for a date range. Same design as get_vat_liability_summary — each row is a GST ledger (CGST/SGST/IGST, input/output/payable/receivable/RCM) with its closing balance for the period, classified as input/output/rcm/other ('rcm' kept separate from input/output — reverse-charge liability is the thing that's easily missed manually), tagged 'structural' (Tally's Type-of-duty/tax field = GST) or 'name_pattern' (matched Input/Output CGST/SGST/IGST or GST Payable/Receivable/RCM naming) — both signals used together for the same reason: confirmed live that Tally's structural tag alone misses every ledger with real activity in a real company file. Deliberately excludes generic expense ledgers that merely mention GST in their name (a freight ledger, a GST write-off/ineligible-ITC ledger) — those aren't tax liability lines and including them would misstate the position. netTotal sums all rows using Tally's own debit/credit sign convention. Not a canned GSTR export — reconstructed from ledger balances. If no matching ledgers exist, returns an explicit note instead of a bare zero.

Inputs: to (required), from (required).

get_health_checkA
Read-only

Check whether this connector is actually safe and working right now: is Tally's gateway reachable, is a company open (and which one), what TALLY_URL it's talking to, whether read-only mode is on, and which tools (if any) are explicitly disabled. Use this before trusting a session, or when something feels off, instead of inferring connector state from a single tool call's success/failure.

Inputs: no named parameters.

get_journal_registerA
Read-only

Get the Journal Register from TallyPrime for a date range — a month-by-month summary of Journal voucher activity, same design as get_sales_register.

Inputs: to (required), from (required).

get_ledgersA
Read-only

Get ledgers (accounts) from TallyPrime. Omit query to get every ledger. Pass query to instead get a fuzzy-ranked shortlist of the closest-matching ledger names — useful when you have a rough or partial name (e.g. from a client document) and need Tally's exact spelling before creating a voucher or a new ledger, without pulling and scanning the entire ledger list yourself. Matches on exact/prefix/substring, then falls back to a loose in-order character match for abbreviations and typos (e.g. 'vro' finds 'VRO Technology'). Returns at most the top 20 matches, ranked best first; an empty result means create the ledger — nothing close enough exists yet. Each ledger includes VATTINNUMBER, VATDEALERTYPE, STATE, and COUNTRY (the values set via create_ledger's trn/vatDealerType/state/country fields, blank if never set), plus GSTIN, PAN, GSTREGISTRATIONTYPE, GSTTYPEOFSUPPLY, and CONTACTPERSON (set via create_ledger's gstin/pan/gstRegistrationType/gstTypeOfSupply/contactPerson fields — GSTIN/PAN/GSTREGISTRATIONTYPE are India's fields, distinct from trn/VATDEALERTYPE which are UAE-specific; a company only uses one country's set or the other, not both) — check the relevant ones before creating a Sales/Purchase invoice (or Credit/Debit Note, Delivery/Receipt Note) for that party: Tally itself defaults a new invoice's Buyer/Place-of-Supply details from the party ledger's own master data, so use these same values for buyerTrn/buyerState/buyerCountry rather than leaving them blank or guessing. Only ask the user to confirm instead of defaulting when the party has multiple registered delivery locations/addresses and it's genuinely unclear which one applies to this specific transaction (confirmed live: a real customer ledger can carry dozens of named addresses, and one invoice's Buyer address and Consignee/Ship-to address can legitimately differ from both the ledger's default and each other).

Inputs: query.

get_ledger_vouchersA
Read-only

Get all voucher entries posted to a specific ledger within a date range

Inputs: to (required), from (required), ledgerName (required).

get_payment_registerA
Read-only

Get the Payment Register from TallyPrime for a date range — a month-by-month summary of Payment voucher activity, same design as get_sales_register. For Receipt vouchers specifically, use get_receipts_and_payments instead — Tally has no separate standalone 'Receipt Register' report reachable this way (confirmed live: 'Could not find Report').

Inputs: to (required), from (required).

get_profit_and_lossB
Read-only

Get the Profit & Loss statement from TallyPrime for a date range

Inputs: to (required), from (required).

get_purchase_registerA
Read-only

Get the Purchase Register from TallyPrime for a date range — a month-by-month summary of Purchase voucher activity, same design as get_sales_register.

Inputs: to (required), from (required).

get_ratio_analysisA
Read-only

Get the Ratio Analysis report from TallyPrime for a date range (Working Capital, Current Ratio, Quick Ratio, Inventory Turnover, Debtors/Creditors Turnover, and similar standard ratios) — Tally's own canned report, reachable directly via a plain Export Data request. Returns Tally's native RATIONAME/value array shape as-is.

Inputs: to (required), from (required).

get_receipts_and_paymentsA
Read-only

Get the Receipts and Payments report from TallyPrime for a date range — a cash/bank-ledger-wise view combining Receipt and Payment activity, Tally's own canned report. This is the closest reachable equivalent to a standalone Cash Book/Bank Book — Tally's actual 'Cash Book'/'Bank Book' menu reports are not reachable via a plain Export Data request (confirmed live: 'Could not find Report'), even though they're registered report names — for a single cash or bank ledger's own transaction history instead, use get_ledger_vouchers with that ledger's name.

Inputs: to (required), from (required).

get_reorder_statusA
Read-only

Get the Reorder Status report from TallyPrime for a date range — stock items with a reorder level configured, and where their current quantity stands against it (closingStock, onPurchaseOrder, onSaleOrder, reorderLevel, shortfall, minimumQty, requiredQty per row). Tally's own report returns every stock item regardless of reorder setup (confirmed live: a 10,770-item company with no reorder levels configured returned a ~1.4MB all-null dump) — this tool filters that down to only rows that actually have a reorder level set, since that's the only subset the report can say anything useful about. An empty rows array with a note means no items have a reorder level configured at all, not an error — use get_stock_summary for a plain quantity view of every item regardless of reorder setup.

Inputs: to (required), from (required).

get_sales_registerA
Read-only

Get the Sales Register from TallyPrime for a date range — a month-by-month summary of Sales voucher activity, Tally's own canned report reachable directly via a plain Export Data request. For individual Sales voucher line detail (not just monthly totals), use get_vouchers or get_ledger_vouchers instead.

Inputs: to (required), from (required).

get_stock_itemsA
Read-only

Get all stock items from TallyPrime. Each item includes NAME, PARENT, CLOSINGBALANCE, plus DESCRIPTION, PARTNUMBER, COSTINGMETHOD (e.g. 'Avg. Cost', 'FIFO'), GSTTYPEOFSUPPLY ('Goods'/'Services') — blank/empty if never set on that item — and GSTAPPLICABLE (read-only: Tally computes this from the item's own GST configuration, it cannot be set directly). Also includes GSTDETAILS: {hsnCode, taxability, applicableFrom, isReverseChargeApplicable, gstIneligibleItc} (or null if no GST Details entry exists at all), taken from Tally's own date-versioned GST Details list — set via create_stock_item's/update_stock_item's hsnCode/taxability/isReverseChargeApplicable/gstIneligibleItc fields. When an item has more than one dated entry (a rate/HSN change over time), this shows only the one with the latest applicableFrom, not the full history.

Inputs: no named parameters.

get_stock_summaryA
Read-only

Get the Stock Summary report from TallyPrime as of a given date

Inputs: asOf (required).

get_trial_balanceA
Read-only

Get the Trial Balance from TallyPrime for a date range

Inputs: to (required), from (required).

get_vat_liability_summaryA
Read-only

Get a UAE VAT liability summary for a date range. Each row is a VAT ledger with its closing balance for the period, classified as input/output/rcm/other — 'rcm' (reverse charge) is kept separate from plain input/output because reverse-charge liability is the thing that's easily missed manually, even though it nets to a wash for most businesses — tagged with how it was found — 'structural' (Tally's own Type-of-duty/tax field is set to VAT on that ledger) or 'name_pattern' (matched Input/Output/Payable/Receivable VAT naming). Both signals are used together, not one alone — confirmed live on real company data that Tally's structural tag is precise but has near-zero recall: every properly-tagged ledger had a zero balance, while the ledgers actually carrying real money were created without that tag set at all. Not filtered by any particular parent group — real companies were confirmed to scatter these ledgers across many different groups, not one standard group. netTotal sums all rows using Tally's own debit/credit sign convention. Not Tally's canned VAT return report (confirmed live it isn't reachable via a plain Export Data request) — reconstructed from ledger balances the same way get_profit_and_loss is. If no matching ledgers exist, returns an explicit note instead of a bare zero — a company with no VAT ledgers (not registered, or unrecognizable naming) is a different fact from a real zero liability period.

Inputs: to (required), from (required).

get_vouchersA
Read-only

Get vouchers (Day Book) from TallyPrime filtered by date range. Returns a flat array of rows (guid, date, voucher_type, voucher_number, reference, party_ledger, amount, narration) — headers only, no stock item or ledger line detail (use get_ledger_vouchers or query_sql for that). Rebuilt on the same Voucher collection query sync_vouchers_to_sql already uses: an earlier version called Tally's canned 'Day Book' report directly, which was confirmed live to silently ignore the date range entirely (returning the same fixed set regardless of what was requested, even for a year before the company's books start) — this version correctly scopes to the requested range.

Inputs: to (required), from (required).

get_voucher_typesA
Read-only

Get all voucher types configured in TallyPrime (e.g. Payment, Sales, Journal)

Inputs: no named parameters.

preview_writeA
Read-only

Build the exact XML for any write tool WITHOUT sending it to Tally — nothing is touched. Returns a previewId plus a plain-English description and the raw XML, so you (or whoever's reviewing) can see precisely what would happen before it happens. Use this instead of calling a create_*/update_*/delete_* tool directly whenever you want a human to review a batch of changes first — e.g. drafting several vouchers from a folder of client documents, where posting the wrong one is costly. Every applicable safety check this tool would normally run (e.g. the voucher-type collision check on update_*/delete_voucher) runs now, at preview time, so the preview already reflects any refusal. A preview expires after 15 minutes and is single-use — call confirm_write with its previewId to actually post it, or just don't confirm it if it's wrong. Never touches Tally with a write of its own (a create_* preview makes no gateway call at all; an update_*/delete_* preview only makes the same read-only collision-check query that tool would normally make) — so unlike every other write tool, preview_write still works even when read-only mode is on. confirm_write is the one that's actually blocked by read-only mode.

Inputs: args (required), toolName (required).

query_sqlA
Read-only

Run a read-only SQL SELECT query against this session's in-memory cache (gone when the session ends). Tables: ledgers(name, parent, closing_balance, trn, state, country), groups(name, parent), stock_items(name, parent, closing_balance), vouchers(guid, date, voucher_type, voucher_number, party_ledger, amount, narration), voucher_items(voucher_guid, date, voucher_type, voucher_number, stock_item, qty, rate, amount, is_deemed_positive, godown, batch), voucher_ledger_entries(voucher_guid, date, voucher_type, voucher_number, ledger, amount, is_deemed_positive, cost_centre, bill_name, bill_type, description) — all six populated only by explicitly calling sync_to_sql/sync_vouchers_to_sql/sync_voucher_items_to_sql/sync_voucher_ledger_entries_to_sql first. Movement analysis, godown-wise stock, and batch/ageing detail are just SELECTs over voucher_items — there is no separate report tool for them. Splitting a ledger's balance apart by voucher (e.g. a combined VAT ledger into Output vs Input), or reconciling a party ledger's movements voucher by voucher, is just a SELECT over voucher_ledger_entries the same way — voucher_ledger_entries.amount is signed (negative debit, positive credit), so GROUP BY ledger, voucher_type with SUM(amount) is the natural query. profit_and_loss(ledger_name, group_name, closing_balance, period_from, period_to), stock_summary(name, parent, opening_qty, closing_qty, opening_value, closing_value, as_of_date), balance_sheet(group_name, amount, as_of_date), trial_balance(name, debit_amount, credit_amount, period_from, period_to), vat_summary(ledger_name, category, closing_balance, period_from, period_to), and gst_summary(ledger_name, category, closing_balance, period_from, period_to) are populated automatically, no separate sync step — every get_profit_and_loss/get_stock_summary/get_balance_sheet/get_trial_balance/get_vat_liability_summary/get_gst_liability_summary call refreshes its table with that call's result, so a follow-up question about the same report can query it here instead of re-fetching from Tally. Each of these six only ever holds the most recent call's data, not a history — re-call the report tool if you need a different period. Every call here checks which company is actually open in Tally right now against what the cache was last synced/queried for, however that company was arrived at (set_company, Tally's own UI, or a connector restart) — a mismatch clears the stale cache and refuses to run, rather than silently answering with a previous company's rows under the new company's name.

Inputs: sql (required).

set_bill_of_materialsA
DestructiveIdempotent

Attach a Bill of Materials (recipe) to an existing finished-goods stock item, so a Manufacturing/Stock Journal producing this item can have its component quantities computed from a fixed ratio instead of typed by hand every time. Uses Tally's native MULTICOMPONENTLIST.LIST structure. This is a pure convenience layer over create_stock_journal — it does not affect stock or post anything by itself; you still call create_stock_journal to actually record a production run, scaling each component's qty by the ratio to basicQty yourself (this tool does not auto-compute that scaling for you). EXTRAPOLATED from a genuine Tally-exported XML template's stock item master shape, not reverse-engineered from a real manually-created BOM — verify carefully after use, especially natureOfItem's accepted values.

Inputs: stockItem (required), components (required), unit, basicQty, +1 more.

set_companyA
Read-only

Switch TallyPrime's active company context. Changes which company subsequent tool calls and reports operate on — validate the name with get_ledgers/get_company_info or the company list first

Inputs: companyName (required).

set_periodA
Read-only

Switch TallyPrime's active reporting period. Changes the global from/to date context used by Tally for subsequent report queries until changed again

Inputs: to (required), from (required).

sync_to_sqlA
Read-only

Pull ledgers, groups, and stock items from TallyPrime into this session's SQL cache (in-memory — gone when this session ends), so query_sql can run fast arbitrary queries without hitting Tally each time. Every sync/query tool checks which company is actually open in Tally right before touching the cache and clears it if that's changed since the last one — however the switch happened (set_company, Tally's own UI, or a connector restart) — so a stale company's rows never silently answer under a new company's name; the return message says so when it happens. Does NOT sync vouchers — use sync_vouchers_to_sql for those, one date range at a time.

Inputs: no named parameters.

sync_voucher_items_to_sqlA
Read-only

Pull voucher INVENTORY LINE ITEMS (stock item, qty, rate, amount, godown, batch — one row per item per batch allocation) for one date range into this session's SQL cache, so query_sql can compute movement analysis, godown-wise stock, or batch detail directly. This is the raw data those analyses need — Tally has no exportable 'Movement Analysis'/'Stock Ageing Analysis'/'Godown Summary' report reachable over the gateway (confirmed live against all 138 registered report names, and confirmed live that per-godown $ClosingBalance/SVGODOWNNAME scoping doesn't work either), so this connector doesn't try to replicate those as report tools — pull the line items with this, then write the aggregation as SQL. qty/amount are UNSIGNED as Tally stores them on the inventory entry; use is_deemed_positive together with voucher_type to work out inward vs outward direction. A voucher with no stock items (Payment, Journal, etc.) contributes zero rows, not an empty one. Same chunked, additive-by-date-range model and same timeout caution as sync_vouchers_to_sql — quarterly/monthly chunks for a busy company. Checks which company is actually open in Tally first and clears the whole cache if it's changed since the last sync/query — however that happened, not just via set_company.

Inputs: to (required), from (required).

sync_voucher_ledger_entries_to_sqlA
Read-only

Pull voucher LEDGER LINES (which ledger each voucher posted to, the amount, cost centre, and bill allocation — one row per ledger line per bill allocation) for one date range into this session's SQL cache. This is the piece get_vouchers/sync_vouchers_to_sql can't give you — those return only each voucher's single overall total, not which ledgers it actually posted to and for how much. Use this whenever a ledger's balance needs to be broken down by the vouchers that make it up — e.g. a combined VAT ledger split into Output vs Input (GROUP BY ledger, voucher_type), or reconciling a party ledger's movements voucher by voucher. amount is SIGNED (negative for a debit line, positive for a credit line — confirmed live: a Sales invoice's party ledger line comes back negative while its Sales/VAT lines come back positive, summing to zero across the voucher) — sum it directly. description carries a ledger line's 'Additional Descriptions for Ledgers' text (several lines joined with ' | ', null where none). Same chunked, additive-by-date-range model and same timeout caution as sync_vouchers_to_sql/sync_voucher_items_to_sql — quarterly/monthly chunks for a busy company. Checks which company is actually open in Tally first and clears the whole cache if it's changed since the last sync/query — however that happened, not just via set_company.

Inputs: to (required), from (required).

sync_vouchers_to_sqlA
Read-only

Pull voucher HEADERS (date, type, number, party ledger, amount, narration — not line items) for one date range into this session's SQL cache (in-memory, gone when the session ends), so query_sql can aggregate/report on them (e.g. sales by customer by month) without re-fetching from Tally. Call this once per chunk to build up full multi-year history for the CURRENTLY OPEN company within this session — re-running for the SAME range just refreshes it (safe to re-run), and each call only touches vouchers within its own date range, so calling it for 2024 then 2025 gives you both, not just the latest. Checks which company is actually open in Tally first and clears the whole cache if it's changed since the last sync/query — however that happened, not just via set_company — so a prior company's vouchers never silently mix into this one's results. IMPORTANT: pick a chunk size that won't time out — a full year (~7,500 vouchers here) took ~6s against the 10s request timeout; prefer quarterly or monthly chunks for a busy company, and back off further if a call times out. Does not include stock item / ledger line detail (see get_ledger_vouchers/get_vouchers for that).

Inputs: to (required), from (required).

update_credit_noteA
DestructiveIdempotent

Update an existing item-invoice Credit Note in TallyPrime, replacing its item lines, party, and narration. Same fields as create_credit_note, plus voucherNumber. Matched by date + voucher number — use get_ledger_vouchers or get_vouchers first to confirm it exists and is unique. Refuses if another voucher type shares the same number on that date (confirmed live: Tally's Alter lookup ignores voucher type and can silently corrupt the wrong one) — resolve the collision in Tally first if that happens.

Inputs: date (required), items (required), partyLedger (required), voucherNumber (required), +14 more.

update_debit_noteA
DestructiveIdempotent

Update an existing item-invoice Debit Note in TallyPrime, replacing its item lines, party, and narration. Same fields as create_debit_note, plus voucherNumber. Matched by date + voucher number — use get_ledger_vouchers or get_vouchers first to confirm it exists and is unique. Refuses if another voucher type shares the same number on that date (confirmed live: Tally's Alter lookup ignores voucher type and can silently corrupt the wrong one) — resolve the collision in Tally first if that happens.

Inputs: date (required), items (required), partyLedger (required), voucherNumber (required), +14 more.

update_delivery_noteA
DestructiveIdempotent

Update an existing Delivery Note in TallyPrime, replacing its item lines, party, and narration. Same fields as create_delivery_note, plus voucherNumber. Matched by date + voucher number — use get_ledger_vouchers or get_vouchers first to confirm it exists and is unique. Refuses if another voucher type shares the same number on that date (confirmed live: Tally's Alter lookup ignores voucher type and can silently corrupt the wrong one) — resolve the collision in Tally first if that happens.

Inputs: date (required), items (required), partyLedger (required), voucherNumber (required), +8 more.

update_job_work_in_orderA
DestructiveIdempotent

Update an existing Job Work In Order in TallyPrime, replacing its item lines (and their component lists), party, order number, and narration. Same fields as create_job_work_in_order, plus voucherNumber. Matched by date + voucher number — use get_ledger_vouchers or get_vouchers first to confirm it exists and is unique. Refuses if another voucher type shares the same number on that date (confirmed live: Tally's Alter lookup ignores voucher type and can silently corrupt the wrong one) — resolve the collision in Tally first if that happens.

Inputs: date (required), items (required), orderNumber (required), partyLedger (required), +2 more.

update_job_work_out_orderA
DestructiveIdempotent

Update an existing Job Work Out Order in TallyPrime, replacing its item lines (and their component lists), party, order number, and narration. Same fields as create_job_work_out_order, plus voucherNumber. Same matching/collision caveats as update_job_work_in_order.

Inputs: date (required), items (required), orderNumber (required), partyLedger (required), +2 more.

update_material_inA
DestructiveIdempotent

Update an existing Material In voucher in TallyPrime, replacing its item lines and narration. Same fields as create_material_in, plus voucherNumber. Matched by date + voucher number — use get_ledger_vouchers or get_vouchers first to confirm it exists and is unique. Refuses if another voucher type shares the same number on that date (confirmed live: Tally's Alter lookup ignores voucher type and can silently corrupt the wrong one) — resolve the collision in Tally first if that happens.

Inputs: date (required), items (required), partyLedger (required), voucherNumber (required), +1 more.

update_material_outA
DestructiveIdempotent

Update an existing Material Out voucher in TallyPrime, replacing its item lines and narration. Same fields as create_material_out, plus voucherNumber. Same matching/collision caveats as update_material_in.

Inputs: date (required), items (required), partyLedger (required), voucherNumber (required), +1 more.

update_physical_stockA
DestructiveIdempotent

Update an existing Physical Stock voucher in TallyPrime, replacing its counted item lines and narration. Same fields as create_physical_stock, plus voucherNumber. Matched by date + voucher number — use get_ledger_vouchers or get_vouchers first to confirm it exists and is unique. Refuses if another voucher type shares the same number on that date (confirmed live: Tally's Alter lookup ignores voucher type and can silently corrupt the wrong one) — resolve the collision in Tally first if that happens.

Inputs: date (required), items (required), voucherNumber (required), narration.

update_purchase_invoiceA
DestructiveIdempotent

Update an existing item-invoice Purchase voucher in TallyPrime, replacing its item lines, party, and narration. Same fields as create_purchase_invoice, plus voucherNumber. Matched by date + voucher number — use get_ledger_vouchers or get_vouchers first to confirm it exists and is unique. Refuses if another voucher type shares the same number on that date (confirmed live: Tally's Alter lookup ignores voucher type and can silently corrupt the wrong one) — resolve the collision in Tally first if that happens.

Inputs: date (required), items (required), partyLedger (required), voucherNumber (required), +14 more.

update_purchase_orderA
DestructiveIdempotent

Update an existing Purchase Order in TallyPrime, replacing its item lines, party, order number, and narration. Same fields as create_purchase_order, plus voucherNumber. Same matching/collision caveats as update_sales_order.

Inputs: date (required), items (required), orderNumber (required), partyLedger (required), +2 more.

update_receipt_noteA
DestructiveIdempotent

Update an existing Receipt Note in TallyPrime, replacing its item lines, party, and narration. Same fields as create_receipt_note, plus voucherNumber. Same matching/collision caveats as update_delivery_note.

Inputs: date (required), items (required), partyLedger (required), voucherNumber (required), +9 more.

update_rejections_inA
DestructiveIdempotent

Update an existing Rejections In voucher in TallyPrime, replacing its item lines and narration. Same fields as create_rejections_in, plus voucherNumber. Same matching/collision caveats as update_material_in.

Inputs: date (required), items (required), voucherNumber (required), narration.

update_rejections_outA
DestructiveIdempotent

Update an existing Rejections Out voucher in TallyPrime, replacing its item lines and narration. Same fields as create_rejections_out, plus voucherNumber. Same matching/collision caveats as update_material_in.

Inputs: date (required), items (required), voucherNumber (required), narration.

update_sales_invoiceA
DestructiveIdempotent

Update an existing item-invoice Sales voucher in TallyPrime, replacing its item lines, party, and narration. Same fields as create_sales_invoice, plus voucherNumber. Matched by date + voucher number — use get_ledger_vouchers or get_vouchers first to confirm it exists and is unique. Refuses if another voucher type shares the same number on that date (confirmed live: Tally's Alter lookup ignores voucher type and can silently corrupt the wrong one) — resolve the collision in Tally first if that happens.

Inputs: date (required), items (required), partyLedger (required), voucherNumber (required), +14 more.

update_sales_orderA
DestructiveIdempotent

Update an existing Sales Order in TallyPrime, replacing its item lines, party, order number, and narration. Same fields as create_sales_order (orderNumber and each item's dueDate still REQUIRED), plus voucherNumber to locate the existing voucher. Matched by date + voucher number — use get_ledger_vouchers or get_vouchers first to confirm it exists and is unique. Refuses if another voucher type shares the same number on that date (confirmed live: Tally's Alter lookup ignores voucher type and can silently corrupt the wrong one) — resolve the collision in Tally first if that happens. Note voucherNumber here is the existing voucher's own number to match by — Tally may still not let you change it, since Order-class vouchers use 'Auto Retain' numbering (see create_sales_order).

Inputs: date (required), items (required), orderNumber (required), partyLedger (required), +2 more.

update_sales_quotationA
DestructiveIdempotent

Update an existing Sales Quotation in TallyPrime, replacing its item lines, party, order number, and narration. Same fields as create_sales_quotation, plus voucherNumber. Same matching/collision caveats as update_sales_order.

Inputs: date (required), items (required), orderNumber (required), partyLedger (required), +2 more.

update_stock_itemB
DestructiveIdempotent

Update an existing stock item in TallyPrime — same fields as create_stock_item, all optional except name.

Inputs: name (required), unit, group, hsnCode, +11 more.

update_stock_journalA
DestructiveIdempotent

Update an existing Stock Journal voucher in TallyPrime, replacing its source/destination lines and narration. Same fields as create_stock_journal, plus voucherNumber. Matched by date + voucher number — use get_ledger_vouchers or get_vouchers first to confirm it exists and is unique. Refuses if another voucher type shares the same number on that date (confirmed live: Tally's Alter lookup ignores voucher type and can silently corrupt the wrong one) — resolve the collision in Tally first if that happens.

Inputs: date (required), sources (required), destinations (required), voucherNumber (required), +3 more.

update_voucherA
DestructiveIdempotent

Update an existing voucher in TallyPrime, replacing its ledger entries and narration. The voucher is matched by type + date + voucher number, so that combination must be unique and must exactly match an existing voucher (use get_ledger_vouchers or get_vouchers first to confirm it). Either pass debitLedger/creditLedger/amount for a simple 2-leg voucher, or pass 'entries' for 3+ lines, same as create_voucher. Refuses if another voucher type shares the same number on that date (confirmed live: Tally's Alter lookup ignores voucher type and can silently corrupt the wrong one) — resolve the collision in Tally first if that happens.

Inputs: date (required), voucherType (required), voucherNumber (required), mode, +19 more.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 87 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count1/5

    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.

    Completeness4/5

    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).

    Maintenance

    ActivityActive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • 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
      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
      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
    • 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