beanie-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BEANCOUNT_LEDGER | Yes | Absolute path to your Beancount ledger file (.bean). |
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 |
|---|---|
| run_queryA | Query the Beancount ledger using BQL. Returns a dict with: columns — list of column name strings rows — list of rows, each a list of value strings truncated — true if the result was cut at 200 rows total_rows — full result count before any truncation error — present (instead of the above) if the BQL is invalid |
| bean_checkA | Validate the ledger with bean-check. Returns a clean confirmation message if there are no problems, or a newline-separated list of errors with file path and line number. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| beanie://accounts | |
| beanie://tables |
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one validates the ledger for errors, the other executes BQL queries. There is no ambiguity in what each tool does.
Both tools use snake_case, but the naming pattern differs slightly: 'bean_check' is a compound noun or verb-object reversed ('check bean'), while 'run_query' is a clear verb-object. Still, the style is consistent and readable.
Only 2 tools for a ledger management server is too few. Typical accounting workflows require more operations (e.g., insert transactions, list accounts, generate reports), making this set feel incomplete for its domain.
The tool surface is severely incomplete: there is no way to create, update, or delete ledger entries, no account management, and only basic validation and querying. Users cannot perform core accounting tasks.