Skip to main content
Glama
MCP YNAB Server

MCP YNAB Server

by klauern

mcp-ynab

A Model Context Protocol server for the YNAB (You Need A Budget) API. Lets MCP clients (Claude Desktop, Claude Code, custom agents) read your budgets, accounts, and transactions, and create or recategorize transactions through structured tools.

Install

The project is managed with uv and Task. All Python commands in this repo go through uv run.

uv sync                  # install dependencies
task install             # install the mcp-ynab CLI into the venv

Related MCP server: ynab-mcp

Configure

Set your YNAB Personal Access Token in the environment (or in a .env file at the repo root):

export YNAB_API_KEY=your-personal-access-token

Get a token at https://app.ynab.com/settings/developer.

Quickstart

1. Set your API key

Code Mode is the default surface — it requires your YNAB API key:

export YNAB_API_KEY="your-key-here"

Or store it in your OS keychain (the server reads it automatically).

2. Use Code Mode

By default the server exposes two tools: search (discover available operations) and execute (run a snippet against the live YNAB API).

Discover tools:

# In the search tool:
return [t for t in spec if "transaction" in t["name"]]

Execute a query:

# In the execute tool:
return await ynab.read.get_budgets()

3. Restore the full tool surface (optional)

To access all ~34 direct YNAB tools, set the escape-hatch preference:

set_preference: code_mode_replace_tools = false

Run the server

mcp-ynab                 # production
task dev                 # dev mode + MCP Inspector in the browser

Tools and resources

By default, the public MCP tool surface is intentionally small:

Tool

Purpose

search

Discover available YNAB operations without live API access

execute

Run a short Python snippet against the live YNAB API

ping

Health check the server

get_preferences

Inspect server preferences

set_preference

Update preferences such as mutation or escape-hatch settings

set_api_key

Store a YNAB API key in the OS keychain

clear_api_key

Remove the stored YNAB API key

set_preferred_budget_id

Cache a preferred budget ID for default-targeted calls

Use search to discover operations:

return [
    {"name": tool["name"], "description": tool["description"]}
    for tool in spec
    if "category" in tool["name"]
]

Then call the operation through execute:

categories = await ynab.read.get_categories()
return [
    {"name": category.name, "balance": category.balance}
    for group in categories
    for category in group.categories[:LIMIT]
]

Mutating operations live under ynab.write.* and require code_mode_mutations_enabled=true:

result = await ynab.write.bulk_categorize(assignments=assignments)
return result

The underlying direct tools still exist in the internal FastMCP registry so Code Mode can dispatch through ynab.read.*, generate stubs, and build the search catalog. They are hidden from the public tool list by default. Set code_mode_replace_tools=false to restore the full direct-tool surface as an escape hatch.

Representative internal direct tools include:

Read-only internal tools

Tool

Purpose

get_budgets

List all budgets in markdown

get_accounts

List accounts in a budget, grouped by type with summary

get_account_balance

Return a single account's current balance in dollars

get_transactions

Recent transactions for an account; optional since_date

get_transactions_needing_attention

Filter for uncategorized / unapproved transactions

get_categories

All categories in a budget grouped by category group

Mutating internal tools

Tool

Purpose

create_transaction

Create a new transaction in YNAB

categorize_transaction

Assign a category to an existing transaction

set_preferred_budget_id

Cache a preferred budget ID for default-targeted tools

cache_categories

Cache a budget's category list locally

For account transfers and credit-card payments, use the destination account's transfer payee ID as payee_id when creating or updating a transaction. The get_payees tool lists transfer payees with their Transfer Account ID. Do not pass a Transfer : ... value as payee_name; YNAB rejects or treats that as a regular payee instead of creating a linked transfer.

Resources

  • ynab://preferences/budget_id — currently preferred budget ID

  • ynab://categories/{budget_id} — cached categories for a budget

  • ynab://code-mode/stubs — generated Python stubs for Code Mode

  • ynab://code-mode/examples — curated Code Mode snippets

Code Mode

Code Mode exposes execute, a Python execution tool for multi-step YNAB workflows. It is enabled by default and controlled through the preferences code_mode_enabled, code_mode_mutations_enabled, and code_mode_replace_tools.

See src/mcp_ynab/code_mode/README.md for usage, wiring instructions, and runner limits.

Development

task fmt                 # ruff format + check --fix
task lint                # ruff check + format --check (no auto-fix)
task typecheck           # mypy
task docstrings          # interrogate (fails under 80%)
task test                # unit tests only (default; integration excluded)
task coverage            # unit tests with coverage report

