@modudraft/mcp 0.12.1 → 0.12.3

package/LICENSE

@@ -0,0 +1,67 @@
+Modudraft MCP Server - Proprietary Software License
+
+Copyright (c) 2026 Modudraft. All rights reserved.
+
+This license applies to the @modudraft/mcp package (the "Software"). By installing
+or running the Software you agree to these terms. If you do not agree, do not
+install or use it.
+
+1. Grant of use
+
+   Subject to these terms, Modudraft grants you a limited, non-exclusive,
+   non-transferable, revocable license to install and run the Software, in the
+   form Modudraft distributes it, solely to connect your own AI tools to the
+   Modudraft service under a valid Modudraft account.
+
+2. Restrictions
+
+   Except as expressly permitted in section 1 or by law that cannot be waived,
+   you may not, and may not allow anyone else to:
+
+   (a) copy, modify, translate, or create derivative works of the Software;
+   (b) redistribute, publish, sublicense, sell, rent, lease, host, or otherwise
+       make the Software available to third parties;
+   (c) reverse engineer, decompile, disassemble, deobfuscate, or otherwise
+       attempt to derive the source code or underlying algorithms of the
+       Software;
+   (d) remove or alter any copyright or proprietary notice; or
+   (e) use the Software to circumvent the limits, authentication, or access
+       controls of the Modudraft service, or in violation of the Modudraft
+       Terms of Service.
+
+3. Ownership
+
+   The Software is licensed, not sold. Modudraft and its licensors retain all
+   right, title, and interest in the Software, including all intellectual
+   property rights. No rights are granted other than those expressly stated
+   here. Third-party components included in the Software remain under their own
+   licenses.
+
+4. Your content
+
+   These terms do not give Modudraft any rights in the diagrams and other
+   content you create or access with the Software. Your rights and ours in that
+   content, and your use of the Modudraft service, are governed by the Terms of
+   Service at https://modudraft.com/terms. If these terms and the Terms of
+   Service conflict on the use of the service, the Terms of Service prevail.
+
+5. Termination
+
+   This license ends automatically if you breach it. When it ends you must stop
+   using the Software and delete all copies. Modudraft may also end it on
+   notice, for example if you no longer have a Modudraft account.
+
+6. Disclaimer of warranty
+
+   THE SOFTWARE IS PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTY OF ANY
+   KIND, EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY,
+   FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT.
+
+7. Limitation of liability
+
+   TO THE MAXIMUM EXTENT PERMITTED BY LAW, MODUDRAFT WILL NOT BE LIABLE FOR ANY
+   INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR FOR ANY
+   LOSS OF DATA, PROFITS, OR REVENUE, ARISING OUT OF OR RELATED TO THE SOFTWARE,
+   EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+For licensing questions or to report a security issue: security@modudraft.com

package/README.md

@@ -82,8 +82,8 @@ Copy the key - you'll only see it once.
 ### Architecture nodes & edges
 | Tool | Description |
 |---|---|
-| `add_node` | Add a component (compute, database, queue, gateway, etc.) |
-| `update_node` | Update label, tool, or archetype |
+| `add_node` | Add a component (compute, database, queue, gateway, etc.). `tool` takes a catalog key or a common name and is resolved to the catalog key (see [Tool names](#tool-names)) |
+| `update_node` | Update label, tool, or archetype (a `tool` name is resolved the same way; the archetype is left alone) |
 | `delete_node` | Remove a node and its connections |
 | `add_edge` | Connect two nodes with optional label and protocol |
 | `update_edge` | Update edge label or protocol |
@@ -272,3 +272,18 @@ Agents build a diagram with many small calls, and the layout only makes sense on
 - 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.
+
+## Tool names
+
+A node's `tool` is a catalog key (`better-auth`, `postgresql`, `google-oauth`), and the app shows an initials badge with an "unknown tool" warning for anything else. Agents rarely use the exact key, so `add_node`, `update_node`, `bulk_add_nodes` and `apply_architecture` resolve what they are given:
+
+1. an exact catalog key (any case);
+2. an alias listed on the tool in the catalog (`postgres`, `pg`, `k8s`, `NextAuth`, `entra id`, `sign in with Google`, `GitHub login`);
+3. the key or display label with case, spaces, punctuation and underscores ignored (`Better Auth`, `betterauth`, `better_auth`, `Auth.js`).
+
+- The resolved catalog key is stored. If you did not pass an `archetype`, the tool's own is used, so `tool: "Better Auth"` is an `auth` node, not `compute`. An explicit `archetype` always wins, and `update_node` never changes the archetype.
+- Nothing is guessed: an ambiguous name (a bare `google`, `microsoft` or `apple`) stays unresolved.
+- An unknown tool is kept exactly as typed (custom technologies are fine) and the response carries a `tool_hint` (`tool_hints` for the bulk tools) naming the closest catalog tools. Use `list_tools` to browse valid values.
+- `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.