Skip to content

Privacy

avenir-mcp is a program you run yourself, not a service. Its publisher runs no server and receives none of your data. This page describes what the program does on your machine with the data it obtains through YNAB’s API.

Who What Under whose policy
You, on your machine avenir-mcp while it runs, and its journal this page
YNAB your plan, as always: avenir-mcp reads it, and changes it when you confirm, with your own token YNAB’s privacy policy
Your model provider the tool results your MCP client sends to its model: accounts, categories, payees, amounts, memos your provider’s; nobody’s with a local model
PyPI the name of the package asked for, and what any web request carries: your IP address and python-httpx as user agent. One request a day at most, none when the update check is off PyPI’s privacy notice, by the Python Software Foundation
The publisher of avenir-mcp nothing —

avenir-mcp passes none of the data it obtains through YNAB’s API to a third party without your knowledge, and sells none of it: the data goes nowhere but where this table says.

When the plans you open with avenir-mcp belong to other people — an accountant working on clients’ plans, for instance — their data travels the same way, and you are the one answerable to them for it.

  • Your YNAB token. Read at start from YNAB_API_KEY, or from the file named by YNAB_API_KEY_FILE. Kept in memory as a secret value, sent only to YNAB’s API over HTTPS, and never logged, printed, returned to the agent or written to disk. It stays where you put it: your MCP client’s configuration, or that file.
  • Your plan’s data: accounts, categories, transactions, payees and memos. Fetched from YNAB when a tool needs it, kept in memory so that the next request asks only for what changed, and returned to your agent as tool results. Never written to disk.
  • The journal. After each change you confirm, one line of identifiers: which transaction moved from which category to which, and what an undo needs; for a budget change or a move, the amount assigned before and after; for a target, the one to restore; for a renamed payee, its name before and after, which its undo needs. Never a transaction’s amount or a memo, and no payee name other than a renamed payee’s. The file is readable by your user account only.
  • Confirmation codes. In memory, single use, valid 10 minutes.
  • Logs. On stderr, identifiers and counts only, warnings and errors by default. Where they end up depends on your MCP client.
  • The update check’s answer. latest-version.json in ~/.cache/avenir-mcp/, or under XDG_CACHE_HOME: the release number PyPI gave, or nothing when the request failed, and the moment of the check. Nothing about you or your plans. The check asks PyPI once a day at most; AVENIR_MCP_NO_UPDATE_CHECK=1 or DO_NOT_TRACK=1 stops it, and a CI run (CI=true or CI=1) never asks.
  • Read-only by default. Tools that change your plan exist only when you set AVENIR_MCP_WRITE=1, and each change is previewed and confirmed before it is sent.
  • The token is a secret value in the code: printed, logged or in an error, it shows as **********.
  • Bank text is data. Payees and memos come from banks and strangers; they are returned as data, never as instructions to the agent.
  • The HTTP transport stays on this machine. It listens on 127.0.0.1 by default, and refuses to allow changes without its own token.
  • The code is checked on every change: static analysis, secret scanning of the whole history, and an audit of the locked dependencies. See Security.
Data Kept
Plan data while avenir-mcp runs; gone when it stops
Confirmation codes usable 10 minutes, and gone when avenir-mcp stops; a code holds a fingerprint of the preview, never its content
Journal until you delete it; avenir-mcp never trims it
The update check’s answer in its file until you delete it; the next check, a day later at the earliest, writes over it
Token where you stored it, until you remove or revoke it
  1. Stop avenir-mcp, or quit your MCP client: the plan data in memory is gone.
  2. Delete the journal: ~/.local/state/avenir-mcp/journal.jsonl, or the path in AVENIR_MCP_JOURNAL or under XDG_STATE_HOME. You lose the undo history, nothing else.
  3. Delete the update check’s answer: ~/.cache/avenir-mcp/latest-version.json, or the same file under XDG_CACHE_HOME. avenir-mcp asks PyPI again at the next start-up, unless you stop the check.
  4. Revoke the token in YNAB’s developer settings, and remove it from your client’s configuration or from its file.
  5. Conversations with your agent are kept by your MCP client and your model provider, not by avenir-mcp: delete them there.

Your data at YNAB stays in your YNAB account, under YNAB’s policy.

avenir-mcp has no telemetry, no account and no server: its publisher receives nothing, and nothing about you or your plans leaves your machine, apart from what goes to YNAB and to your MCP client. The one request it makes elsewhere is the daily update check: PyPI learns only that someone at your address asked for the avenir-mcp page, as it does for any download, and AVENIR_MCP_NO_UPDATE_CHECK=1 stops that request. This documentation site sets no cookies and runs no analytics; its fonts are served by the site itself. Cloudflare Pages, which hosts it, receives visitors’ IP addresses to serve the pages and protect them, under the Cloudflare Privacy Policy. The site’s former addresses on GitHub Pages only redirect to it; GitHub records visitors’ IP addresses for security, under the GitHub Privacy Statement.

A release that changes what avenir-mcp stores or sends changes this page in the same release, and its changelog says so. Questions: GitHub issues; the legal notice names the publisher.

Unofficial project. We are not affiliated, associated, or in any way officially connected with YNAB or any of its subsidiaries or affiliates. The official YNAB website can be found at https://www.ynab.com. The names YNAB and You Need A Budget, as well as related names, tradenames, marks, trademarks, emblems, and images are registered trademarks of YNAB. avenir-mcp is provided as is, without warranty, and is not financial advice. Legal notice · Privacy