Tally MCP Server
An MCP server that lets Claude read from and write to TallyPrime via its built-in XML/HTTP gateway.
README
<p align="center"> <img src="assets/icon.png" alt="Tally MCP Server" width="180"> </p>
Tally MCP Server
A Model Context Protocol (MCP) server that lets Claude read from and write to TallyPrime via its built-in XML/HTTP gateway.
How it works
Claude Desktop <--stdio--> ┐
├─ this MCP server <--HTTP/XML--> TallyPrime (localhost:9000)
Remote MCP client <--HTTP--> ┘
Locally, Claude Desktop launches this server as a stdio process. Remotely, it can also run as an HTTP server. Either way, tool calls get translated into Tally's XML request format, sent to Tally's HTTP gateway, and returned as cleaned-up JSON. There's also an optional local SQL cache (PGLite) for ad-hoc queries beyond the fixed report tools.
Prerequisites
- Node.js 18+
- TallyPrime installed, running, with a company open
- Tally's HTTP gateway enabled:
F1 (Help) > Settings > Connectivity > Client/Server configurationand set TallyPrime acts as toBothorServer, port9000(default).
Setup
npm install
npm run build
Configure Claude Desktop
Option A — Extension (recommended): package as a .dxt and install
with one click. See docs/EXTENSION_PACKAGING.md.
Option B — manual config: edit your Claude Desktop config file:
- Windows:
%APPDATA%\Claude\claude_desktop_config.json - macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
Add:
{
"mcpServers": {
"tally": {
"command": "node",
"args": ["D:\\Projects\\Tally-MCP-Server\\dist\\index.js"],
"env": {
"TALLY_URL": "http://localhost:9000"
}
}
}
}
Restart Claude Desktop. You should see a hammer/tools icon indicating the
tally server is connected.
Available tools
17 tools total — read (ledgers, stock, groups, voucher types, cost centres,
day book, ledger vouchers, company info, P&L, balance sheet, trial balance,
stock summary, bills receivable/payable), write (create ledger, group,
stock item, voucher), and SQL cache (sync_to_sql, query_sql). Full
reference with args: docs/TOOLS.md.
Dates use DD-MM-YYYY format, matching Tally's convention.
Running remotely (HTTP)
TALLY_MCP_TOKEN=<secret> npm run start:http
Docs
- docs/ARCHITECTURE.md — request flow, file responsibilities
- docs/TALLY_XML_GUIDE.md — how Tally's XML gateway works, gotchas
- docs/TOOLS.md — full tool reference + how to add a new tool
- docs/SQL_CACHE.md — the PGLite SQL cache, schema, examples
- docs/HTTP_DEPLOYMENT.md — running as a remote HTTP server
- docs/EXTENSION_PACKAGING.md — packaging as a
.dxtClaude Desktop Extension
Project structure
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 (.dxt) manifest
Environment variables
| Variable | Default | Purpose |
|---|---|---|
TALLY_URL |
http://localhost:9000 |
Tally's HTTP gateway address |
PORT |
3939 |
Port for npm run start:http |
TALLY_MCP_TOKEN |
(unset) | Bearer token required on the HTTP server's /mcp endpoint if set |
Troubleshooting
- "Could not reach TallyPrime" — Tally isn't running, or the HTTP gateway isn't enabled on port 9000.
- "Tally returned an empty response" — Tally is running but no company is open.
create_ledger/create_voucherfails with errors — check that the parent group / ledger names exactly match what exists in Tally (names are case-sensitive and must match exactly).
Roadmap / not yet supported
- Editing or deleting existing vouchers/ledgers/masters
- Inventory vouchers (Stock Journal, Manufacturing Journal, etc.)
- GST-specific reports (GSTR-1, GSTR-3B)
- Multi-company support (currently always targets whichever company is open)
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。