Integration tests

Integration tests are gated behind pytest.mark.integration and excluded from the default task test run. They make real calls to your YNAB account, so they require YNAB_API_KEY.

YNAB_API_KEY=your-token task test:integration

The default integration suite is read-only. Tests that mutate data (create_transaction, categorize_transaction) require an additional opt-in:

YNAB_API_KEY=your-token YNAB_INTEGRATION_ALLOW_WRITES=1 \
  task test:integration

License

MIT

Available Tools

8 tools
clear_api_keyA
Idempotent

Remove the stored YNAB API key from the OS keychain (env var unaffected).

Inputs: no named parameters. Returns: result

executeA
Destructive

Execute a Python snippet against the gated ynab.read/ynab.write Code Mode API.

Enabled by default. Mutating calls require ``code_mode_mutations_enabled`` preference
and must use ``ynab.write.*``; eval dry-run mode is the explicit exception. The snippet
is treated as the body of an async function:
``await ynab.read.get_budgets()``, ``return`` directly.

Inputs: code (required), timeout.

get_preferencesA
Read-onlyIdempotent

Return the current YNAB MCP preferences as a markdown table.

Reads the in-memory ``ynab_resources.preferences`` (which already reflects
the env > preferences.json > defaults source order). The same content is
available as a resource at ``ynab://preferences`` for clients that prefer
to read it that way.

Inputs: no named parameters. Returns: result

pingA
Read-onlyIdempotent

Verify YNAB API auth by fetching the current user's id.

Useful for confirming that ``YNAB_API_KEY`` is set and valid without
touching budget data.

Inputs: no named parameters. Returns: result

set_api_keyA
Idempotent

Store a YNAB personal access token in the OS keychain.

The token is persisted in the platform keychain (macOS Keychain,
Windows Credential Locker, or Linux Secret Service) under
service=``mcp-ynab`` user=``YNAB_API_KEY``. After this returns, future
requests in this process and future runs will pick the key up via
``_resolve_api_key`` — though the ``YNAB_API_KEY`` env var still wins
if it is set.

Inputs: api_key (required). Returns: result

set_preferenceA
Idempotent

Set a single preference and persist it to preferences.json.

``name`` must be one of the ``Preferences`` model fields:
``default_budget_id``, ``category_cache_ttl_minutes``, or
``confirm_before_post``. Bool values accept any of
``1/0/true/false/yes/no/on/off`` (case-insensitive). The empty string is
the documented way to clear ``default_budget_id`` (stored as ``None``);
on a non-Optional field it surfaces as a coercion error.

Note: changes to ``default_budget_id`` here are equivalent to calling
``set_preferred_budget_id``; both write the same field.

Inputs: name (required), value (required). Returns: result

set_preferred_budget_idA
Idempotent

Set the preferred YNAB budget ID.

Inputs: budget_id (required). Returns: result

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 8 tools

    Disambiguation3/5

    Most tools are distinct, but set_preferred_budget_id and set_preference overlap directly, with the description explicitly noting both write the same default_budget_id field. execute and search are also similar in form, though their targets are clearly differentiated by the descriptions.

    Naming Consistency4/5

    Tool names consistently use lowercase snake_case with imperative verbs like set, get, clear, and ping. Minor inconsistency exists between get_preferences (plural) and set_preference (singular), but the overall pattern is predictable.

    Tool Count5/5

    Eight tools is a well-scoped count for this server. Each tool covers a clear concern: auth, key management, preferences, discovery, and dynamic YNAB API execution.

    Completeness4/5

    The server covers its configuration and auth lifecycle thoroughly, and execute provides broad access to the YNAB Code Mode API while search enables discovery. The main limitation is that direct YNAB operations are not exposed as first-class tools, requiring agents to construct snippets.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      A
      maintenance
      A Model Context Protocol server that enables AI-powered interaction with YNAB (You Need A Budget) data, allowing users to query their budgets through conversational interfaces.
      22
      527 npm
      168
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for interacting with YNAB (You Need A Budget). Provides tools for accessing budget data through MCP-enabled clients like Claude Desktop.
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables interaction with You Need A Budget (YNAB) via their API, allowing users to manage budgets, accounts, categories, and transactions through natural language.
      2
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      An MCP server that provides Large Language Models with access to YNAB (You Need A Budget) budgets, allowing them to fetch budget data including accounts, categories, and category groups.
      32
      6
      -