Skip to main content
Glama
ZenMoney MCP

ZenMoney MCP

by nonnname

ZenMoney MCP

Read-only MCP server for ZenMoney. It syncs ZenMoney data into process memory and exposes it through MCP tools and resources. It does not persist financial data or API responses to disk.

Agentic Workflows

The read-only mode is a good fit for agentic workflows with tools such as Hermes and OpenClaw. Agents can analyze transactions in the way the user asks, compare spending patterns, prepare recurring personal-finance reports, and surface anomalies without being able to create, update, or delete ZenMoney data.

Related MCP server: mcp-beancount

Unofficial Project

This is an unofficial project and is not affiliated with, endorsed by, or sponsored by ZenMoney. Users are responsible for complying with ZenMoney terms and for protecting their own access tokens.

MCP Client Config

Use the published CLI through npx and pass runtime configuration through your MCP client:

{
  "mcpServers": {
    "zenmoney": {
      "command": "npx",
      "args": ["-y", "@nonnname/zenmoney-mcp"],
      "env": {
        "ZENMONEY_ACCESS_TOKEN": "paste-token-here",
        "ZENMONEY_SYNC_ON_START": "true",
        "ZENMONEY_API_BASE_URL": "https://api.zenmoney.ru/v8",
        "ZENMONEY_DEFAULT_RESULT_LIMIT": "100",
        "ZENMONEY_MAX_RESULT_LIMIT": "500",
        "ZENMONEY_REQUEST_TIMEOUT_MS": "30000",
        "ZENMONEY_ENABLE_WRITE_TOOLS": "false"
      }
    }
  }
}

The same example is available in mcp-config.example.json.

Configuration

ZENMONEY_ACCESS_TOKEN=
ZENMONEY_SYNC_ON_START=true
ZENMONEY_API_BASE_URL=https://api.zenmoney.ru/v8
ZENMONEY_DEFAULT_RESULT_LIMIT=100
ZENMONEY_MAX_RESULT_LIMIT=500
ZENMONEY_REQUEST_TIMEOUT_MS=30000
ZENMONEY_ENABLE_WRITE_TOOLS=false

ZENMONEY_DEFAULT_RESULT_LIMIT and ZENMONEY_MAX_RESULT_LIMIT limit MCP responses from the in-memory snapshot. They do not limit ZenMoney API synchronization.

Local Development

npm install
cp .env.example .env
npm run dev

For a production-like local run from source:

npm run build
npm start

Tools

  • sync_run

  • sync_status

  • accounts_list

  • transactions_list

  • transactions_get

  • transactions_suggest

  • tags_list

  • merchants_list

  • budgets_list

  • budgets_get_status

budgets_get_status calculates read-only category budget status for a month. It reports the configured outcome budget, actual spending, remaining amount, overspend state, and matched category ids. Child categories are included by default with includeChildren: true.

Optional Write Tools

The server is read-only by default. Write tools are not registered unless you explicitly enable them at process startup.

Enable write tools with a launch argument:

{
  "mcpServers": {
    "zenmoney": {
      "command": "npx",
      "args": ["-y", "@nonnname/zenmoney-mcp", "--enable-write-tools"],
      "env": {
        "ZENMONEY_ACCESS_TOKEN": "paste-token-here"
      }
    }
  }
}

Or enable write tools with an environment variable:

{
  "env": {
    "ZENMONEY_ACCESS_TOKEN": "paste-token-here",
    "ZENMONEY_ENABLE_WRITE_TOOLS": "true"
  }
}

Write tools can create, update, and delete ZenMoney user entities except budgets. Update and delete tools require expectedChanged, which is the changed value returned by the read tools. If the entity changes remotely before the write, the server returns a conflict and does not send the mutation.

Budget writes are not supported.

Write tools registered only after opt-in:

  • accounts_create

  • accounts_update

  • accounts_delete

  • transactions_create

  • transactions_create_expense

  • transactions_create_income

  • transactions_create_transfer

  • transactions_update

  • transactions_delete

  • tags_create

  • tags_update

  • tags_delete

  • merchants_create

  • merchants_update

  • merchants_delete

  • reminders_create

  • reminders_update

  • reminders_delete

  • reminder_markers_create

  • reminder_markers_update

  • reminder_markers_delete

Resources

  • zenmoney://status

  • zenmoney://accounts

  • zenmoney://transactions

  • zenmoney://transactions/{id}

  • zenmoney://tags

  • zenmoney://merchants

  • zenmoney://budgets

  • zenmoney://schema/account

  • zenmoney://schema/transaction

  • zenmoney://schema/tag

  • zenmoney://schema/merchant

  • zenmoney://schema/budget

Contributor setup, verification, and maintainer release instructions live in CONTRIBUTING.md.

Available Tools

10 tools
accounts_listZenMoney AccountsC

List accounts from the in-memory ZenMoney snapshot.

Inputs: includeArchived.

budgets_get_statusZenMoney Budget StatusB

Calculate read-only spending and remaining amount for a category budget.

Inputs: month (required), tagId (required), includeChildren, userId.

budgets_listZenMoney BudgetsC

List budgets from the in-memory ZenMoney snapshot.

Inputs: month, tagId, userId.

merchants_listZenMoney MerchantsC

List merchants from the in-memory ZenMoney snapshot.

Inputs: query, limit.

sync_runZenMoney SyncC

Synchronize the in-memory ZenMoney snapshot.

Inputs: full.

sync_statusZenMoney Cache StatusA

Return memory cache initialization and synchronization status.

Inputs: no named parameters.

tags_listZenMoney TagsC

List tags/categories from the in-memory ZenMoney snapshot.

Inputs: includeArchived.

transactions_getZenMoney TransactionB

Get one transaction by id from the in-memory ZenMoney snapshot.

Inputs: id (required).

transactions_listZenMoney TransactionsC

List transactions from the in-memory ZenMoney snapshot.

Inputs: dateFrom, dateTo, accountId, tagId, +4 more.

transactions_suggestZenMoney Suggest TransactionC

Ask ZenMoney to suggest transaction payee, merchant, or tags.

Inputs: payee, merchant, amount, accountId, +1 more.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct entity or operation: listing for accounts, budgets, merchants, tags, and transactions; plus specific operations like get, suggest, sync, and status. No overlapping purposes.

    Naming Consistency5/5

    All tools follow a consistent 'entity_verb' pattern (e.g., accounts_list, sync_run). While the order differs from the typical 'verb_noun', the pattern is uniform across the entire set.

    Tool Count5/5

    With 10 tools, the server covers core operations for a read-only snapshot viewer: listing all entities, specific retrieval, suggestion, and synchronization management. This is well-scoped.

    Completeness3/5

    The tool set provides list operations for all major entities and a get for transactions, but lacks individual get endpoints for accounts, budgets, merchants, and tags. This leaves gaps for detailed inspection.

    Maintenance

    ActivityInactive
    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
    • F
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that gives AI agents structured access to a Beancount personal finance ledger.
      1
      -
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for ZenMoney that enables AI clients to read and manage personal finance data (accounts, categories, transactions, etc.) via natural language.
      17
      86 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server for the Zenmoney personal-finance API that exposes read access to accounts, transactions, categories, budgets, merchants, and reminders, plus the ability to create transactions.
      8
      MIT