@modudraft/mcp 0.12.3 → 0.12.5

package/README.md

@@ -177,6 +177,7 @@ Copy the key - you'll only see it once.
 | Tool | Description |
 |---|---|
 | `export_mermaid` | Export as Mermaid flowchart or ER diagram (paste into GitHub Markdown) |
+| `render_diagram_text` | Draw the architecture, sequence, DB schema (ER), cloud, network or data-flow tab as plain-text line art, the whole tab or a part of it (see [Viewing diagrams as text](#viewing-diagrams-as-text)) |
 | `export_plantuml` | Export as PlantUML component diagram |
 | `export_drawio` | Export as draw.io / diagrams.net XML |
 | `export_terraform` | Generate Terraform resource stubs from the cloud tab |
@@ -261,7 +262,9 @@ The `get_diagram` response includes a `hints` array listing nodes with empty met
 
 ## License
 
-MIT © [Modudraft](https://modudraft.com)
+Proprietary software. Copyright © 2026 [Modudraft](https://modudraft.com). All rights reserved.
+
+You may install and run this package to connect your own AI tools to the Modudraft service under a valid Modudraft account. Copying, modifying, redistributing, and reverse-engineering it are not permitted. The full terms are in the `LICENSE` file included in this package, and use of the service is governed by the [Terms of Service](https://modudraft.com/terms). Questions: security@modudraft.com.
 
 ## Auto-tidy
 
@@ -287,3 +290,164 @@ A node's `tool` is a catalog key (`better-auth`, `postgresql`, `google-oauth`),
 - `suggest_architecture` also recognises these names when it looks for an auth component in a description, and the nodes it proposes now carry real catalog archetypes (`client`, `gateway`, `auth`, `notification`, `search`, `database`, `cache`, `queue`, `storage`, `observability`, `compute`).
 - Aliases are part of the catalog itself (an `aliases` list on each tool in `@modudraft/core`), so the editor's palette search finds a tool by them too: typing `entra`, `next auth` or `sign in with google` finds Azure AD, Auth.js and Google OAuth.
 - Importing a dependency manifest (`import_file` on `package.json`, `requirements.txt`, `Gemfile`, `go.mod`, `composer.json`, `pom.xml`) now also reports an `auth` list of the authentication libraries it finds, under their catalog names (`Better Auth`, `Auth.js`, `Clerk`, `Keycloak`, `Microsoft OAuth`...), ready to pass straight to `add_node`. Bare `@supabase/supabase-js` and `firebase` are not counted as auth.
+
+## Viewing diagrams as text
+
+`render_diagram_text` draws a tab as plain-text line art, so any agent or terminal can *see* a diagram without a Mermaid or PlantUML renderer. Print the returned `text` inside a code fence. It is read-only.
+
+It draws the **full** tab or a **part** of it. `diagram_type` is `architecture` (default), `sequence`, `er` (the DB schema), `cloud`, `network` or `data_flow`.
+
+| Selector | Applies to | Example | Shows |
+|---|---|---|---|
+| `focus` + `hops` + `direction` | architecture | `focus: "Auth", hops: 2, direction: "out"` | that node and everything within N edges (`out` = downstream, `in` = callers, `both` = default) |
+| `nodes` | architecture | `nodes: ["Auth", "Postgres DB"]` | exactly those nodes and the edges between them |
+| `boundary` | architecture | `boundary: "VPC"` | the nodes inside that boundary |
+| `archetype` | architecture | `archetype: "database"` | only nodes of that archetype |
+| `from_message` / `to_message` | sequence | `from_message: 13, to_message: 15` | messages 13 to 15 (0-based, inclusive) |
+| `participants` | sequence | `participants: ["Web App", "API Server"]` | only messages between them |
+| `focus` + `hops` + `direction` | er | `focus: "orders", hops: 1` | that table and the tables related to it (`out` = the tables it references, `in` = the tables that reference it) |
+| `tables` / `name_prefix` / `schema` | er | `tables: ["users", "orders"]`, `name_prefix: "order"`, `schema: "audit"` | exactly those tables / tables whose name starts with it / tables of one schema |
+| `detail` | er | `detail: "keys"` | `full` (default, every column), `keys` (only PK / FK / unique columns) or `names` (just the table names) |
+| `root` | cloud, network | `root: "main-vpc"` | that resource and everything inside it |
+| `depth` | cloud, network | `depth: 1` | this many levels below the root(s); `0` = only the roots. Boxes with hidden children show `(+N)` |
+| `type` | cloud, network | `type: "ec2"` | resources of that type plus the chain of ancestors above them, marked as context |
+| `config` / `style` | cloud, network | `config: "all"`, `style: "tree"` | how much config to show (`none`, `summary` = first 3 entries, `all`); `nested` boxes, an indented `tree`, or `auto` (nested, falling back to a tree when too wide or deeper than 4 levels) |
+| `flow` / `descriptions` | data_flow | `flow: "Orders pipeline"`, `descriptions: true` | one flow / each stage's description under its name |
+
+Selectors combine (each narrows the view). Nodes, boundaries, participants, tables, resources and flows are given by id or exact name, case-insensitive; an unknown or ambiguous one is an error that lists the choices. A partial view says what it leaves out: a box that still has hidden neighbours shows `(+N)` and they are listed below the diagram, and omitted messages are counted.
+
+Options: `layout` (`LR` or `TB`, architecture and er), `max_width` (default 120; the renderer switches layout, moves edge labels to a numbered legend, or falls back to a tree, to fit), and `charset` (`unicode` or `ascii` for terminals and agents that cannot show box-drawing characters). The result also carries structured `shown`, `hidden` and `warnings`.
+
+`focus: "Auth", hops: 2, direction: "out"`:
+
+```
+                            ┌─────────────────┐
+                          ┌►│ Microsoft OAuth │
+                          │ │    external     │
+                          │ └─────────────────┘
+                          │
+                          │
+┌───────────┐  OAuth 2.0  │   ┌──────────────┐
+│   Auth    │─────────────┘ ┌►│ GitHub OAuth │
+│ auth (+1) │── OAuth 2.0 ──┘ │   external   │
+│           │───────────────┐ └──────────────┘
+└───────────┘   OAuth 2.0   │
+                            │
+                            │ ┌──────────────┐
+                            └►│ Google OAuth │
+                              │   external   │
+                              └──────────────┘
+
+Partial view: 4 of 12 nodes, 3 of 11 edges shown (focus "Auth", 2 hops out).
+Hidden neighbours:
+  Auth: <- API Server
+```
+
+`diagram_type: "sequence", from_message: 13, to_message: 15, participants: ["Web App", "API Server"]`:
+
+```
+ Web App   API
+    │       │
+    │       │        ... 13 earlier messages omitted
+    │       │      ┏ loop: on each edit (autosave)
+    │──────►│      ┃ 13 PATCH /api/diagrams/:id/ops {seq, ops}
+    │◄┄┄┄┄┄┄│      ┃ 15 200 { ok, seq }
+    │       │      ┗
+    │       │        ... 15 later messages omitted
+    │       │        ... 1 message with other participants hidden
+
+Columns: API = API Server
+```
+
+The ER view draws each table as a box of columns (`PK`, `FK`, `UK`; `?` marks a nullable column) and each relation as a line from the table that holds the foreign key, labelled with the column and `N:1`, `1:1` or `N:M`. Relations come from foreign-key columns and from stored relations, merged. Tables with no relations are packed into a grid. `diagram_type: "er", focus: "orders"`:
+
+```
+        ┌─────────────────────────┐
+        │       order_items       │
+        │          (+1)           │
+        │ PK    id  uuid          │
+        │ FK    order_id  uuid    │
+        │ FK,UK product_id  uuid  │
+        │       quantity  integer │
+        └─────────────────────────┘
+                     │
+                     │ order_id N:1
+                    ┌┘
+                    ▼
+     ┌──────────────────────────────┐
+     │            orders            │
+     │ PK id  uuid                  │
+     │ FK user_id  uuid             │
+     │ FK billing_address_id  uuid  │
+     │ FK shipping_address_id  uuid │
+     │    total  numeric(10, 2)     │
+     └──────────────────────────────┘
+      │              │             │
+      │              │ user_id N:1 │
+  [1] │          [2] │          ┌──┘
+ ┌────┘         ┌────┘          ▼
+ ▼              ▼       ┌────────────────┐
+┌────────────────┐      │     users      │
+│   addresses    │      │      (+2)      │
+│ PK id  uuid    │      │ PK id  uuid    │
+│    line1  text │      │ UK email  text │
+│    city  text  │      │    name?  text │
+└────────────────┘      └────────────────┘
+
+Legend:
+  [1] orders -> addresses: billing_address_id N:1
+  [2] orders -> addresses: shipping_address_id N:1
+Partial view: 4 of 10 tables, 4 of 9 relations shown (focus "orders", 1 hop).
+Hidden neighbours:
+  users: <- profiles, <- audit.events
+  order_items: -> products
+```
+
+Cloud and network are containment hierarchies (a VPC contains subnets), not graphs, so they are drawn as boxes nested inside their parent, or as an indented tree. `diagram_type: "cloud", style: "tree", config: "none"`:
+
+```
+prod-account (aws-account)
+· account_id: 123456789012
+· region: eu-west-1
+├── main-vpc (vpc)
+│   · cidr: 10.0.0.0/16
+│   ├── public-a (subnet)
+│   │   · cidr: 10.0.1.0/24
+│   │   · az: eu-west-1a
+│   │   ├── web-alb (load-balancer)
+│   │   │   · scheme: internet-facing
+│   │   ├── web-1 (ec2)
+│   │   │   · instance_type: t3.small
+│   │   │   · ami: ami-0abc
+│   │   │   · key_pair: prod
+│   │   │   · +1 more
+│   │   └── web-2 (ec2)
+│   │       · instance_type: t3.small
+│   └── private-a (subnet)
+│       · cidr: 10.0.2.0/24
+│       └── orders-db (rds)
+│           · engine: postgres
+│           · size: db.t3.medium
+└── assets (s3-bucket)
+```
+
+A data flow is drawn as one lane per flow, sources to transforms to sinks: **all sources feed all transforms, and all transforms feed all sinks** (a column with several stages joins the next through a shared bus). The flow's notes sit on the arrows, or in a numbered legend when they are long. `diagram_type: "data_flow", flow: "Orders pipeline", descriptions: true`:
+
+```
+Flow: Orders pipeline
+Sources                                         Transforms                           Sinks
+┌────────────────────────────────┐              ┌────────────────────────────┐       ┌──────────────────────┐
+│           Orders API           │  raw events  │        Deduplicate         │  [1]  │      Warehouse       │
+│      source · postgresql       │      ┌──────►│     transform · spark      │───┬──►│   sink · snowflake   │
+│ Orders written by the checkout │──────┤       │ Drop repeated events by id │   │   └──────────────────────┘
+│ service                        │      │       └────────────────────────────┘   │
+└────────────────────────────────┘      │                                        │   ┌──────────────────────┐
+                                        │                                        │   │     Search index     │
+┌────────────────────────────────┐      │                                        └──►│ sink · elasticsearch │
+│           Web events           │      │                                            └──────────────────────┘
+│         source · kafka         │──────┘
+└────────────────────────────────┘
+
+Legend:
+  [1] Orders pipeline: transforms -> sinks: cleaned, deduplicated rows ready for analytics and search
+```