Accounting Ledger MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| echoA | |
| create_ledgerB | |
| record_cash_saleA | |
| record_cash_purchaseB | |
| record_client_invoiceA | |
| record_supplier_billA | |
| generate_profit_loss_reportA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: setup, reporting, and four specific transaction types. The echo tool is unrelated but not confusing, as it serves a generic utility function.
Most tools follow a consistent verb_noun pattern with snake_case (create_ledger, generate_profit_loss_report, record_*). The exception is 'echo', which is a simple verb, but this is a minor deviation.
Seven tools is well-scoped for an accounting ledger server: one setup tool, four transaction recording tools, one reporting tool, and one utility. Each tool earns its place.
The server covers setup, transaction recording, and reporting, but lacks fundamental operations like listing or retrieving transactions, editing, or deleting records. This creates a gap where agents cannot inspect or manage recorded data directly.