@modudraft/mcp 0.4.3 → 0.5.0

package/README.md

@@ -104,6 +104,9 @@ Copy the key — you'll only see it once.
 | `add_sequence_participant` | Register a named participant |
 | `clear_sequence` | Remove all sequence messages |
 | `auto_sequence` | Derive sequence messages from the architecture edges |
+| `add_sequence_fragment` | Wrap messages in a loop / alt / opt / par fragment |
+| `update_sequence_fragment` | Change a fragment's kind, condition, or message list |
+| `delete_sequence_fragment` | Remove a fragment |
 
 ### DB schema (ER diagram)
 | Tool | Description |
@@ -121,6 +124,28 @@ Copy the key — you'll only see it once.
 | `delete_api_endpoint` | Remove an endpoint |
 | `export_openapi` | Export schema as OpenAPI 3.0 JSON |
 
+### Cloud diagram
+| Tool | Description |
+|---|---|
+| `add_cloud_resource` | Add a cloud resource (cluster, VPC, service, etc.) |
+| `update_cloud_resource` | Rename or change the type of a cloud resource |
+| `delete_cloud_resource` | Remove a cloud resource |
+
+### Network diagram
+| Tool | Description |
+|---|---|
+| `add_network_device` | Add a network device (router, switch, firewall, etc.) |
+| `update_network_device` | Rename or change the type of a network device |
+| `delete_network_device` | Remove a network device |
+
+### Data flow diagram
+| Tool | Description |
+|---|---|
+| `add_data_flow_stage` | Add a pipeline stage (source, transform, sink, etc.) |
+| `update_data_flow_stage` | Rename or change the type of a data flow stage |
+| `delete_data_flow_stage` | Remove a data flow stage |
+| `reorder_data_flow_stages` | Set the order of all stages in a data flow diagram |
+
 ### Discovery (static, no API call)
 | Tool | Description |
 |---|---|
@@ -140,6 +165,12 @@ Copy the key — you'll only see it once.
 
 > "What metadata is missing from the diagram nodes? Fill in the hosts and ports based on our .env file."
 
+> "Add a data flow diagram showing how events move from our Kafka topics through a Flink transform into the data warehouse."
+
+> "Draw the network topology — edge router, core switch, two firewalls, and the DMZ segment."
+
+> "Wrap the retry loop in the checkout sequence in an alt fragment with condition 'payment fails'."
+
 ---
 
 ## How it works

package/dist/index.js

@@ -25830,14 +25830,53 @@ var ALL_TOOLS = [
       return { ok: true, id: updated.id };
     }
   },
-  // ── Data Flow stages ─────────────────────────────────────────────────────
+  // ── Data Flow flows + stages ──────────────────────────────────────────────
+  {
+    name: "list_data_flows",
+    description: "List all named data flows in the Data Flow tab of a diagram.",
+    inputSchema: {
+      type: "object",
+      properties: {
+        diagram_id: { type: "string" }
+      },
+      required: ["diagram_id"]
+    },
+    async handler(args) {
+      const { data } = await fetchDiagram(diagramId(args));
+      const tab = data.diagrams.find((d) => d.type === "data-flow");
+      return tab?.dataFlows ?? [];
+    }
+  },
+  {
+    name: "add_data_flow",
+    description: "Create a new named data flow in the Data Flow tab. Returns the flow id to use when adding stages.",
+    inputSchema: {
+      type: "object",
+      properties: {
+        diagram_id: { type: "string" },
+        name: { type: "string", description: 'Name for the flow (e.g. "Ingestion pipeline", "ETL")' }
+      },
+      required: ["diagram_id", "name"]
+    },
+    async handler(args) {
+      const id = diagramId(args);
+      let flow;
+      await mutateTypedTab(id, "data-flow", (entry) => {
+        const order = (entry.dataFlows ?? []).length;
+        flow = { id: genId(), name: str(args.name, "Untitled flow"), order };
+        entry.dataFlows = [...entry.dataFlows ?? [], flow];
+      });
+      return flow;
+    }
+  },
   {
     name: "add_data_flow_stage",
-    description: "Add a stage to the Data Flow tab. Stages have a role (source \u2192 transform \u2192 sink) and an optional tool. Stages are ordered by insertion; use reorder_data_flow_stages to rearrange.",
+    description: "Add a stage to a data flow. Stages have a role (source \u2192 transform \u2192 sink) and an optional tool. Pass flow_id to add to a specific flow (use list_data_flows or add_data_flow to get one). Stages are ordered by insertion; use reorder_data_flow_stages to rearrange.",
     inputSchema: {
       type: "object",
       properties: {
         diagram_id: { type: "string" },
+        flow_id: { type: "string", description: "ID of the data flow this stage belongs to (from add_data_flow or list_data_flows)" },
         type: {
           type: "string",
           enum: ["source", "transform", "sink"],
@@ -25852,9 +25891,11 @@ var ALL_TOOLS = [
       const id = diagramId(args);
       let stage;
       await mutateTypedTab(id, "data-flow", (entry) => {
-        const order = (entry.dataFlowStages ?? []).length;
+        const flowId = str(args.flow_id) || void 0;
+        const order = (entry.dataFlowStages ?? []).filter((s) => s.flowId === flowId).length;
         stage = {
           id: genId(),
+          ...flowId ? { flowId } : {},
           type: str(args.type, "source"),
           label: str(args.label),
           tool: str(args.tool),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@modudraft/mcp",
-  "version": "0.4.3",
+  "version": "0.5.0",
   "description": "MCP server for Modudraft — create and edit system-design diagrams via AI (cloud edition)",
   "type": "module",
   "bin": {