@n8n/mcp-apps 0.1.0 → 0.3.0

package/LICENSE_EE.md

@@ -0,0 +1,27 @@
+# The n8n Enterprise License (the “Enterprise License”)
+
+Copyright (c) 2022-present n8n GmbH.
+
+With regard to the n8n Software:
+
+This software and associated documentation files (the "Software") may only be used in production, if
+you (and any entity that you represent) hold a valid n8n Enterprise license corresponding to your
+usage. Subject to the foregoing sentence, you are free to modify this Software and publish patches
+to the Software. You agree that n8n and/or its licensors (as applicable) retain all right, title and
+interest in and to all such modifications and/or patches, and all such modifications and/or patches
+may only be used, copied, modified, displayed, distributed, or otherwise exploited with a valid n8n
+Enterprise license for the corresponding usage. Notwithstanding the foregoing, you may copy and
+modify the Software for development and testing purposes, without requiring a subscription. You
+agree that n8n and/or its licensors (as applicable) retain all right, title and interest in and to
+all such modifications. You are not granted any other rights beyond what is expressly stated herein.
+Subject to the foregoing, it is forbidden to copy, merge, publish, distribute, sublicense, and/or
+sell the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT
+NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES
+OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
+For all third party components incorporated into the n8n Software, those components are licensed
+under the original license provided by the owner of the applicable component.

package/README.md

@@ -18,9 +18,11 @@ helpers used by `packages/cli` to register them as MCP resources and tools.
   the host context the MCP client provides at runtime.
 
 Today the package ships a single app, `workflow-preview`, which is rendered
-after the `create_workflow_from_code` MCP tool returns and gives the user a
-button to open the freshly created workflow in n8n. New apps can be added
-alongside it (see [Adding a new app](#adding-a-new-app)).
+after the `create_workflow_from_code` MCP tool returns. It loads the sanitized
+workflow graph through the existing `get_workflow_details` MCP tool, renders the
+existing n8n demo canvas in an iframe, and keeps a button to open the freshly
+created workflow in n8n. New apps can be added alongside it (see
+[Adding a new app](#adding-a-new-app)).
 
 ## Package layout
 
@@ -33,7 +35,15 @@ src/
       main.ts               # mounts App with i18n
       index.html            # entry HTML (built into dist/apps/<app>.html)
       tokens.scss           # design tokens / global styles
-      url.ts                # defense-in-depth URL validation
+      types.ts              # workflow preview data types
+      type-guards.ts        # workflow preview data guards
+      composables/
+        use-workflow-preview.ts # workflow preview state and host tool handling
+      utils/
+        url.ts              # defense-in-depth URL validation
+  components/               # reusable MCP app Vue components
+    workflow-preview/       # workflow-preview-specific reusable components
+  composables/              # reusable MCP host/runtime composables
   i18n/                     # vue-i18n setup + host locale resolution
   locales/                  # flat-key locale files (en.json, …)
   server/                   # consumed by packages/cli
@@ -42,6 +52,7 @@ src/
     register-mcp-app-tool.ts
     resource-loader.ts      # lazy reads built HTML from dist/apps
     index.ts                # public entry: @n8n/mcp-apps/server
+  utils/                    # framework-agnostic client helpers
 ```
 
 `apps-manifest.ts` is the canonical registry of MCP apps. Both the Vite
@@ -63,14 +74,25 @@ Each app:
   through `onhostcontextchanged` and reflects it on the document.
 - Reads the originating tool's `structuredContent` via `ontoolresult` to
   populate its own state.
+- Calls `app.callServerTool(...)` when it needs fresh n8n data from the MCP
+  server. The workflow preview uses this to call `get_workflow_details` with
+  the created workflow ID.
 - Calls `app.openLink({ url })` to ask the host to navigate — never opens
   links itself.
 
 URL handling is locked down by `isAllowedWorkflowUrl` in
-`src/apps/workflow-preview/url.ts`: only `http(s)://` URLs with a non-empty
+`src/apps/workflow-preview/utils/url.ts`: only `http(s)://` URLs with a non-empty
 host are accepted, both when reading the tool result and right before calling
 `openLink`. This is defense in depth on top of the host's own validation.
 
+The workflow preview iframe uses a server-provided `previewUrl` when available.
+Otherwise it uses the existing n8n preview service because instance routes are
+commonly blocked or unreachable from MCP hosts. The resource metadata declares
+broad `frameDomains` for `http` and `https` so hosts that enforce MCP Apps CSP
+can load instance-specific or configured preview URLs. The framed n8n server's
+own frame policy still applies, so the app falls back to the open-workflow
+button when the preview cannot load.
+
 ## Internationalization
 
 Locale files live under `src/locales/` and use flat, namespaced keys