Skip to content

v0.2.0 — install anywhere, and a place to start

Latest

Choose a tag to compare

@hs737 hs737 released this 28 Aug 14:24
· 2 commits to master since this release

v0.2.0 — install anywhere, and a place to start

The theme is reach and first contact: getting the server installed without
editing JSON, and giving an assistant somewhere to begin once it is.

Installing

  • An MCPB bundle for desktop hosts. The host asks for the token in a form
    and stores it in the OS keychain, so there is no config file to edit and
    no credential left in plain text. A checkbox controls writes.
  • A Claude Code plugin and marketplace: two commands, no JSON.
  • A published container image for linux/amd64 and linux/arm64.
  • Listed in the MCP Registry.

Every manifest that carries a version is generated from pyproject.toml and
checked in CI, so an install surface cannot quietly fetch a previous
release.

Using

  • Six guided prompts, which most clients surface as slash commands:
    monthly review, weekly triage, categorize and approve, subscription
    audit, cash position, and review-and-undo.
  • Three reference resources covering the YNAB method, write safety, and
    which tool to reach for. Fetched on demand, so they cost nothing until
    a client asks.
  • Every tool now carries a readable title and an honest destructive hint,
    for the permission dialogs clients show before a call touches real data.

New tool

  • analysis_recurring_charges answers what subscriptions actually cost per
    year. It groups by YNAB's payee id rather than payee names, so no fuzzy
    matching is involved, and it requires a consistent amount as well as a
    steady cadence — without that second test a weekly grocery run reads as
    a subscription.

Correctness

  • Text YNAB returns HTML-escaped is decoded on the way in, so a payee reads
    as B&H Photo Video. Writes still send exactly what the caller supplied.
  • Write field lengths are checked against YNAB's own limits before the
    request leaves, which matters most in bulk writes where one over-long
    memo otherwise fails the whole batch.
  • Invalid arguments are reported as validation errors naming the field,
    rather than as internal errors.

Verified against the live YNAB API across every read-only tool, and from a
clean install of the wheel, the sdist, and the container image.