Repository navigation
v0.6.0
Highlights
apply_changescan show an interactive card (experimental, off by default: setGRAMPS_MCP_UI=prefab). Clients that render MCP Apps get a card where the user can untick changes (changes that depend on each other are ticked and unticked together), fix a name before applying, and apply or cancel. Apply callsconfirm_changes, a tool the host keeps away from the model. Clients that do not advertise MCP Apps keep the elicitation confirmation.GRAMPS_MCP_UI=prefab-alwaysshows the card to every client; one that cannot render it writes nothing.- The confirmation text is now valid Markdown, so the detail lines of each change no longer run together in VS Code.
Things to know
- The guarantee that the model cannot confirm for the user rests on the host keeping
confirm_changesout of the model's tool list, as the MCP Apps specification asks. Check it in your client. - In card mode,
apply_changeshas no output schema and does not carry Claude Code'srequiresUserInteractionmark. - Labels that name an object do not follow a name being edited until it is applied.
- Details and screenshots: https://jerive.github.io/gramps-mcp/reference/tools/#interactive-card-experimental
What's Changed
- Drop the version from the docs by @jerive in #16
- Show apply_changes as an interactive card: tick, fix a name, apply by @jerive in #17
Full Changelog: v0.5.2...v0.6.0