Money Manager MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| baseUrl | Yes | The base URL for the Money Manager API (e.g., http://192.168.1.1:8888). This is the IP address and port displayed when you start the web server in the Money Manager app. | http://192.168.1.1:8888 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| init_get_dataB | Retrieves initial application data including categories, payment types, asset groups, and multi-book configuration. |
| transaction_listC | Lists transactions within a date range. |
| transaction_createC | Creates a new income or expense transaction. |
| transaction_updateC | Updates an existing transaction. |
| transaction_deleteC | Deletes one or more transactions. |
| summary_get_periodB | Retrieves financial summary statistics for a date range. |
| summary_export_excelB | Exports transaction data to Excel file. The server returns an HTML-based Excel format. Use .xls extension for best compatibility (if .xlsx is provided, it will be auto-corrected to .xls with a warning). |
| asset_listB | Retrieves all assets in a hierarchical structure. |
| asset_createC | Creates a new asset/account. |
| asset_updateC | Modifies an existing asset. |
| asset_deleteC | Removes an asset. |
| card_listB | Retrieves all credit cards in a hierarchical structure. |
| card_createC | Creates a new credit card. |
| card_updateC | Modifies an existing credit card. |
| transfer_createC | Transfers money between two assets. |
| transfer_updateA | Modifies an existing transfer. WARNING: The server creates a new transfer with a NEW ID instead of updating in-place. The old ID will no longer exist after update. Use transaction_list to get the new ID if needed. |
| dashboard_get_overviewB | Retrieves dashboard overview with asset trends and portfolio breakdown. |
| dashboard_get_asset_chartC | Retrieves historical chart data for a specific asset. |
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 18 tools
Every tool has a clearly distinct purpose with no ambiguity, as they are organized by resource types (asset, card, dashboard, init, summary, transaction, transfer) and specific actions (create, list, update, delete, get, export). The descriptions further clarify unique functions, such as dashboard_get_asset_chart for chart data versus dashboard_get_overview for overview data, ensuring agents can easily differentiate between tools.
The naming follows a consistent pattern of resource_action or resource_action_additional_detail using snake_case throughout, with minor deviations like init_get_data and summary_export_excel that slightly break the verb_noun convention but remain readable. Overall, the naming is predictable and aids in understanding tool purposes across the set.
With 18 tools, the count is well-scoped for a money management server, covering assets, cards, transactions, transfers, dashboards, summaries, and initialization. Each tool earns its place by providing necessary CRUD operations and additional functionalities like exporting and dashboard views, without being excessive or insufficient for the domain.
The tool surface offers complete CRUD/lifecycle coverage for key resources (assets, cards, transactions, transfers), along with dashboard insights, summary statistics, data export, and initialization. There are no obvious gaps; agents can perform all essential financial management tasks, from creating and updating records to analyzing trends and exporting data, ensuring no dead ends in workflows.