convez.ai
MCP ServerFinanceiroIntermediário
partymola

Monzo MCP Server

partymola/monzo-mcp

Integração bancária Monzo com OAuth, cache local e análise de gastos

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor MCP que integra a API bancária do Monzo com suporte a OAuth, cache local de transações e análise de gastos. Oferece acesso somente leitura a contas, saldos, potes e histórico de transações através do Claude Code ou qualquer cliente MCP compatível.

Instalação

$npx convez-ai partymola/monzo-mcp

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
6
Forks
5
Acompanhando
1
Saúde
57%
Último commit
há 3 dias
Versão
v0.13.0
Issues abertas
1
Contribuidores
3

Casos de uso

  • Análise de padrões de gastos e categorização automática
  • Consulta de saldo e transações direto do Claude
  • Sincronização de histórico transacional em cache local
  • Relatórios de gastos por categoria e comerciante

Veredito

Implementação robusta de integração bancária com OAuth adequado e cache persistente. Bem estruturado para uso em automação financeira pessoal através do Claude, com segurança adequada ao evitar operações de escrita.

README

A tradução para o português deste README ainda está na fila.

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
  • Spending analysis - category breakdowns, top merchants, month-over-month comparison
  • Transaction search - search by merchant, description, or notes across cached history

Tools

ToolDescriptionData source
monzo_list_accountsList accounts with types and IDsLive API
monzo_get_balanceCurrent balance and spend todayLive API
monzo_list_potsSavings pots and balancesLive API
monzo_syncSync transactions to local cacheLive API -> SQLite
monzo_list_transactionsList/filter cached transactionsLocal cache
monzo_search_transactionsSearch by merchant/description/notesLocal cache
monzo_spendingSpending analysis with category breakdownLocal cache

Prerequisites

  • Python 3.13+
  • 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 .

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

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).

Configuration

All configuration is via environment variables (optional):

VariableDefaultDescription
MONZO_MCP_CONFIG_DIR<package>/config/Directory for OAuth credentials and tokens
MONZO_MCP_DB_PATH<package>/monzo.dbPath to SQLite transaction cache

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). It overrides the usual last-sync resumption and is passed straight to the Monzo API. Reaching back more than ~90 days only works inside the SCA window; outside it, the 90-day fallback applies.

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

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.

Ver o original no GitHub

Bom para

Relacionados