@awesomate/hosting-mcp 0.48.0 → 0.49.0

package/dist/index.js

@@ -42886,10 +42886,13 @@ server.registerTool(
   "awesomate_crm_apps",
   {
     annotations: annotate("awesomate_crm_apps", MUTATING),
-    description: "The account's own apps (a client portal, a members' app) whose users sign in by email link and then read and change only what each kind's access rules allow them (awesomate_crm_kinds set_access). Pro and above to create or change; reading is every plan. action 'list': each app with its publishable key, allowed origins, sign-up mode and default role. action 'create' {name, allowed_origins, sign_up?, default_role?}: name appears in the sign-in email; allowed_origins are the exact origins the app runs on (https://portal.example.com; http://localhost:5173 for development; capacitor://localhost for the mobile shell), with no path and no wildcard; sign_up 'invite' (default: only people added with awesomate_crm_app_users) or 'open' (anyone who uses the email link gets the default role). action 'update' {app_id, ...any of those, status?}: status 'disabled' signs everyone out of that app. The publishable key (pk_...) is not a secret: it goes in the app's browser code, with @awesomate/sdk. Never put the account's own token (amt_pat_...) in browser code. Confirm origins and sign-up mode with the user: open sign-up lets strangers in under the default role.",
+    description: "The account's own apps (a client portal, a members' app) whose users sign in by email link and then read and change only what each kind's access rules allow them (awesomate_crm_kinds set_access). Pro and above to create or change; reading is every plan. action 'list': each app with its publishable key, allowed origins, sign-up mode and default role. action 'create' {name, allowed_origins, sign_up?, default_role?}: name appears in the sign-in email; allowed_origins are the exact origins the app runs on (https://portal.example.com; http://localhost:5173 for development; capacitor://localhost for the mobile shell), with no path and no wildcard; sign_up 'invite' (default: only people added with awesomate_crm_app_users) or 'open' (anyone who uses the email link gets the default role). action 'update' {app_id, ...any of those, status?}: status 'disabled' signs everyone out of that app and stops its server keys. The publishable key (pk_...) is not a secret: it goes in the app's browser code, with @awesomate/sdk. Never put the account's own token (amt_pat_...) in browser code. Confirm origins and sign-up mode with the user: open sign-up lets strangers in under the default role. SERVER KEYS (ak_...), for the app's own server or an n8n workflow, used with @awesomate/sdk createClient({ token: <key> }) or as a Bearer token on https://hub.awesomate.ai/api/sdk/v1/server: action 'keys' {app_id} lists them (never the secrets); 'create_key' {app_id, name, access: 'read'|'write', kinds?} makes one (kinds leaves it to those kinds, 'contact' to read contacts; leave it out for every kind) and returns the key ONCE: put it straight into the app server's environment (awesomate_app_set_env for an app hosted with us, or the n8n credential) and never into browser code, a repository or a reply to the user; 'revoke_key' {app_id, key_id} stops it at once. A key reads every attribute of an app kind, contacts only as you read them, and writes need Support Plus and above. Prefer the narrowest key: read unless the server writes, and only the kinds it uses.",
     inputSchema: {
-      action: external_exports.enum(["list", "create", "update"]),
-      app_id: external_exports.string().max(48).optional().describe("update: the app"),
+      action: external_exports.enum(["list", "create", "update", "keys", "create_key", "revoke_key"]),
+      app_id: external_exports.string().max(48).optional().describe("update, keys, create_key, revoke_key: the app"),
+      access: external_exports.enum(["read", "write"]).optional().describe("create_key"),
+      kinds: external_exports.array(external_exports.string().max(41)).max(50).optional().describe("create_key: only these kinds (contact to read contacts); leave out for every kind"),
+      key_id: external_exports.string().max(64).optional().describe("revoke_key: from keys"),
       name: external_exports.string().max(80).optional(),
       allowed_origins: external_exports.array(external_exports.string().max(200)).max(10).optional(),
       sign_up: external_exports.enum(["invite", "open"]).optional(),
@@ -42897,10 +42900,21 @@ server.registerTool(
       status: external_exports.enum(["active", "disabled"]).optional().describe("update only")
     }
   },
-  async ({ action, app_id, name, allowed_origins, sign_up, default_role, status }) => {
+  async ({ action, app_id, name, allowed_origins, sign_up, default_role, status, access, kinds, key_id }) => {
     try {
       const cfg = requireConfig();
       if (action === "list") return textResult(await hubGet(cfg, "/api/my-crm/v1/apps"));
+      if (action === "keys" || action === "create_key" || action === "revoke_key") {
+        if (!app_id) return errorResult(new Error(`${action} needs app_id, from list.`));
+        const keys = `/api/my-crm/v1/apps/${encodeURIComponent(app_id)}/keys`;
+        if (action === "keys") return textResult(await hubGet(cfg, keys));
+        if (action === "revoke_key") {
+          if (!key_id) return errorResult(new Error("revoke_key needs key_id, from keys."));
+          return textResult(await hubDelete(cfg, `${keys}/${encodeURIComponent(key_id)}`));
+        }
+        if (!name || !access) return errorResult(new Error("create_key needs a name and access (read or write)."));
+        return textResult(await hubPost(cfg, keys, { name, access, ...kinds ? { kinds } : {} }));
+      }
       const fields = Object.fromEntries(Object.entries({ name, allowed_origins, sign_up, default_role }).filter(([, v]) => v !== void 0));
       if (action === "create") return textResult(await hubPost(cfg, "/api/my-crm/v1/apps", fields));
       if (!app_id) return errorResult(new Error("update needs app_id, from list."));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awesomate/hosting-mcp",
-  "version": "0.48.0",
+  "version": "0.49.0",
   "description": "Awesomate MCP server — lets Claude manage your Awesomate WordPress hosting, plan, limits, n8n automations, and build Node/static apps + databases",
   "license": "UNLICENSED",
   "type": "module",

package/skill/CHANGELOG.json

@@ -1,5 +1,13 @@
 {
   "versions": [
+    {
+      "version": "0.49.0",
+      "highlights": [
+        "Your app's own server, or an n8n workflow, can now read and write your app data with a server key of its own (awesomate_crm_apps, create_key), instead of your account's token",
+        "Keep each key narrow: read only, or only the kinds it needs. Revoking one stops it at once, and switching an app off stops all its keys",
+        "Use a key with the @awesomate/sdk package (createClient with the key as the token) or as a Bearer token from n8n. It never works from a browser"
+      ]
+    },
     {
       "version": "0.48.0",
       "highlights": [