For Ynab MCP Server
YNAB budget data analysis and spending insights for your AI assistant.
Data last scanned today · Reviewed today
Overview
The For Ynab MCP Server allows AI clients to interface directly with your YNAB budget data. It exposes the YNAB API as a suite of tools, providing answers to complex questions regarding budget health, recurring charges, and overall spending analysis that the raw API cannot typically address in a single request. The server defaults to a read-only mode to safeguard your financial data. Users who require write capabilities can explicitly enable them by setting an environment variable, which ensures that modifications remain under the user's direct control.
Our verdict
This project holds a high risk level with a security score of 38/100. The score reflects that the server is community-maintained rather than official and has not undergone an editorial security review. While it features a helpful zero-dependency design, users should exercise caution as the authentication and read-only implementation details have not been independently audited. It is best suited for advanced users comfortable with managing their own API token security.
- Operates with zero direct dependencies to minimize supply-chain risk.
- Defaults to read-only mode for safer budget data access.
- Includes documentation for configuration and client setup.
- Licensed under the permissive Apache-2.0 license.
- Carries a high risk rating due to lack of security review.
- Maintained by the community rather than the official YNAB organization.
- Low adoption with only 1 GitHub star.
Tools
| Tool | Description | Risk |
|---|---|---|
| overview_month_health | How is this month's budget doing? | low |
| overview_cash_position | What's my cash position across all accounts? | low |
| triage_uncategorized | Which transactions still need a category? | low |
| triage_unapproved | What's waiting for me to approve? | low |
| analysis_overspent_categories | Which categories are overspent, and by how much? | low |
| analysis_target_funding_gaps | Which targets won't be funded this month? | low |
| analysis_upcoming_scheduled_risks | Are any scheduled transactions at risk? | low |
| bookkeeping_transaction_history | What have I spent at this payee over the last year? | low |
| analysis_recurring_charges | What subscriptions am I actually paying for? | low |
| reconcile_preview | Does this account match the statement, and what's in the way? | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›Are write operations enabled by default?
No, the server is read-only by default. Write tools are not registered unless you explicitly set the environment variable YNAB_ALLOW_WRITES=1.
›Can I perform undo actions if write operations are enabled?
Yes, every write operation records the state that preceded it, allowing you to undo changes if necessary.
›Is it mandatory to specify a budget in every request?
No, while optional, providing a YNAB_PLAN_ID environment variable allows you to interact with your budget without needing to name it in each request.
›How can I avoid storing my YNAB token in a plain text configuration file?
You can download the .mcpb bundle file from the latest release, which prompts for your token and securely stores it in your OS keychain.
›What is the purpose of the 'smoke' command?
The smoke command is used to validate your configuration and ensure all tools are properly registered, printing the total number of registered tools upon success.
Alternatives
Changelog
- Fix
- Improvedv0.3.1 — dependency updates
2026-09-03
- Improved
- New
- Newv0.1.0 — MCP Server for YNAB
2026-08-28
Badge
Maintain this server? Add the live badge to your README.