@modudraft/mcp 0.15.2 → 0.16.0

package/README.md

@@ -71,6 +71,12 @@ Without it, all diagram tools work as usual. The file tools fall back to your cl
 | `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) |
 
 
+### Upgrading to 0.16.0
+
+- `HEAD` and `OPTIONS` are supported HTTP methods for API endpoints and OpenAPI imports (`TRACE` is still skipped with a warning). The Postman and Insomnia importers still keep only GET, POST, PUT, PATCH and DELETE.
+- `add_api_endpoint`, `bulk_add_api_endpoints`, and `add_db_table` reject duplicates, for every protocol: an http endpoint with the same method and path (placeholders are normalized, so `/orders/:id`, `/orders/{id}` and `/orders/{orderId}` are the same path), an endpoint of another protocol with the same protocol and name, and a table with the same schema and name (case-insensitive; no schema means `public`).
+- `export_openapi` hoists `$defs` into `components.schemas` (identical definitions share one component), rewrites `:name` path segments to `{name}`, synthesizes undeclared path parameters, and lists undeclared or unused path parameters and duplicate operations under `x-modudraft-warnings`.
+
 ### Upgrading to 0.14.2
 
 - File tools (`read_file`, `import_file`, `import_directory`, `scan_project`, `export_to_file`, ...) only read and write inside your source-code folder (your repo or git worktree). The server takes it from your MCP client's workspace folders, then `MODUDRAFT_PROJECT_ROOTS`, then the folder the server was started in. Your home directory itself is never accepted, so Claude Desktop users who want the file tools should set the optional `MODUDRAFT_PROJECT_ROOTS` to their repo. Relative paths resolve against the first folder, and a leading `~` is expanded.
@@ -133,7 +139,7 @@ A diagram can hold many named sequences. Each has its own lanes (architecture no
 ### DB schema (ER diagram)
 | Tool | Description |
 |---|---|
-| `add_db_table` | Add a database table with columns |
+| `add_db_table` | Add a database table with columns; rejects duplicate table names (case-insensitive) |
 | `update_db_table` | Replace a table's columns |
 | `delete_db_table` | Remove a table |
 | `export_er_diagram` | Export schema as SQL DDL |
@@ -141,11 +147,11 @@ A diagram can hold many named sequences. Each has its own lanes (architecture no
 ### API schema (OpenAPI)
 | Tool | Description |
 |---|---|
-| `add_api_endpoint` | Add an http, graphql, grpc, websocket or event endpoint. Its request and response shapes go in `contract`: per-protocol slots holding JSON Schema (as an object or YAML), where fields are required unless marked `optional: true`. Omit `contract` to start from an empty one |
-| `bulk_add_api_endpoints` | Add many endpoints in one call, each with its own `contract`; one invalid endpoint rejects the whole batch |
+| `add_api_endpoint` | Add an http (including HEAD and OPTIONS), graphql, grpc, websocket or event endpoint; rejects duplicate endpoints. Its request and response shapes go in `contract`: per-protocol slots holding JSON Schema (as an object or YAML), where fields are required unless marked `optional: true`. Omit `contract` to start from an empty one |
+| `bulk_add_api_endpoints` | Add many endpoints in one call, each with its own `contract`; rejects duplicates within the batch or diagram; one invalid endpoint rejects the whole batch |
 | `update_api_endpoint` | Update endpoint details; `contract` replaces the slots it names and keeps the rest; changing `protocol` converts the contract and lists anything that could not be kept in `dropped` |
 | `delete_api_endpoint` | Remove an endpoint |
-| `export_openapi` | Export the http endpoints as OpenAPI 3.1 (JSON, or YAML with `format: yaml`) |
+| `export_openapi` | Export the http endpoints as OpenAPI 3.1 (JSON, or YAML with `format: yaml`); hoists `$defs` into `components.schemas`, synthesizes undeclared path params, and reports warnings under `x-modudraft-warnings` |
 
 The old `request_body`, `request_format`, `body`, `body_format` and top-level `responses` arguments were removed; they now return an error naming their replacement in `contract`.