MoneyWiz MCP Server · Setup overview
Set up MoneyWiz MCP Server
This page explains the main steps. Exact installation commands, client configuration and current examples are maintained on GitHub.
Installation instructions on GitHub ↗MoneyWiz MCP Server connects a local MoneyWiz database to an MCP-compatible client through a permanently read-only interface. Version 2.1.0 adds questions such as “Which bills are due this week or month?”, with account filters and separate bill and transfer totals per currency. See the v2.1.0 release notes.
What you need
macOS, MoneyWiz or a compatible MoneyWiz SQLite database, Python 3.10 or later, and a client supporting local stdio MCP connections. The repository recommends uv for installing its locked environment.
The setup at a glance
- Install the server. Use the repository’s current installation instructions.
- Connect the right database. Configure an explicit path to the primary MoneyWiz database and follow the examples for your chosen client.
- Verify and reconcile. Check readiness, then compare supported balances, transaction counts and per-currency cashflow with MoneyWiz-produced exports from your own store.
- Ask a bounded question. State the account or deliberate account group, topic, dates and currency. Check result completeness before drawing a conclusion.
Updating to version 2.1.0
Follow the repository’s upgrade instructions, then restart or reconnect your MCP client. If Codex has an explicit list of enabled MoneyWiz tools, add the new due-bills tool as described there.
Understand the boundaries
The server cannot write financial records. Currencies remain explicit, with no implicit conversion or mixed-currency total. Unsupported investment, forex or loan values are not authoritative. This is factual retrieval, not financial advice.
Bill results cover remaining MoneyWiz schedules. Supported monthly and yearly rules can be projected; unsupported recurrence rules mark forecasts and totals as incomplete. Paid or skipped history is not reconstructed, and schedule state does not prove bank settlement.
The server performs no financial-data network calls. Results pass to the connected client, which may send them to its model provider under that client’s policy and settings. Keep configuration, exports and validation results private.
Personal Intelligence can help map source authority and keep evidence visible. It neither installs this server nor replaces reconciliation.