Limitations and roadmap

Known limitations

Area	Limitation	Workaround
Confirmation codes	kept in memory: a server restart forgets them	ask again for a new preview
Undo	local to the machine whose journal recorded the operation; an undo cannot be undone	redo the change
approve_transactions	applies at once, without preview	it only clears YNAB’s review flag
import_transactions	applies at once, without preview; not undoable here	it only brings in what the bank already has; delete a transaction in YNAB to take it back
update_category, create_category	not undoable; YNAB’s API cannot delete a category	rename back; hide the category in YNAB
HTTP transport	plain HTTP, one shared token, no user accounts	keep it on 127.0.0.1, or use stdio
Public or shared server	not supported: no user accounts, and YNAB’s terms require OAuth for others’ plans	each person runs their own avenir-mcp — see the legal notice
Split transactions	never suggested nor recategorised: their lines carry the categories; split_transaction splits one, but YNAB’s API cannot change or undo a split	change or undo them in YNAB
Suggestions	need a history: a merchant never classified gets none	the agent proposes, you decide
Forecast	extends the last months, plus YNAB’s scheduled transactions; a quarterly or yearly charge without a schedule does not recur by its definition	schedule it in YNAB, or pass it as one_offs
Currency	amounts are shown as numbers, without a currency symbol	—
Python	3.12 to 3.14; 3.15 waits on a dependency (beartype)	—

Roadmap

• From a document to the year’s schedules: the agent reads a tax notice or a call for funds, and avenir-mcp creates or updates the schedules and targets it sets, in one previewed, confirmed and undoable batch.
• A .mcpb bundle for one-click install in Claude Desktop.
• Undo for update_category.
• Lower the Python floor once dependencies allow.
• Run the evaluation through other clients than Claude Code, and with local models.

Missing something? Propose a feature.