Skip to main content
Glama
monzo-mcp

monzo-mcp

monzo-mcp

CI License: GPL v3 Python 3.13+ Glama MCP Server

MCP server for the Monzo banking API. Read-only access to accounts, balances, pots, transactions, and spending analysis - all through Claude Code or any MCP client.

Unlike other Monzo MCP implementations that use raw bearer tokens (which expire in 6 hours), this server handles full OAuth with automatic token refresh.

Features

  • 7 read-only tools - no write operations, no money movement

  • OAuth with auto-refresh - tokens refresh automatically, no manual regeneration

  • Local transaction cache - SQLite database survives Monzo's 90-day SCA window

  • Auto-sync on demand - the cache-reading tools run an incremental sync automatically if the cache wasn't synced today, so you rarely need to call monzo_sync by hand

  • Spending analysis - category breakdowns, top merchants, month-over-month comparison

  • Transaction search - search by merchant, payee (counterparty), description, or notes across cached history

  • Counterparty details - bank transfers (faster payments, p2p, Bacs) are cached with the payee's name, sort code, and account number

Related MCP server: monzo-mcp

Tools

Tool

Description

Data source

monzo_list_accounts

List accounts with types and IDs

Live API

monzo_get_balance

Current balance and spend today

Live API

monzo_list_pots

Savings pots and balances

Live API

monzo_sync

Sync transactions to local cache

Live API -> SQLite

monzo_list_transactions

List/filter cached transactions

Local cache (auto-syncs if stale)

monzo_search_transactions

Search by merchant/payee/description/notes

Local cache (auto-syncs if stale)

monzo_spending

Spending analysis with category breakdown

Local cache (auto-syncs if stale)

Prerequisites

  • Python 3.13+ (tested on 3.13, 3.14 and 3.15, on Linux, macOS and Windows, in CI)

  • uv (recommended) or pip

  • A Monzo account with an OAuth client registered at developers.monzo.com

Installation

git clone https://github.com/partymola/monzo-mcp.git
cd monzo-mcp
uv venv --python 3.13 .venv
uv pip install -e .

This package is not on PyPI - the name belongs to an unrelated project. A container image is published instead; see Docker.

Setup

1. Register a Monzo OAuth client

Go to developers.monzo.com and create an OAuth client:

  • Set the redirect URL to http://localhost:6600/callback

  • Note your Client ID and Client Secret

2. Authenticate

monzo-mcp auth

