@ateam-ai/mcp 0.4.14 → 0.4.16

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ateam-ai/mcp",
-  "version": "0.4.14",
+  "version": "0.4.16",
   "mcpName": "io.github.ariekogan/ateam-mcp",
   "description": "A-Team MCP Server — build, validate, and deploy multi-agent solutions from any AI environment",
   "type": "module",

package/src/tools.js

@@ -771,11 +771,14 @@ export const tools = [
       "Eliminates ~50% of identical plugin boilerplate (imports, theme/bridge hooks, " +
       "postMessage protocol, default export shape). You then fill in the component body. " +
       "Use kind='iframe' for web-only, 'rn' for mobile-only, 'adaptive' for both. " +
-      "Auto-discovery (Phase 5 of the strip) picks up the new plugin at next deploy " +
-      "without a manifest declaration. " +
-      "The scaffold MERGES into the existing connector (its server.js + other files are preserved) — " +
-      "works on both GitHub-backed and repo-less (locally-deployed) tenants; the merge base is the " +
-      "GitHub repo when connected, otherwise the deployed connector source.",
+      "Also writes ui-dist/<plugin>/manifest.json with the required render block.\n\n" +
+      "⚠️ RENDERING IS NOT AUTOMATIC. At deploy, Phase 5 discovers plugins by calling each connector's " +
+      "ui.listPlugins + ui.getPlugin — a plugin only appears (and renders) if the connector ADVERTISES it there " +
+      "with a render.{mode, iframeUrl?, reactNative?} block. Dropping the scaffold files alone does NOT register it. " +
+      "If the connector generates its plugin list from ui-dist/<plugin>/manifest.json, the emitted manifest is picked up automatically; " +
+      "if the connector has a HARDCODED list (e.g. personal-assistant-ui-mcp: UI_PLUGINS[] + PLUGIN_MANIFESTS{} in server.js), you MUST add this plugin there (copy the render block from the manifest.json). " +
+      "Verify after deploy with ateam_get_solution(solution_id, 'connectors_health') or ateam_get_widget_catalog. Then declare it at solution ui_plugins[] so a skill can open it via sys.focusUiPlugin (see ateam_get_spec topic:'widgets').\n\n" +
+      "The scaffold MERGES into the existing connector (server.js + other files preserved) — works on GitHub-backed AND repo-less tenants; merge base is the GitHub repo when connected, else the deployed connector source.",
     inputSchema: {
       type: "object",
       properties: {
@@ -2017,6 +2020,32 @@ export default {
     });
   }
 
+  // Emit a manifest.json with the render block the platform requires. A plugin
+  // is only DISCOVERABLE + RENDERABLE if it appears in the connector's
+  // ui.listPlugins / ui.getPlugin output WITH a render.{ mode, iframeUrl?,
+  // reactNative? } — dropping the HTML/TSX files alone is NOT enough. This
+  // manifest is the source of truth for that block; connectors whose
+  // ui.listPlugins is generated from ui-dist/<plugin>/manifest.json pick it up
+  // automatically, and for connectors with a HARDCODED plugin list (e.g.
+  // personal-assistant-ui-mcp) copy this render block into their ui.getPlugin.
+  const mode = k === "iframe" ? "iframe" : k === "rn" ? "react-native" : "adaptive";
+  const render = { mode };
+  if (k === "iframe" || k === "adaptive") render.iframeUrl = `/ui/${pluginName}/index.html`;
+  if (k === "rn" || k === "adaptive") render.reactNative = { component: pluginName };
+  const prettyName = pluginName.replace(/-/g, " ").replace(/\b\w/g, (c) => c.toUpperCase());
+  files.push({
+    path: `ui-dist/${pluginName}/manifest.json`,
+    content: JSON.stringify({
+      id: pluginName,
+      name: prettyName,
+      version: "1.0.0",
+      description: `${prettyName} plugin — replace with your real description.`,
+      render,
+      channels: ["command"],
+      capabilities: { commands: [] },
+    }, null, 2) + "\n",
+  });
+
   return files;
 }
 
@@ -3899,8 +3928,9 @@ const handlers = {
         k === "iframe" || k === "adaptive"
           ? `Edit ui-dist/${plugin_name}/index.html — replace the placeholder UI.`
           : null,
-        `Phase 5 auto-discovery will register the plugin at next deploy.`,
-        `Optional: drop a manifest.json next to the source for custom commands/capabilities.`,
+        `A manifest.json (with the required render block) was written to ui-dist/${plugin_name}/manifest.json.`,
+        `⚠️ REQUIRED to render: the plugin must appear in this connector's ui.listPlugins / ui.getPlugin output WITH that render block. Dropping the files alone does NOT register it. If the connector has a HARDCODED plugin list (e.g. personal-assistant-ui-mcp: UI_PLUGINS[] + PLUGIN_MANIFESTS{} in server.js), add this plugin there — copy the render block from the manifest.json. Verify with ateam_get_solution(solution_id, "connectors_health") or ateam_get_widget_catalog after deploy.`,
+        `Then declare it at solution level (ui_plugins[]) so a skill can open it via sys.focusUiPlugin — see ateam_get_spec(topic:"widgets").`,
       ].filter(Boolean),
     };
   },