Skip to main content
Glama
BudgetBakers MCP Server

BudgetBakers MCP Server

by vmrchnk

BudgetBakers MCP Server

npm version

MCP server for integrating Claude with the BudgetBakers Wallet API. Gives Claude access to financial data: accounts, transactions, categories, and spending analytics.

Quick start

Add to ~/.claude/settings.json (or Claude Desktop config):

{
  "mcpServers": {
    "budgetbakers": {
      "command": "npx",
      "args": ["-y", "budgetbakers-mcp"],
      "env": {
        "BUDGETBAKERS_API_TOKEN": "<your-token>"
      }
    }
  }
}

You can get the API token from BudgetBakers Wallet settings.

Related MCP server: Yodlee MCP Server

Tools

Tool

Description

get_accounts

List all accounts with balances. Filters: currency, accountType

get_categories

Income/expense categories. Filter: name

get_labels

User-defined tags. Filter: name

search_transactions

Search transactions. Requires accountId. Filters: dates, category, payee, amount

get_transaction

Full details of a single transaction by id

spending_by_category

Spending grouped by category for a date range

cashflow_summary

Income, expenses, and net cashflow for a date range

top_merchants

Top merchants by spending for a date range

accountId is required for transactions and analytics tools. Call get_accounts first to get it.

Example prompts

  • "Show my accounts and balances"

  • "How much did I spend in February?"

  • "What do I spend the most money on?"

  • "Top 5 merchants this month"

  • "Find all transactions at Starbucks in January"

Development

git clone https://github.com/vmrchnk/budgetbakers-mcp.git
cd budgetbakers-mcp
npm install
npm run build

To use the local build instead of the npm package:

{
  "mcpServers": {
    "budgetbakers": {
      "command": "node",
      "args": ["/path/to/budgetbakers-mcp/build/index.js"],
      "env": {
        "BUDGETBAKERS_API_TOKEN": "<your-token>"
      }
    }
  }
}

Technical details

  • TypeScript, ES2022, Node16 modules

  • Dependencies: @modelcontextprotocol/sdk, zod

  • Supports agentHints=true — API returns hints about pagination, rate limits, etc.

  • Automatic pagination via hint-provided URLs

  • Analytics tools aggregate data server-side (API has no analytics endpoints)

Available Tools

8 tools
cashflow_summaryB

Calculate income, expenses, and net cashflow for a date range.

Inputs: dateTo (required), dateFrom (required), accountId (required).

get_accountsA

Get all financial accounts with balances. Use this first to get accountId for other tools.

Inputs: currency, accountType, includeArchived.

get_categoriesA

Get income/expense categories. Use to find categoryId for filtering transactions.

Inputs: name.

get_labelsA

Get user-defined labels/tags. Use to find labelId for filtering transactions.

Inputs: name.

get_transactionA

Get full details of a single transaction by ID.

Inputs: id (required).

search_transactionsA

Search transactions with filters. accountId is required — use get_accounts first to find it.

Inputs: accountId (required), limit, payee, dateTo, +4 more.

spending_by_categoryA

Aggregate spending by category for a date range. Shows where money goes.

Inputs: dateTo (required), dateFrom (required), accountId (required).

top_merchantsB

Find merchants/payees with the highest spending in a date range.

Inputs: dateTo (required), dateFrom (required), accountId (required), limit.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 8 tools

    Disambiguation5/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      C
      quality
      D
      maintenance
      Enables querying of BudgetBakers Wallet data including accounts, transactions, categories, and labels through natural language commands.
      8
      38 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude Desktop to Yodlee financial data, enabling account management, transaction queries, spending summaries, and audio narrations.
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Connects Claude to Credit Karma for natural-language access to transactions, spending patterns, and account summaries.
      11
      369 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables users to manage personal expenses, analyze spending patterns, track budgets, generate reports, and export data through natural language conversations with Claude.
      -