@awesomate/hosting-mcp 0.91.1 → 0.92.2

package/dist/index.js

@@ -40082,11 +40082,23 @@ ${JSON.stringify(details, null, 2)}`;
 }
 function keyHolder(ctx) {
   const c = ctx && typeof ctx === "object" ? ctx : {};
-  const email2 = typeof c.email === "string" ? c.email : null;
+  const k = c.key && typeof c.key === "object" ? c.key : {};
+  const email2 = typeof k.email === "string" ? k.email : typeof c.email === "string" ? c.email : null;
+  if (k.holder === "person") {
+    const name = typeof k.name === "string" && k.name ? k.name : email2 ?? "a team member";
+    const level = k.level === "full" ? "full" : "view";
+    return {
+      holder: "person",
+      email: email2,
+      name,
+      level,
+      note: `This key belongs to ${name}${email2 && name !== email2 ? ` (${email2})` : ""}, a team member${level === "view" ? " with view-only access" : ""}: Claude does only what they can do in the hub, never more, and never with a shell on the hosting account. Do not offer anything their access does not include; if they ask, say the account owner can do it.`
+    };
+  }
   return {
     holder: "account_owner",
     email: email2,
-    note: `This key belongs to the account owner${email2 ? ` (${email2})` : ""}: everything Claude does with it is done as the owner. Team members cannot connect Claude Code with their own key yet.`
+    note: `This key belongs to the account owner${email2 ? ` (${email2})` : ""}: everything Claude does with it is done as the owner. Team members connect their own Claude Code, at their own access, once the owner turns it on for them.`
   };
 }
 
@@ -42388,7 +42400,7 @@ server.registerTool(
   "awesomate_get_context",
   {
     annotations: annotate("awesomate_get_context", READ_ONLY),
-    description: "THE session entry point: call it FIRST, before any domain context. Returns the connected account: plan, capabilities, limits, scopes, token expiry, cPanel routing, PLUS `key` (whose key this is: always the account owner's today, so everything done with it is done as the owner; say so if the user is not the owner; team members cannot connect Claude Code with their own key yet; a tool the key's scopes do not cover answers at once with the hub's own refusal), PLUS `attention` ({unreadNotifications, erroringWorkflows7d, patExpiresInDays}: null means unknown, never zero; when something is non-zero, mention it to the user in one line before starting the asked task), `features` ({key: {available, reason, message}}: what this account has; never offer one whose available is false, say its message instead), `latestMcpVersion` (if serverVersion still lags it after a restart, the npx cache is stale; remedy: rm -rf ~/.npm/_npx, then restart), and `skill` ({updateAvailable, staleSkills, whatsNew}: if updateAvailable, mention ONCE with a whatsNew line, offer awesomate_skill_update, never mid-task). If the token is near expiry (patExpiresInDays < 7), re-running Connect Claude Code from hub.awesomate.ai/claude refreshes skills AND renews the token in one go.",
+    description: "THE session entry point: call it FIRST, before any domain context. Returns the connected account: plan, capabilities, limits, scopes, token expiry, cPanel routing, PLUS `key` (whose key this is: the account owner's, so everything is done as the owner, or a team member's own (`holder: 'person'`), which does only what that person can do in the hub and never has a shell: say whose it is, and never offer work outside a person's access; a tool the key's scopes do not cover answers at once with the hub's own refusal), PLUS `attention` ({unreadNotifications, erroringWorkflows7d, patExpiresInDays}: null means unknown, never zero; when something is non-zero, mention it to the user in one line before starting the asked task), `features` ({key: {available, reason, message}}: what this account has; never offer one whose available is false, say its message instead), `latestMcpVersion` (if serverVersion still lags it after a restart, the npx cache is stale; remedy: rm -rf ~/.npm/_npx, then restart), and `skill` ({updateAvailable, staleSkills, whatsNew}: if updateAvailable, mention ONCE with a whatsNew line, offer awesomate_skill_update, never mid-task). If the token is near expiry (patExpiresInDays < 7), re-running Connect Claude Code from hub.awesomate.ai/claude refreshes skills AND renews the token in one go.",
     inputSchema: {}
   },
   async () => {
@@ -43079,7 +43091,7 @@ server.registerTool(
   "awesomate_site_staging_promote",
   {
     annotations: annotate("awesomate_site_staging_promote", DESTRUCTIVE),
-    description: "Publish the staging copy to the LIVE site (overwrites live files + database with staging). The live site is auto-snapshotted first \u2014 the result includes preSnapshotId, which awesomate_rollback_site can restore if anything looks wrong. **Confirm with the user before promoting \u2014 it replaces the live site.** Requires shell access (Support Plus+).",
+    description: "Publish the staging copy to the LIVE site (overwrites live files + database with staging). The live site is auto-snapshotted first: the result includes preSnapshotId, which awesomate_rollback_site can restore if anything looks wrong. The live site keeps its own search engine visibility (staging is always hidden from search engines; that setting is not copied to live); if searchEngineVisibility.warning is present, live may now be hidden from search engines, so relay it to the user. **Confirm with the user before promoting: it replaces the live site.** Requires shell access (Support Plus+).",
     inputSchema: {
       domain: external_exports.string().describe("The LIVE site domain whose staging copy should go live")
     }
@@ -43452,7 +43464,7 @@ server.registerTool(
   "awesomate_knowledge_provision",
   {
     annotations: annotate("awesomate_knowledge_provision", MUTATING),
-    description: `Enable the Knowledge Base for this account (creates their isolated tenant on the Awesomate knowledge platform and wires the n8n credential). Idempotent \u2014 safe to re-call; a pending:true response means provisioning continues in the background: poll awesomate_knowledge_status. consent_required \u2192 send the user to Settings \u2192 Features (hub.awesomate.ai/settings?tab=features): under the Knowledge row, the second line "Use your content for Knowledge". Switching on Knowledge itself is NOT the consent. They must switch it themselves; re-check, then retry. upgrade_required \u2192 relay the upsell, don't retry. Get the user's explicit go-ahead before enabling.`,
+    description: `Enable the Knowledge Base for this account (creates their isolated tenant on the Awesomate knowledge platform and wires the n8n credential). Idempotent: safe to re-call, and the account owner re-calling on an active account puts back a missing "Awesomate Knowledge Base" n8n credential. The response's credential is {status, verified?, reason?}: created / exists are fine; adopted with verified:false means an existing credential was kept and its key may be stale (tell the user to rotate the Knowledge key); skipped or failed carries the reason (for example no n8n API key stored, so the user connects n8n first); a pending:true response means provisioning continues in the background: poll awesomate_knowledge_status. consent_required \u2192 send the user to Settings \u2192 Features (hub.awesomate.ai/settings?tab=features): under the Knowledge row, the second line "Use your content for Knowledge". Switching on Knowledge itself is NOT the consent. They must switch it themselves; re-check, then retry. upgrade_required \u2192 relay the upsell, don't retry. Get the user's explicit go-ahead before enabling.`,
     inputSchema: {}
   },
   async () => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awesomate/hosting-mcp",
