Monzo MCP

Name: Monzo MCP
Author: partymola

作者：partymola版本 0.13.0i★ –i在你的电脑上运行

注册名称io.github.partymola/monzo-mcp

安装

概览

作者提供的说明（英文原文）

Read-only MCP server for the Monzo banking API: OAuth, local transaction cache, spending analysis.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 会计、财务与税务

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

Docker已安装 Docker

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "monzo": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/partymola/monzo-mcp:v0.13.0"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add monzo -- docker run -i --rm ghcr.io/partymola/monzo-mcp:v0.13.0

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "monzo": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/partymola/monzo-mcp:v0.13.0"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "monzo": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/partymola/monzo-mcp:v0.13.0"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月9日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 partymola 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“会计、财务与税务”中的其他服务器比较i

星标数多于此分类中其他 2957 个服务器的 0%
发布到注册中心的时间比此分类中其他 2957 个服务器的 89% 更新
基础检查结果等于或优于此分类中其他 2957 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Monzo MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.13.0）于3天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。

有什么可以替代它？

同一分类中有：Finance Toolkit, SolidInvoice, Korea Tax Calculator

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Finance Toolkit

500+ transparent financial methods calculated from raw statements, not third-party endpoints.

作者：JerBouma广泛使用↓ 1.6万/周★ 5496前天更新

电脑或云端

安装

SolidInvoice

Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.

作者：SolidInvoice正在增长★ 9819天前更新

在云端运行✓ solidinvoice.co

安装

Korea Tax Calculator

Korean tax calculation and tax-audit judgment MCP: 96 tools with statutory citations.

作者：UpstageAI正在增长↓ 3172/周★ 97今天更新

在你的电脑上运行

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

monzo-mcp

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

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`	`/config/`	Directory for OAuth credentials and tokens
`MONZO_MCP_DB_PATH`	`/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.