@modudraft/mcp 0.5.1 → 0.7.0

package/README.md

@@ -2,7 +2,7 @@
 
 Model Context Protocol (MCP) server for [Modudraft](https://modudraft.com) — the system-design diagramming tool.
 
-Connect your AI assistant (Claude, Cursor, Copilot, etc.) to your Modudraft diagrams and let it build and edit architecture, sequence, DB schema, and API diagrams for you.
+Connect your AI assistant (Claude, Cursor, Copilot, etc.) to your Modudraft diagrams and let it build and edit architecture, sequence, DB schema, API, cloud, network, and data-flow diagrams for you.
 
 ---
 
@@ -127,7 +127,7 @@ Copy the key — you'll only see it once.
 ### Cloud diagram
 | Tool | Description |
 |---|---|
-| `add_cloud_resource` | Add a cloud resource (cluster, VPC, service, etc.) |
+| `add_cloud_resource` | Add a cloud resource (cluster, VPC, service, database, queue, etc.) |
 | `update_cloud_resource` | Rename or change the type of a cloud resource |
 | `delete_cloud_resource` | Remove a cloud resource |
 
@@ -146,6 +146,44 @@ Copy the key — you'll only see it once.
 | `delete_data_flow_stage` | Remove a data flow stage |
 | `reorder_data_flow_stages` | Set the order of all stages in a data flow diagram |
 
+### File import
+| Tool | Description |
+|---|---|
+| `scan_project` | Scan a directory and list all importable files (docker-compose, K8s, Terraform, SQL, Prisma, OpenAPI, etc.) |
+| `read_file` | Read any file from the filesystem |
+| `import_file` | Import a file into a diagram — auto-detects format |
+
+**Supported import formats:**
+- **Architecture:** `docker-compose.yml` → nodes + edges
+- **Cloud:** Kubernetes YAML, Terraform `.tf`, AWS CloudFormation YAML/JSON
+- **DB schema:** SQL DDL, `schema.prisma`, DBML, `schema.rb` (Rails), TypeORM entities, SQLAlchemy models, dbt `schema.yml`
+- **API:** OpenAPI 2.x/3.x, GraphQL SDL, Protocol Buffers `.proto`, Postman collection, Insomnia export v4, AsyncAPI
+- **Context (no diagram change):** `.env` files (sensitive values always redacted), `package.json`, `go.mod`, `requirements.txt`, `Gemfile`, `pom.xml`, `Cargo.toml`
+
+### Export
+| Tool | Description |
+|---|---|
+| `export_mermaid` | Export as Mermaid flowchart or ER diagram (paste into GitHub Markdown) |
+| `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 |
+| `export_k8s_yaml` | Generate Kubernetes YAML manifests from the cloud tab |
+| `export_to_file` | Write any export format directly to a local file |
+
+### Validation & diff
+| Tool | Description |
+|---|---|
+| `validate_diagram` | Check a diagram for issues: dangling edges, orphaned nodes, FK integrity, missing PKs, duplicate routes, etc. |
+| `diff_diagram` | Compare two diagrams and return a structured list of what changed (added/removed/modified) |
+
+### Cross-diagram intelligence
+| Tool | Description |
+|---|---|
+| `find_shared_services` | Find nodes that appear in multiple diagrams — useful for shared infrastructure audits |
+| `suggest_connections` | Detect likely missing edges based on archetype pairs |
+| `suggest_architecture` | Generate a suggested node/edge structure from a text description |
+| `clone_diagram` | Deep-copy a diagram as a starting template |
+
 ### Discovery (static, no API call)
 | Tool | Description |
 |---|---|
@@ -153,10 +191,34 @@ Copy the key — you'll only see it once.
 | `list_tools` | Available tech tools per archetype (postgresql, redis, kafka, etc.) |
 | `list_protocols` | Valid edge protocol values |
 
+### Org context
+| Tool | Description |
+|---|---|
+| `get_org_context` | Get cached org context — existing tools, protocols, naming patterns |
+| `refresh_org_context` | Force a refresh of the org context cache |
+
 ---
 
 ## Example prompts
 
+> "Scan my project at ~/code/myapp and import everything you find into diagram X."
+
+> "Import our docker-compose.yml and create an architecture diagram."
+
+> "Import schema.prisma and generate the DB schema tab."
+
+> "Export the architecture as a Mermaid diagram and save it to ./docs/architecture.md."
+
+> "Generate Terraform stubs for everything in the cloud tab and save to ./infra/main.tf."
+
+> "Validate diagram X — are there any issues with the schema or missing connections?"
+
+> "Compare diagram A and diagram B — what changed between the two designs?"
+
+> "What services appear in more than one of our diagrams?"
+
+> "Suggest an architecture for a checkout service with Stripe, Postgres, Redis, and an event queue."
+
 > "Create a diagram of a typical e-commerce backend with a React frontend, API gateway, user service, product service, order service, PostgreSQL databases, Redis cache, and Kafka queue. Connect them and layout the diagram."
 
 > "Add the DB schema for the order service — orders, order_items, and payments tables."
@@ -165,17 +227,11 @@ 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
 
-Each tool call requires a `diagram_id`. The server reads the current diagram from the Modudraft API, applies the change in memory, and writes it back. Changes appear instantly in the Modudraft web app.
+Each tool call requires a `diagram_id`. The server reads the current diagram from the Modudraft API, applies the change in memory, and writes it back — with a 150ms debounce batch so rapid sequential edits (add 10 nodes, add edges) result in a single API round trip. Changes appear instantly in the Modudraft web app.
 
 The `get_diagram` response includes a `hints` array listing nodes with empty metadata fields so your AI assistant knows what context to ask you for.
 
@@ -186,6 +242,7 @@ The `get_diagram` response includes a `hints` array listing nodes with empty met
 - API keys are hashed (SHA-256) server-side and never stored in plain text
 - Keys can be revoked at any time from the dashboard
 - All requests use HTTPS
+- `.env` file imports redact all secrets — only topology metadata (host, port, database name, region) is ever extracted; passwords, tokens, and API keys are always replaced with `[REDACTED]`
 
 ---