mcp-for-money-money
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| export_accountsA | Exportiert die Kontenliste aus MoneyMoney als plist. Zeigt die exakten Kontonamen für den account-Parameter von export_transactions. MoneyMoney muss entsperrt sein. |
| export_transactionsA | Exportiert die Umsätze eines Kontos in einem Zeitraum. Das plist enthält bookingDate, amount, name und purpose je Buchung, in Buchungsreihenfolge je Tag. Das ist die Soll-Liste der Abbuchungen für den Rechnungsabgleich. MoneyMoney muss entsperrt sein. |
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 2 tools
The two tools target completely distinct resources and operations: one exports the account list, the other exports transactions for a specific account. Their purposes are clearly separated with no overlap.
Both tools follow the exact same verb_noun pattern: export_accounts and export_transactions. The naming is perfectly consistent and predictable.
With only 2 tools, the server feels thin for what appears to be a specialized MoneyMoney integration, though it may be justified if these are the only needed operations. This is borderline given the narrow domain scope.
The two tools cover the core data export flows (getting account references and exporting transactions), but there are no update/delete/cancel operations. For a read-only export purpose this may be complete, yet the transaction export lacks flexibility (e.g., no filtering by type, no summary/aggregation options).