Skip to content

Propose a feature

avenir-mcp grows from real uses of a budget. If you find yourself doing a task by hand that an agent could do for you, or an answer that could be clearer, propose it. Proposals are handled in the project’s GitHub issues, in public; you need a GitHub account.

Open a feature request
  1. Check it is not already there. Read the roadmap and search the open proposals. If yours exists, add a 👍 and your use case to it rather than a new issue.

  2. Open a feature request. The form asks four things:

    Question Why
    What do you want to do? the task, in your words — not the tool you imagine
    What would you say to the agent? a sentence you would type, and the answer you expect
    What happens today? what the current tools do, and why it is not enough
    Does it change the budget? a write needs a preview, a confirmation and an undo
  3. Follow the discussion. Questions come as comments on the issue; you are notified by GitHub.

A proposal is easier to accept when it:

  • describes a task, not a YNAB endpoint to wrap — see Architecture;
  • works with YNAB’s public API and a personal access token;
  • can be tested on an invented budget, like the rest of avenir-mcp;
  • if it writes, can be previewed, confirmed and undone — see Safety by design.

Proposals that would send your data to another service, or act without your confirmation, are declined.

Status Meaning
open, enhancement received; comments may ask for details
on the roadmap accepted and planned
closed with a pull request shipped: see the changelog
closed, wontfix declined, with the reason

Unofficial project. We are not affiliated, associated, or in any way officially connected with YNAB or any of its subsidiaries or affiliates. YNAB and You Need A Budget are registered trademarks of YNAB. avenir-mcp is provided as is, without warranty, and is not financial advice. Legal notice