@modudraft/mcp 0.11.0 → 0.12.1

package/README.md

@@ -62,6 +62,7 @@ Copy the key - you'll only see it once.
 |---|---|---|
 | `MODUDRAFT_API_KEY` | Yes | Your `mdft_…` API key |
 | `MODUDRAFT_API_URL` | No | Override API base URL (default: `https://api.modudraft.com`) |
+| `MODUDRAFT_AUTO_TIDY_MS` | No | Quiet period, in milliseconds, before the architecture tab is auto-tidied after nodes or edges are added or removed (default `8000`; `0` turns auto-tidy off). See [Auto-tidy](#auto-tidy) |
 
 ---
 
@@ -75,7 +76,7 @@ Copy the key - you'll only see it once.
 | `get_diagram` | Get full diagram state + missing-metadata hints |
 | `delete_diagram` | Move diagram to Bin |
 | `clear_diagram` | Remove all content from a diagram |
-| `layout_diagram` | Auto-arrange nodes (dagre, supports LR/TB/RL/BT) |
+| `layout_diagram` | Auto-arrange the architecture tab now, with the same layout as the editor's Tidy button (LR/TB/RL/BT); boundaries are refitted around their nodes |
 | `get_share_link` | Get or create a share link |
 
 ### Architecture nodes & edges
@@ -102,6 +103,9 @@ Copy the key - you'll only see it once.
 |---|---|
 | `add_sequence_message` | Add a message between two nodes (pass a node id or exact node label; resolved to the node id, which is what the Sequence tab draws) |
 | `bulk_add_sequence_messages` | Add many messages (and optional fragments) in one call; participants resolve to node ids like `add_sequence_message` |
+| `get_sequence` | Read just the sequence: messages (ids, node labels, whether the tab draws them) and fragments; far smaller than `get_diagram` |
+| `update_sequence_message` | Edit one message in place (sender, receiver, label, type) and/or move it to a new position |
+| `delete_sequence_message` | Delete one message and renumber the rest; fragments that included it are trimmed (or removed if left empty) |
 | `add_sequence_participant` | Register a named participant |
 | `clear_sequence` | Remove all sequence messages |
 | `auto_sequence` | Derive sequence messages from the architecture edges |
@@ -120,11 +124,19 @@ Copy the key - you'll only see it once.
 ### API schema (OpenAPI)
 | Tool | Description |
 |---|---|
-| `add_api_endpoint` | Add a REST/GraphQL/gRPC endpoint |
-| `update_api_endpoint` | Update endpoint details |
+| `add_api_endpoint` | Add a REST/GraphQL/gRPC endpoint (responses can carry an example `body` and `body_format`) |
+| `update_api_endpoint` | Update endpoint details; `responses` replaces the whole response list, bodies included |
 | `delete_api_endpoint` | Remove an endpoint |
 | `export_openapi` | Export schema as OpenAPI 3.0 JSON |
 
+### Notes
+| Tool | Description |
+|---|---|
+| `get_notes` | Return the diagram's Markdown notes |
+| `set_notes` | Replace the notes |
+| `append_to_notes` | Add content to the end of the notes |
+| `replace_in_notes` | Literal find-and-replace inside the notes (must match exactly once unless `replace_all`), so one checkbox or sentence can change without resending everything |
+
 ### Cloud diagram
 | Tool | Description |
 |---|---|
@@ -250,3 +262,13 @@ The `get_diagram` response includes a `hints` array listing nodes with empty met
 ## License
 
 MIT © [Modudraft](https://modudraft.com)
+
+## Auto-tidy
+
+Agents build a diagram with many small calls, and the layout only makes sense once the nodes *and* the edges between them exist. So adding or removing a node or an edge (`add_node`, `add_edge`, `delete_node`, `delete_edge`, `bulk_add_nodes`, `bulk_add_edges`) does not tidy immediately. Each change restarts a per-diagram timer, and the diagram is tidied **once, after the changes stop** - never between the ten adds of a ten-element build. It is the same layout as the editor's Tidy button.
+
+- Editing a property (`update_node`, `update_edge`, metadata) never triggers it, only a change in the number of elements does.
+- `add_node` with an explicit `x`/`y` keeps that position and does not schedule a tidy.
+- Calling `layout_diagram` yourself tidies right away and cancels the pending one.
+- The tidy is best-effort: if the diagram is locked by someone editing, it is skipped, and the next add or remove schedules another.
+- Set `MODUDRAFT_AUTO_TIDY_MS` to change the quiet period, or `0` to turn it off.