ZenMoney MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENMONEY_ACCESS_TOKEN | Yes | Access token for ZenMoney API. Required for authentication. | |
| ZENMONEY_API_BASE_URL | No | Base URL for the ZenMoney API. | https://api.zenmoney.ru/v8 |
| ZENMONEY_SYNC_ON_START | No | Whether to sync data on server start. | true |
| ZENMONEY_MAX_RESULT_LIMIT | No | Maximum limit for result lists in MCP responses. | 500 |
| ZENMONEY_REQUEST_TIMEOUT_MS | No | Timeout for API requests in milliseconds. | 30000 |
| ZENMONEY_DEFAULT_RESULT_LIMIT | No | Default limit for result lists in MCP responses. | 100 |
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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sync_runC | Synchronize the in-memory ZenMoney snapshot. |
| sync_statusA | Return memory cache initialization and synchronization status. |
| accounts_listC | List accounts from the in-memory ZenMoney snapshot. |
| transactions_listC | List transactions from the in-memory ZenMoney snapshot. |
| transactions_getB | Get one transaction by id from the in-memory ZenMoney snapshot. |
| transactions_suggestC | Ask ZenMoney to suggest transaction payee, merchant, or tags. |
| tags_listC | List tags/categories from the in-memory ZenMoney snapshot. |
| merchants_listC | List merchants from the in-memory ZenMoney snapshot. |
| budgets_listC | List budgets from the in-memory ZenMoney snapshot. |
| budgets_get_statusB | Calculate read-only spending and remaining amount for a category budget. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| status | ZenMoney memory cache status. |
| schema_account | |
| schema_transaction | |
| schema_tag | |
| schema_merchant | |
| schema_budget | |
| accounts | |
| transactions | |
| tags | |
| merchants | |
| budgets |
TDQS
Scored across 10 tools
Each tool targets a distinct entity or operation: listing for accounts, budgets, merchants, tags, and transactions; plus specific operations like get, suggest, sync, and status. No overlapping purposes.
All tools follow a consistent 'entity_verb' pattern (e.g., accounts_list, sync_run). While the order differs from the typical 'verb_noun', the pattern is uniform across the entire set.
With 10 tools, the server covers core operations for a read-only snapshot viewer: listing all entities, specific retrieval, suggestion, and synchronization management. This is well-scoped.
The tool set provides list operations for all major entities and a get for transactions, but lacks individual get endpoints for accounts, budgets, merchants, and tags. This leaves gaps for detailed inspection.