BudgetBakers MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BUDGETBAKERS_API_TOKEN | Yes | Your BudgetBakers Wallet API token |
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 |
|---|---|
| get_accountsA | Get all financial accounts with balances. Use this first to get accountId for other tools. |
| get_categoriesA | Get income/expense categories. Use to find categoryId for filtering transactions. |
| get_labelsA | Get user-defined labels/tags. Use to find labelId for filtering transactions. |
| search_transactionsA | Search transactions with filters. accountId is required — use get_accounts first to find it. |
| get_transactionA | Get full details of a single transaction by ID. |
| spending_by_categoryA | Aggregate spending by category for a date range. Shows where money goes. |
| cashflow_summaryB | Calculate income, expenses, and net cashflow for a date range. |
| top_merchantsB | Find merchants/payees with the highest spending in a date range. |
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 8 tools
Each tool targets a distinct resource or function: accounts, categories, labels, individual transactions, filtered search, and three separate analytics aggregations. There is no overlap or ambiguity between tools, even among the analytics which are clearly differentiated by output.
Four tools follow a clear verb_noun pattern (get_accounts, get_categories, get_labels, get_transaction) and search_transactions also fits. However, the three analytics tools (spending_by_category, cashflow_summary, top_merchants) are noun phrases rather than imperative verbs, mixing conventions. Names remain readable and descriptive, but the inconsistency is noticeable.
Eight tools is well-scoped for a financial data query server. The set covers account discovery, reference data, transaction retrieval/search, and analytics without bloat. Each tool earns its place and the count feels appropriate for the domain.
The server provides solid read/analytics coverage: accounts, categories, labels, single transaction, filtered search, and three aggregate views. Minor gaps include lack of a 'list all transactions' endpoint without accountId (search requires it) and no budget/balance history tools, but for a read-centric budget server these are workable limitations.