Skip to main content
Glama
Wallet BudgetBakers MCP

Wallet BudgetBakers MCP

by lapin7771n

Wallet by BudgetBakers — MCP Server

Read-only MCP server for accessing Wallet by BudgetBakers financial data from Claude.

Prerequisites

Related MCP server: BudgetBakers Wallet MCP Server

Setup

1. Set your API token

export WALLET_API_TOKEN=your_token_here

The project includes .mcp.json — Claude Code auto-discovers the server. Just open the project directory:

cd wallet-bb-mcp
claude
# /mcp should show "wallet-bb" connected

3. Claude Desktop / Cowork

  1. Open Claude Desktop → Settings (gear icon) → Developer → Edit Config

  2. This opens claude_desktop_config.json in your editor. Add the mcpServers block:

{
  "mcpServers": {
    "wallet-bb": {
      "command": "/Users/YOUR_USERNAME/.local/bin/uv",
      "args": ["--directory", "/path/to/wallet-bb-mcp", "run", "server.py"],
      "env": {
        "WALLET_API_TOKEN": "your_token_here"
      }
    }
  }
}
  1. Replace the values:

    • command — full path to uv (run which uv in terminal to get it)

    • --directory argument — full path to this project

    • WALLET_API_TOKEN — your actual token (env var interpolation doesn't work here)

  2. Save the file and restart Claude Desktop

  3. You should see an MCP tools indicator (hammer icon) in the chat input area

4. Claude.ai Connector (remote)

The server can be deployed to Google Cloud Run and used as a remote MCP connector:

  1. Go to claude.ai → Profile → Settings → Integrations

  2. Click Add custom integration

  3. Enter the server URL: https://<your-cloud-run-service-url>/mcp

  4. No authentication required — the Wallet API token is stored server-side

Cloud Run Deployment

The server supports both local (stdio) and remote (HTTP) transport. Cloud Run deployment is automated via GitHub Actions.

How it works

  • Push to main triggers .github/workflows/deploy.yml

  • Cloud Build builds the Docker image from Dockerfile

  • Cloud Run deploys the new revision to europe-central2

  • Auth is handled via Workload Identity Federation (keyless)

Manual deployment

gcloud run deploy wallet-bb-mcp \
  --source . \
  --region europe-central2 \
  --project wallet-bb-mcp \
  --allow-unauthenticated \
  --set-env-vars "WALLET_API_TOKEN=your_token" \
  --port 8080

Local HTTP mode

MCP_TRANSPORT=streamable-http WALLET_API_TOKEN=your_token uv run server.py
# Health check: curl http://localhost:8080/health
# MCP endpoint: http://localhost:8080/mcp

Available Tools

Tool

Description

get_accounts

List financial accounts (bank, cash, cards). Start here.

get_records

Get transactions for an account (requires account ID)

get_records_by_id

Get specific records by IDs (max 30)

get_categories

List spending/income categories

get_budgets

List budgets with limits and spent amounts

get_goals

List savings goals with progress

get_labels

List custom labels/tags

get_standing_orders

List recurring payments

get_record_rules

List auto-categorization rules

get_api_usage

Check API usage quota

Filter Syntax

All text fields support filter prefixes:

Prefix

Example

Meaning

eq.

eq.Groceries

Exact match

contains.

contains.bank

Contains (case-sensitive)

contains-i.

contains-i.amazon

Contains (case-insensitive)

Range filters for dates, amounts, and timestamps:

Prefix

Example

Meaning

gte.

gte.2025-01-01

Greater than or equal

lte.

lte.2025-12-31

Less than or equal

Combined

gte.100,lte.500

Between 100 and 500

Rate Limits

  • 500 requests per hour

  • Use get_api_usage() to check remaining quota

  • Server returns structured error with Retry-After on HTTP 429

Available Tools

10 tools
get_accountsA

Get all financial accounts (bank accounts, cash, cards, etc.).

Use this first to discover account IDs — you'll need them for get_records().

Args: ctx: MCP context limit: Items per page (1-100, default 30) offset: Items to skip for pagination account_id: Filter by exact account ID name: Filter by account name (use prefix: eq., contains., contains-i.) account_type: Filter by type (e.g. general, loan, insurance) currency_code: Filter by ISO currency code (e.g. UAH, USD, EUR) bank_account_number: Filter by bank account number created_at: Filter by creation date (e.g. "gte.2025-01-01") updated_at: Filter by last update date (e.g. "gte.2025-01-01")

Inputs: name, limit, offset, account_id, +5 more. Returns: result

get_api_usageB

Get API usage statistics.

Args: ctx: MCP context period: Time period — format is Xdays, Xweeks, or Xmonths (e.g. "30days", "4weeks", "3months")

Inputs: period. Returns: result

get_budgetsA

Get all budgets with their limits, spent amounts, and periods.

Args: ctx: MCP context limit: Items per page (1-100, default 30) offset: Items to skip budget_id: Filter by exact budget ID name: Filter by budget name (use prefix: eq., contains., contains-i.) currency_code: Filter by currency (e.g. UAH, USD) created_at: Filter by creation date (e.g. "gte.2025-01-01") updated_at: Filter by last update date (e.g. "gte.2025-01-01")

Inputs: name, limit, offset, budget_id, +3 more. Returns: result

get_categoriesA

Get spending/income categories.

Categories are organized hierarchically (parent -> children). Use category IDs to filter records by category.

Args: ctx: MCP context limit: Items per page (1-100, default 50) offset: Items to skip category_id: Filter by exact category ID name: Filter by name (use prefix: contains-i.food) created_at: Filter by creation date (e.g. "gte.2025-01-01") updated_at: Filter by last update date (e.g. "gte.2025-01-01")

Inputs: name, limit, offset, created_at, +2 more. Returns: result

get_goalsA

Get all savings goals with current/target amounts and deadlines.

Args: ctx: MCP context limit: Items per page (1-100, default 30) offset: Items to skip goal_id: Filter by exact goal ID name: Filter by goal name (use prefix: eq., contains., contains-i.) note: Filter by note text (use prefix: contains-i.vacation) created_at: Filter by creation date (e.g. "gte.2025-01-01") updated_at: Filter by last update date (e.g. "gte.2025-01-01")

Inputs: name, note, limit, offset, +3 more. Returns: result

get_labelsA

Get custom labels (tags) used to organize records.

Args: ctx: MCP context limit: Items per page (1-100, default 50) offset: Items to skip label_id: Filter by exact label ID name: Filter by label name (use prefix: eq., contains., contains-i.) created_at: Filter by creation date (e.g. "gte.2025-01-01") updated_at: Filter by last update date (e.g. "gte.2025-01-01")

Inputs: name, limit, offset, label_id, +2 more. Returns: result

get_record_rulesA

Get auto-categorization rules for records.

These rules automatically assign categories/labels to matching transactions.

Args: ctx: MCP context limit: Items per page (1-100, default 30) offset: Items to skip rule_id: Filter by exact rule ID name: Filter by rule name (use prefix: eq., contains., contains-i.) created_at: Filter by creation date (e.g. "gte.2025-01-01") updated_at: Filter by last update date (e.g. "gte.2025-01-01")

Inputs: name, limit, offset, rule_id, +2 more. Returns: result

get_recordsA

Get financial records (transactions) for a specific account.

IMPORTANT: account_id is required. Use get_accounts() first to find it. Max date range is 370 days. If no date filter, returns last 3 months.

Date filter examples:

  • "gte.2025-01-01" — from Jan 1, 2025

  • "gte.2025-01-01,lte.2025-01-31" — January 2025

Amount filter examples:

  • "gte.100" — amount >= 100

  • "gte.100,lte.500" — between 100 and 500

Text filter prefixes: eq., contains., contains-i.

Args: ctx: MCP context account_id: Required. Account ID (use get_accounts to find IDs) record_date: Date range filter with prefix (e.g. "gte.2025-01-01") limit: Items per page (1-100, default 30) offset: Items to skip for pagination category_id: Filter by category ID label_id: Filter by label ID note: Filter by note text (use prefix: contains-i.grocery) payee: Filter expenses by payee (use prefix: contains-i.amazon) payer: Filter income by payer amount: Filter by amount (use prefix: gte.100,lte.500) record_type: Filter by type: income or expense. Transfers are not a separate type — they are identified by transferId/transferAccountId fields in the response sort_by: Sort field and direction (e.g. "recordDate,asc" or "amount,desc") created_at: Filter by creation date (e.g. "gte.2025-01-01") updated_at: Filter by last update date (e.g. "gte.2025-01-01")

Inputs: account_id (required), note, limit, payee, +10 more. Returns: result

get_records_by_idA

Get specific records by their IDs (comma-separated, max 30).

Args: ctx: MCP context record_ids: Comma-separated record IDs (e.g. "id1,id2,id3")

Inputs: record_ids (required). Returns: result

get_standing_ordersA

Get recurring/scheduled payments (standing orders).

Shows planned future transactions: bills, subscriptions, salary, etc.

Args: ctx: MCP context limit: Items per page (1-100, default 30) offset: Items to skip standing_order_id: Filter by exact standing order ID name: Filter by name (use prefix: eq., contains., contains-i.) currency_code: Filter by ISO currency code (e.g. UAH, USD, EUR) created_at: Filter by creation date (e.g. "gte.2025-01-01") updated_at: Filter by last update date (e.g. "gte.2025-01-01")

Inputs: name, limit, offset, created_at, +3 more. Returns: result

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct resource (accounts, records, categories, budgets, goals, labels, standing orders, rules, API usage). The only potential overlap is get_records vs get_records_by_id, but the latter explicitly retrieves by IDs, making the distinction clear.

    Naming Consistency5/5

    All tools follow the get_<resource> pattern with consistent snake_case. The sole variation, get_records_by_id, still adheres to the overall convention and is predictable.

    Tool Count5/5

    10 tools is well-scoped for a read-only financial data API, covering all major entities without unnecessary bloat or missing core resources.

    Completeness5/5

    The tool set provides comprehensive read-only coverage of the budgeting domain: accounts, transactions, categories, budgets, goals, labels, standing orders, rules, and API usage. No obvious gaps exist for querying financial data, and filters allow for detailed retrieval.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      A
      quality
      D
      maintenance
      Read-only MCP server for accessing personal finance data from Ogarni.AI, including receipts, categories, summaries, notifications, and more.
      20
      -
    • A
      license
      C
      quality
      D
      maintenance
      Enables querying of BudgetBakers Wallet data including accounts, transactions, categories, and labels through natural language commands.
      8
      34 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Read-only MCP and HTTP proxy server for accessing Monarch Money financial data, enabling transaction analysis, budget tracking, and cashflow insights through natural language.
      6
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for programmatic read-only access to RiseUp cashflow data, allowing AI assistants to retrieve budget information via natural language.
      7
      1,180 npm
      40
      MIT