@modudraft/mcp 0.12.1 → 0.12.2

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.