-  "version": "0.91.1",
+  "version": "0.92.2",
   "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,24 @@
 {
   "versions": [
+    {
+      "version": "0.92.2",
+      "highlights": [
+        "Publishing a staging copy keeps the live site's search engine setting, instead of hiding the live site from Google like the staging copy, and says so if it could not"
+      ]
+    },
+    {
+      "version": "0.92.1",
+      "highlights": [
+        "Turning on Knowledge again now puts back a missing n8n credential for it, and says why when it cannot (for example, n8n is not connected yet)"
+      ]
+    },
+    {
+      "version": "0.92.0",
+      "highlights": [
+        "Claude says whose key it is: the account owner's, or a team member's own, which does only what that person can do",
+        "Connecting on a computer already connected to the same account as someone else stops and asks, instead of replacing their key"
+      ]
+    },
     {
       "version": "0.91.1",
       "highlights": [

package/skill/awesomate-hosting/SKILL.md

@@ -40,6 +40,7 @@ before any work** — every tool response is stamped `account: <slug> (source:
 once (plus `awesomate_get_limits` before any create/change) and cache:
 
 - **`plan`** and **`capabilities.shell`** — decides which branch below you're on.
+- **`key`**: whose key this is. When `key.holder` is `person`, say so first ("This is Mia's own Claude Code, with view-only access") and never offer work their access does not include; if they ask for it, say the account owner can do it. A person's key never has a shell.
 - **`attention`** — `{unreadNotifications, erroringWorkflows7d, patExpiresInDays}`.
   If it shows erroring workflows or unread notifications, say so in ONE line
   ("two of your automations failed this week — want me to look?") before the
@@ -230,7 +231,7 @@ MCP, so say that rather than stopping.
 | Tool | Reach for it when |
 |---|---|
 | `awesomate_whoami` | First call of every session — which account this folder acts on (zero network) |
-| `awesomate_get_context` | Session start: plan, capabilities, PAT expiry, `attention`, skill updates, and `key`: whose key this is (always the account owner's today, so everything is done as the owner; team members cannot connect their own yet). A tool the key's scopes do not cover is refused at once in the hub's words: relay it, never retry |
+| `awesomate_get_context` | Session start: plan, capabilities, PAT expiry, `attention`, skill updates, and `key`: whose key this is (the account owner's, so everything is done as the owner, or a team member's own, `holder: 'person'`, which does only what they can do in the hub). A tool the key's scopes do not cover is refused at once in the hub's words: relay it, never retry |
 | `awesomate_get_limits` | Before any create/change — live plan limits + workflow/AI-editor credit balances |
 | `awesomate_get_plan_features` | The live plan ladder, so upgrade talk is accurate |
 | `awesomate_business` | Before writing anything in the business's name: its own name, services, voice, colours, contact details. `read:'documents'` / `read:'document'` for the brand guide, voice guide and business summary; `read:'suggestions'` for details awaiting the owner's yes |
@@ -462,7 +463,10 @@ AI crawlers — anyone with the link can view, perfect for client review).
   `--domain <staging domain>`), send the user the staging URL to review.
 - `awesomate_site_staging_promote <live domain>` — publishes staging over live.
   Live is auto-snapshotted first; report the returned `preSnapshotId` as the
-  undo handle (`awesomate_rollback_site`). **Confirm before promoting.**
+  undo handle (`awesomate_rollback_site`). Live keeps its own search engine
+  setting; if the result carries `searchEngineVisibility.warning`, tell the
+  user live may now be hidden from search engines and how to check.
+  **Confirm before promoting.**
 - `awesomate_site_staging_discard <live domain>` — deletes the staging copy;
   live untouched. **Confirm — unpublished staging changes are lost.**
 

package/skill/awesomate-hosting/references/connect-troubleshooting.md

@@ -25,6 +25,14 @@ The bootstrap prints a final `AWESOMATE CONNECT: SUCCESS account=<slug>` (or
 silence. `PARTIAL` means the token/pin are stored but a step (listed in
 `issues=`) needs the printed manual fix.
 
+`FAILED reason=profile-belongs-to-someone-else` means this computer is already
+connected to the same account as a different person (an owner and a team member
+sharing a computer). Nothing was saved. Ask the person at the computer which key
+should stay; re-run with `--replace` only on their clear yes, never on your own.
+Otherwise they connect from their own user account on the computer. The key made
+by the refused run is unused: they can remove it in the hub at Settings,
+Account, Your Claude Code.
+
 ## Sandboxed / ephemeral environments (cloud agent containers)
 
 - **Egress proxy**: if `HTTPS_PROXY`/`HTTP_PROXY` is set, the environment

package/skill/awesomate-hosting/scripts/bootstrap.mjs

@@ -11,7 +11,7 @@
  * access token itself is never printed.
  *
  * Usage (Claude runs this — the user doesn't touch a terminal):
- *   node bootstrap.mjs --code amt_bs_XXXX [--account <slug>] [--pin-dir <dir>]
+ *   node bootstrap.mjs --code amt_bs_XXXX [--account <slug>] [--pin-dir <dir>] [--replace]
  *   node bootstrap.mjs --pat amt_pat_XXXX [--account <slug>]   # resume: skip redeem
  *
  * --account asserts WHICH account this connect is for — mismatch aborts before
@@ -472,6 +472,7 @@ async function main() {
       shellAccess: Boolean(ctx.capabilities?.shell),
       cpanel: ctx.cpanel ?? null,
       expiresAt: ctx.patExpiresAt ?? null,
+      ...(ctx.key?.holder === 'person' ? { keyKind: 'person_device' } : {}),
     };
   } else {
     console.log(`Redeeming setup code against ${apiBase} …`);
@@ -514,6 +515,21 @@ async function main() {
     redeemed.email = redeemed.email ?? context?.email ?? null;
   }
 
+  // One computer, two people (per-person keys design §6.1): never silently swap whose key this
+  // account uses here. An owner and a team member on a shared computer each keep their own.
+  const saved = readJsonFile(credPath) ?? {};
+  const before = (saved.profiles ?? {})[slug] ?? (saved.slug === slug ? saved : null);
+  const beforeEmail = typeof before?.email === 'string' ? before.email.trim().toLowerCase() : null;
+  const newEmail = typeof redeemed.email === 'string' ? redeemed.email.trim().toLowerCase() : null;
+  const replacing = Boolean(beforeEmail && newEmail && beforeEmail !== newEmail);
+  if (replacing && !process.argv.includes('--replace')) {
+    console.error(`This computer is already connected to "${slug}" as ${beforeEmail}. Connecting as ${newEmail} would replace that key here.`);
+    console.error('Ask the person at this computer which key should stay. Only on their clear yes, run the same command again with --replace; otherwise connect from your own user account on this computer.');
+    console.error(`The new key for ${newEmail} was made but not saved here. If it will not be used, remove it in the hub: Settings, Account, Your Claude Code.`);
+    console.error('AWESOMATE CONNECT: FAILED reason=profile-belongs-to-someone-else');
+    process.exit(1);
+  }
+
   const profile = {
     apiBase,
     pat: redeemed.pat,
@@ -523,6 +539,8 @@ async function main() {
     plan: redeemed.plan,
     cpanel: redeemed.cpanel ?? null,
     expiresAt: redeemed.expiresAt ?? null,
+    // Someone else's SSH key never carries over to this person's profile.
+    ...(replacing ? { ssh: undefined } : {}),
   };
   mergeProfile(profile);
   console.log(`✓ Access token stored as profile "${slug}" in ${credPath} (chmod 600). Plan: ${redeemed.plan}.`);
@@ -571,6 +589,8 @@ async function main() {
         console.log('  Everything else is set up. This usually means hosting isn\'t fully provisioned — contact Awesomate support, then ask me to "retry SSH setup".');
       }
     }
+  } else if (redeemed.keyKind === 'person_device') {
+    console.log('• This is your own key: it does what you can do in the hub. SSH and deploys stay with the account owner.');
   } else {
     console.log('• Plan has no shell access — read/status mode. Upgrade to Support Plus for SSH + deploy.');
   }

package/skill/awesomate-onebrain/SKILL.md

@@ -260,8 +260,8 @@ while 1Brain is on.
   person's Task goes too), or move one on an older course to the role's
   current course (progress is read again from the new course). Each only on
   the owner's yes.
-- **`my_onboarding`**: the plans of the person this key belongs to, which
-  today is always the account owner.
+- **`my_onboarding`**: the plans of the person this key belongs to: the
+  account owner, or a team member on their own key.
 - Writing quizzes and acknowledgements, and sharing a course with a learner,
   are 1Brain's own connector's work (2d), owners and admins only.