@modudraft/mcp 0.23.0 → 0.23.2

package/README.md

@@ -96,6 +96,19 @@ Every MCP tool is listed by default. If that is too much context for your client
 - `load_toolset(name)` adds a group at runtime and sends a tools-changed notification. If your client doesn't refresh tools after `load_toolset`, set `MODUDRAFT_TOOLSETS` instead.
 - Calling any tool by name always works, even when it isn't listed: the server loads its group and runs it.
 
+### Upgrading to 0.23.2
+
+- An expired or revoked API key now fails with a clear message ("Your Modudraft API key expired" or "was revoked") and a link to create a new one at https://app.modudraft.com/account?section=api-keys. A key revoked because your plan ended says so and links to billing instead. The `modudraft-mcp check` CLI shows the same messages. Other authentication errors are unchanged.
+- New keys default to a 1-year expiry (you can still pick 30 days, 90 days or no expiry when you create one); unused keys are revoked after 90 days; a warning email goes out 7 days before an expiry or auto-revoke; revoked keys stay in the key list for 30 days.
+- Creating a key in the web app asks you to sign in again first if your session is older than 15 minutes. This applies to the web app only; the MCP server cannot create keys.
+
+### Upgrading to 0.23.1
+
+- A write refused because a tab is too large (HTTP 413 `tab_too_large`) now shows the server's message, which names the tab and the limit, instead of a generic failure.
+- `import_file` and `import_directory` check the built diagram against the tab size and item limits before writing, and report the problem without saving anything.
+- `snapshot_diagram`, `list_snapshots` and the other version tools say "Version history isn't available on the Free plan. Upgrade to Pro to keep versions." when your plan has no version history.
+- `clone_diagram` asks the server to copy the source diagram's Notes images to the clone. A `.modudraft` file exported from a diagram keeps absolute image URLs, and so do copied image URLs. They work only while the source diagram's Notes or versions still reference the image; after that the daily sweep removes it.
+
 ### Upgrading to 0.23.0
 
 - New tool `export_structurizr` (export toolset) writes a diagram back out as a Structurizr workspace: `format: "dsl"` or `"json"`, with an optional `path` under your project folders and `overwrite`. It returns `{ format, summary, text }`, or `{ format, path, summary }` when it wrote a file. `export_structurizr` can write `.dsl` files; the other file-writing tools cannot. No other tool changed.
@@ -126,7 +139,7 @@ Every MCP tool is listed by default. If that is too much context for your client
 ### Upgrading to 0.19.0
 
 - Snapshots are now server versions. `snapshot_diagram` saves a named version in the diagram's Version history (visible to teammates in the web app), `list_snapshots` lists the versions, and `restore_snapshot` restores one (`snapshot_id` is a version id or a version number). Parameter names are unchanged. The restore is saved as a new version and the state before it stays in the history (the previous version), so it can be undone.
-- Versions are pruned oldest first by plan: 10 per diagram on Free, 50 on Pro, 200 on Team. Pending edits from this MCP are saved before a snapshot or restore.
+- Versions are pruned oldest first by plan: 50 per diagram on Pro, 200 on Team; Free has no version history. Pending edits from this MCP are saved before a snapshot or restore.
 - `delete_snapshot` is removed (versions are pruned automatically by plan); calling it returns an explanatory error.
 - Snapshots saved by older versions in `~/.modudraft/snapshots.v2.json` are still listed (with `source: "local"`) and can be restored, but are read-only: no new local snapshots are written.
 - Requires a Modudraft API with version history.