BudgetBakers Wallet MCP Server
Related Servers
Alternatives to BudgetBakers Wallet MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceRead-only MCP server for accessing Wallet by BudgetBakers financial data, allowing users to query accounts, transactions, categories, budgets, and more via natural language.10MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the BudgetBakers Wallet REST API, enabling management of transactions, accounts, categories, budgets, labels, and more through natural language.24 npmMIT
- AlicenseAqualityDmaintenanceIntegrates Claude with the BudgetBakers Wallet API to access financial data including accounts, transactions, categories, and spending analytics.89 npmMIT
- AlicenseAqualityDmaintenanceEnables reading and writing YNAB budget data, such as listing budgets, accounts, categories, transactions, and creating or updating transactions, through natural language commands.8MIT
- AlicenseNot gradedqualityCmaintenanceEnables natural-language access to personal finance data, including consolidated balances, monthly overviews, transaction search, credit card invoices, recurring bills, budgets, category/tag reports, cash flow forecasts, and Open Finance status, with optional read/write tools.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Actual Budget for personal finance management through natural language, supporting transactions, account balances, budget tracking, spending analysis, and payment searches.483 npm1MIT
TDQS
Scored across 8 tools
Each tool targets a distinct resource or action: accounts, records, categories, labels, API usage, and CRUD operations on records. The names clearly separate listing from mutation, and get_api_usage is unique.
All tool names follow a consistent lower_snake_case verb_noun pattern: list_* for retrieval, create_/update_/delete_records for mutations, and get_api_usage. No mixed conventions or vague verbs.
8 tools is well-scoped for a wallet management server, covering core resources and CRUD for records without excessive bloat. Each tool has a clear purpose.
Records have full CRUD (create, update, delete, list), and accounts/categories/labels have list operations. However, missing single-item getters and CRUD for non-record resources create minor gaps that agents can work around via listing.