@modudraft/mcp 0.22.1 → 0.23.0

package/README.md

@@ -86,7 +86,7 @@ Every MCP tool is listed by default. If that is too much context for your client
 | `data_flows` | Data-flow pipelines and stages | `list_data_flows`, `add_data_flow`, `add_data_flow_stage`, `update_data_flow_stage`, `delete_data_flow_stage`, `reorder_data_flow_stages` |
 | `views` | Show and hide tabs, the Notes tab | `get_enabled_tabs`, `enable_tab`, `disable_tab`, `get_notes`, `set_notes`, `append_to_notes`, `replace_in_notes` |
 | `import` | Read and scan the repo, import files, apply env values | `read_file`, `scan_project`, `import_file`, `import_directory`, `apply_env_to_nodes` |
-| `export` | Mermaid, PlantUML, draw.io, Terraform, K8s, write files, generate docs and runbooks | `export_mermaid`, `export_plantuml`, `export_drawio`, `export_terraform`, `export_k8s_yaml`, `export_to_file`, `generate_docs`, `generate_runbook` |
+| `export` | Mermaid, PlantUML, draw.io, Terraform, K8s, Structurizr, write files, generate docs and runbooks | `export_mermaid`, `export_plantuml`, `export_drawio`, `export_terraform`, `export_k8s_yaml`, `export_to_file`, `export_structurizr`, `generate_docs`, `generate_runbook` |
 | `analysis` | Validate, diff, cross-diagram suggestions, clone | `validate_diagram`, `diff_diagram`, `find_shared_services`, `suggest_connections`, `clone_diagram`, `suggest_architecture` |
 | `project` | Watch a repo for drift, sync a diagram with the repo, generate sequences from the API | `watch_project`, `check_project_drift`, `unwatch_project`, `sync_project`, `generate_sequence_from_api` |
 | `history` | Server version history (snapshots) and the edit log | `snapshot_diagram`, `list_snapshots`, `restore_snapshot`, `get_edit_log` |
@@ -96,6 +96,10 @@ 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.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.
+
 ### Upgrading to 0.22.1
 
 - `write_config` now adds the `$schema` line to `modudraft.json`, so editors validate and autocomplete the file.
@@ -310,6 +314,7 @@ The old `request_body`, `request_format`, `body`, `body_format` and top-level `r
 | `export_terraform` | Generate Terraform resource stubs from the cloud tab |
 | `export_k8s_yaml` | Generate Kubernetes YAML manifests from the cloud tab |
 | `export_to_file` | Write any export format directly to a local file (`level` picks the architecture level for mermaid, plantuml and drawio) |
+| `export_structurizr` | Export a diagram as a Structurizr workspace: `format` `dsl` (model, views and styles; no positions) or `json` (adds layouts and the Notes tab). Returns `summary` (what was exported, left out or changed) and the `text`, or writes it to `path` under your project folders (`overwrite: true` replaces an existing file) |
 
 ### Validation & diff
 *(toolset: `analysis`)*
@@ -433,7 +438,7 @@ Items from other files are never touched. Existing items without import history
 - Only the files the workspace uses (`!include`, `!docs` and `!adrs` targets, and the `.json` files beside it, checked for a layout) are read from its folder, up to 50 MB in all; `node_modules` and `.git` are skipped. A Structurizr `workspace.json` may be up to 20 MB; other entry files are limited to 2 MB, and the files a workspace includes count toward the 50 MB total.
 - `watch_project` / `check_project_drift` track the workspace file itself (`workspace.dsl`), not the files it includes. After editing an included file, run `sync_project` (or the CI check), which reads the whole workspace, to see the change.
 
-More on importing a workspace: https://modudraft.com/docs/structurizr
+More on importing a workspace: https://modudraft.com/docs/migrations/structurizr
 
 ## Project drift