Ynab Mcpb MCP Server

Local-first YNAB MCP workflows for reconciliation, receipt splitting, safe bulk cleanup, scheduled transactions, and spending analysis. The ynab mcpb mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 10 defined tools rather than through you.

What it actually does

Paste a receipt → itemized split transaction in seconds

• Receipt itemization — — Paste a receipt, get an itemized split transaction with tax allocation automatically distributed across line items
• Bank reconciliation (beta) — — Import a bank CSV, fuzzy-match against YNAB, detect missing or mismatched transactions, and apply bulk fixes
• 35 YNAB tools — — Full coverage plus scheduled transactions and deterministic period analytics
• Write safety by default — — Preview mode requires a short-lived, single-use confirmation bound to the exact validated request
• Smaller tool profiles — — Choose core, read-only, or full at startup without dynamic registration
• Delta sync — — Fetches only changed data since the last request, keeping things fast

Its toolset

Everything the assistant can do here goes through one of these:

• Category — Tools
• Budgets — list_budgets get_budget get_default_budget set_default_budget
• Accounts — list_accounts get_account create_account
• Transactions — list_transactions get_transaction create_transaction create_transactions update_transaction update_transactions delete_transaction
• Categories — list_categories get_category update_category
• Payees — list_payees get_payee
• Months — list_months get_month
• Reconciliation — reconcile_account
• Analytics — analyze_spending compare_spending_periods
• Utilities — get_user diagnostic_info clear_cache

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

You will need 2 environment variables: YNAB_ACCESS_TOKEN, YNAB_EXPORT_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Ynab Mcpb's toolset — Category, Budgets, Accounts and 7 more — is a fair guide to whether it matches your workflow. It is maintained by dizzlkheinz; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Ynab Mcpb.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the ynab mcpb mcp server does with a few real requests.