This opens your browser for Monzo OAuth. After authorizing, approve the login in your Monzo app within 5 minutes for full transaction history access (Monzo's SCA window).

3. Register with Claude Code

claude mcp add -s user monzo -- /path/to/monzo-mcp/.venv/bin/monzo-mcp

On Windows the console script is at .venv\Scripts\monzo-mcp.exe.

4. First sync

In Claude Code, run monzo_sync to populate the local transaction cache. Do this immediately after auth to take advantage of the SCA window (up to 11 months of history).

Docker

Images are published to ghcr.io/partymola/monzo-mcp. Tags carry a v prefix (:vX.Y.Z), and :latest follows the most recent release.

The container needs a volume. Credentials and the transaction cache live under /data; with nothing mounted there, the container still starts and every tool reports that it is not configured, and anything you authorise is lost as soon as the container is replaced.

First register an OAuth client as described in Setup step 1 - auth prompts for the Client ID and secret, and there is no way to supply them later. The redirect URL is http://localhost:6600/callback, the same as a source install.

Authenticate once, into a named volume. Decide before you run this whether you want a bind mount instead - switching afterwards means authorising again:

docker volume create monzo-mcp-data
docker run --rm -it \
  -v monzo-mcp-data:/data \
  -p 127.0.0.1:6600:6600 \
  ghcr.io/partymola/monzo-mcp:latest auth

The published port is needed only for this step, so the OAuth redirect can reach the container. Binding it to 127.0.0.1 keeps the callback listener off your network. No browser opens - the container has none - so copy the URL it prints. Then approve the login in your Monzo app within 5 minutes (see Monzo SCA window).

Then register the server, reusing the same volume:

claude mcp add -s user monzo -- \
  docker run --rm -i -v monzo-mcp-data:/data ghcr.io/partymola/monzo-mcp:latest

-i is required - the server speaks JSON-RPC over stdin and stdout.

Sync straight away. The 11-month backfill closes 5 minutes after you approve in the Monzo app (see Monzo SCA window), and this route is longer than a source install - so call monzo_sync as soon as the server is registered. Miss it and you silently get 90 days instead, with no error.

To keep the files somewhere you can read them, use a bind mount instead of a named volume. The container runs as root and writes credentials owner-only, so without --user they end up root-owned:

mkdir -p ~/monzo-mcp-data/config
docker run --rm -it \
  -v ~/monzo-mcp-data:/data \
  --user $(id -u):$(id -g) \
  -p 127.0.0.1:6600:6600 \
  ghcr.io/partymola/monzo-mcp:latest auth

Pass the same -v and --user to the server command. Create the directory first - --user against a named volume fails, because the volume initialises root-owned from the image.

CLI

monzo-mcp              Start the MCP server (stdio transport)
monzo-mcp auth         Interactive OAuth setup (opens the browser)
monzo-mcp --version    Print the installed package version

Configuration

All configuration is via environment variables (optional):

Variable

Default

Description

MONZO_MCP_CONFIG_DIR

<package>/config/

Directory for OAuth credentials and tokens

MONZO_MCP_DB_PATH

<package>/monzo.db

Path to SQLite transaction cache

MONZO_MCP_CALLBACK_HOST

localhost

Interface the auth callback server binds to. The redirect URI is unaffected

The container image sets the first two under /data, because the package-relative defaults resolve into the interpreter's lib directory there, which cannot be mounted. It sets the third to 0.0.0.0, because a published port arrives on the container's bridge interface and a localhost bind refuses it.

Credential files (created by monzo-mcp auth):

  • config/monzo_client.json - OAuth client ID and secret

  • config/monzo_tokens.json - Access and refresh tokens (auto-refreshed)

Monzo SCA window

Monzo's Strong Customer Authentication (SCA) limits transaction history access:

  • Within 5 minutes of app approval: up to ~11 months of history

  • After the window expires: only the last 90 days

The local SQLite cache preserves all synced transactions permanently, so run monzo_sync promptly after monzo-mcp auth.

To backfill a specific range, pass since to monzo_sync - an ISO date (2026-01-01) or datetime (2026-01-01T14:30:00Z). Within the last 90 days this works at any time. Reaching further back only works inside the SCA window; outside it the request is refused, and the sync quietly fetches only what is newer than the newest cached transaction.

Older cached transactions gain fields added in newer versions (e.g. counterparty/payee details on bank transfers) only when re-fetched, which a post-auth full sync does for the history it re-pulls.

Security

  • Zero write tools - cannot send money, move funds between pots, or modify transactions

  • Monzo API itself cannot send money to external accounts

  • Tokens stored as JSON files in the config/ directory (gitignored)

  • All API calls are GET requests with Bearer token auth

Troubleshooting

  • "SCA required" or only 90 days of history - re-run monzo-mcp auth and approve the login in the Monzo app within 5 minutes, then sync straight away (see the SCA window above).

  • Token expired / no refresh - re-run monzo-mcp auth to re-authorise.

  • "No transaction data available" - the cache is empty, and the rest of the message says why. If it says the last sync failed, run monzo_sync to see the error. Run monzo-mcp auth only if it says the stored credentials were refused or cannot be used, or that the login needs approving in the Monzo app, and then call monzo_sync once.

  • Every tool reports "not configured" under Docker, or authentication does not survive a restart - nothing is mounted at /data. See Docker; the same volume must be passed to the auth run and to the server.

  • auth sits on "Waiting for callback..." after you approve - the callback was not delivered. Press Ctrl-C and run it again. Under Docker, check the port is published (-p 127.0.0.1:6600:6600).

Contributing

See CONTRIBUTING.md for development setup, the test workflow, and the pre-commit hook. Changes are tracked in CHANGELOG.md.

License

GPL-3.0-or-later. See LICENSE.

Available Tools

7 tools
monzo_get_balanceA

Get current balance for a Monzo account.

Args: account_type: "personal" or "joint" (default: "personal")

Returns balance, spend today, and currency. Also records a balance snapshot.

Inputs: account_type.

monzo_list_accountsA

List all Monzo accounts with their types and IDs.

Returns account details including whether each is personal or joint, and whether it is open or closed. Any other kind of account keeps Monzo's own type name (e.g. "uk_rewards") and is not synced.

Inputs: no named parameters.

monzo_list_potsA

List all pots (savings buckets) for a Monzo account.

Args: account_type: "personal" or "joint" (default: "personal")

Returns the account the pots belong to, plus pot names and balances. Also records balance snapshots.

Inputs: account_type.

monzo_list_transactionsA

List transactions from the local cache.

Auto-syncs if the cache is stale (last sync before today).

Queries the synced transaction database, not the live API. Bank transfers (faster payments, p2p, bacs) include a counterparty object with the payee name and, where the scheme provides them, sort code and account number.

Returns {"account_type": ..., "transactions": [...]}, where account_type echoes the filter applied and is null when unfiltered.

Args: account_type: "personal" or "joint" (default: all) since: Start date, e.g. "2026-01-01" (inclusive) before: End date, e.g. "2026-02-01" (exclusive) category: Exact category match, e.g. "groceries", "eating_out", "transport" merchant: Merchant name search (case-insensitive, partial match) limit: Max results (default 50)

Inputs: limit, since, before, category, +2 more.

monzo_search_transactionsA

Search cached transactions by merchant, counterparty (payee), description, or notes.

Auto-syncs if the cache is stale (last sync before today).

Case-insensitive partial match across merchant_name, counterparty_name, description, and notes fields. Counterparty matching finds bank transfers (faster payments, p2p, bacs) by payee name.

Returns {"account_type": ..., "transactions": [...]}, where account_type echoes the filter applied and is null when unfiltered.

Args: query: Search term account_type: "personal" or "joint" (default: all) since: Start date, e.g. "2026-01-01" (inclusive) before: End date, e.g. "2026-02-01" (exclusive) limit: Max results (default 30)

Inputs: query (required), limit, since, before, +1 more.

monzo_spendingA

Analyse spending from cached Monzo transactions.

Auto-syncs if the cache is stale (last sync before today).

Every result carries account_type, echoing the filter applied and null when unfiltered, so a zero total says which account it measured.

Args: month: Month in YYYY-MM format (default: current month) category: Filter by category, e.g. "groceries", "eating_out", "transport" account_type: "personal" or "joint" (default: all) detail: If true, return individual transactions instead of category summary

Inputs: month, detail, category, account_type.

monzo_syncA

Sync transactions, balances, and pots from the Monzo API into the local cache.

Fetches up to 11 months of history (within SCA window) or falls back to the last-synced timestamp / 90 days. Handles pagination and auth-hold deduplication automatically. Declined card attempts are not stored. Only current and joint accounts are synced; any other is listed as skipped.

Args: account_type: "personal", "joint", or None to sync both since: Optional ISO date ("2026-01-01") or datetime ("2026-01-01T14:30:00Z") to start the backfill from, overriding last-sync resumption. Reaching beyond ~90 days only works inside the post-auth SCA window.

Inputs: since, account_type.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools target clearly distinct resources/actions (accounts, balance, pots, sync, spending analysis). The main overlap is between monzo_list_transactions and monzo_search_transactions, since list_transactions also accepts a merchant filter, but the search tool's broader field coverage (counterparty, description, notes) and different default limit provide some separation.

    Naming Consistency4/5

    All names use a consistent monzo_ prefix and snake_case. Most follow verb_noun (list_accounts, get_balance, list_pots, list_transactions, search_transactions), with minor deviations for the bare verbs/nouns monzo_sync and monzo_spending.

    Tool Count5/5

    Seven tools is well-scoped for a read-only personal banking integration. Each tool covers a distinct area (accounts, balance, pots, sync, transaction listing, search, spending analysis) without obvious redundancy.

    Completeness4/5

    The surface covers the core read-only lifecycle: account discovery, balances, pots, transaction retrieval/search, sync, and spending analysis. Minor gaps remain, such as fetching a single transaction's full detail or editing transaction notes/tags, but agents can work around these using the listing and search tools.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides an MCP server for querying and managing Monarch Money personal finance data through a local SQLite mirror with read-only SQL access. It enables users to sync transaction history from the Monarch API and analyze accounts, categories, and tags.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Read-only Monzo banking integration for Claude Code that allows querying balances, transactions, pots, and spending analysis through natural conversation.
      55 PyPI
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables local read-only exploration of Quicken Simplifi financial data through MCP, with tools for searching transactions, categories, tags, and merchants, using a local SQLite cache and token-based authentication.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only access to Monarch Money financial data, including accounts, transactions, cash flow, spending, and income, via MCP, with secure local credential storage.
      1
      MIT