@awesomate/hosting-mcp 0.52.0 → 0.53.0

package/dist/index.js

@@ -42804,17 +42804,19 @@ var crmAttribute = external_exports.object({
   choices: external_exports.array(external_exports.string().max(100)).max(200).optional().describe("required for choice / choices"),
   required: external_exports.boolean().optional(),
   sensitivity: external_exports.enum(["ordinary", "personal", "sensitive"]).optional().describe("sensitive values are never readable by AI"),
-  readable_by_ai: external_exports.boolean().optional().describe("default false: only readable attributes reach awesomate_crm_rows")
+  readable_by_ai: external_exports.boolean().optional().describe("default false: only readable attributes reach awesomate_crm_rows"),
+  visible_to: external_exports.array(external_exports.string().max(31)).max(10).nullable().optional().describe("which of an app's signed-in roles see it, e.g. ['staff']; leave out for everyone who can read the record")
 });
 server.registerTool(
   "awesomate_crm_kinds",
   {
     annotations: annotate("awesomate_crm_kinds", MUTATING),
-    description: "The kinds of app data in the client's own database (the tables an app keeps: jobs, memos, bookings, messages), created directly from here on Support Plus and above. action 'list': every kind with its attributes and links. 'define' {key, label?, label_plural?, attributes, links?}: a new kind; links: [{key, to, label?, required?}] where to is 'contact' or a kind already made, and each shows as <key>_id. 'add_attribute' {kind, attribute}. 'archive_attribute' {kind, key}: leaves the views, values kept. 'archive' {kind}: kept, restorable. No migration and no SQL: a kind is registry rows plus generated views. Business things whose values must be traced to a source (a property, an installed system) are 'tracked' kinds the owner accepts in the hub; they are refused here. Mark an attribute readable_by_ai only when the owner wants Claude and agents to see it, and never for anything sensitive. 'set_access' {kind, access} (or access on define): who among the people signed in to the account's apps (awesomate_crm_apps) may read and change records of this kind, by their role: {read: {<role>: <rule>}, write: {<role>: <rule>}}. A rule is all, none, own (records they created), or linked:<link path ending at a contact> (linked:customer: jobs whose customer is them; linked:job.customer: memos on their jobs), joined with |. A role with no rule gets nothing; the default lets owner and staff do everything and members nothing. A write must leave the record inside the person's rule. Confirm the design with the user before defining: a kind is part of their data, not scratch space.",
+    description: "The kinds of app data in the client's own database (the tables an app keeps: jobs, memos, bookings, messages), created directly from here on Support Plus and above. action 'list': every kind with its attributes and links. 'define' {key, label?, label_plural?, attributes, links?}: a new kind; links: [{key, to, label?, required?}] where to is 'contact' or a kind already made, and each shows as <key>_id. 'add_attribute' {kind, attribute}. 'archive_attribute' {kind, key}: leaves the views, values kept. 'set_visibility' {kind, key, visible_to}: which of an app's signed-in roles see that attribute (['staff'] for a cost or an internal note on a customer's job; null for everyone who can read the record; [] for none of them). Others read it as null and cannot write it; the database enforces it, and the account, Claude and hooks always see every attribute. 'archive' {kind}: kept, restorable. No migration and no SQL: a kind is registry rows plus generated views. Business things whose values must be traced to a source (a property, an installed system) are 'tracked' kinds the owner accepts in the hub; they are refused here. Mark an attribute readable_by_ai only when the owner wants Claude and agents to see it, and never for anything sensitive. 'set_access' {kind, access} (or access on define): who among the people signed in to the account's apps (awesomate_crm_apps) may read and change records of this kind, by their role: {read: {<role>: <rule>}, write: {<role>: <rule>}}. A rule is all, none, own (records they created), or linked:<link path ending at a contact> (linked:customer: jobs whose customer is them; linked:job.customer: memos on their jobs), joined with |. A role with no rule gets nothing; the default lets owner and staff do everything and members nothing. A write must leave the record inside the person's rule. Confirm the design with the user before defining: a kind is part of their data, not scratch space.",
     inputSchema: {
-      action: external_exports.enum(["list", "define", "add_attribute", "archive_attribute", "archive", "set_access"]),
-      kind: external_exports.string().max(41).optional().describe("the kind to change (add_attribute, archive_attribute, archive, set_access)"),
-      key: external_exports.string().max(41).optional().describe("define: the new kind; archive_attribute: the attribute"),
+      action: external_exports.enum(["list", "define", "add_attribute", "archive_attribute", "archive", "set_access", "set_visibility"]),
+      kind: external_exports.string().max(41).optional().describe("the kind to change (add_attribute, archive_attribute, archive, set_access, set_visibility)"),
+      key: external_exports.string().max(41).optional().describe("define: the new kind; archive_attribute, set_visibility: the attribute"),
+      visible_to: external_exports.array(external_exports.string().max(31)).max(10).nullable().optional().describe("set_visibility: the roles that see it, or null for everyone"),
       label: external_exports.string().max(80).optional(),
       label_plural: external_exports.string().max(80).optional(),
       attributes: external_exports.array(crmAttribute).max(60).optional(),
@@ -42826,7 +42828,7 @@ server.registerTool(
       }).optional().describe("define / set_access: {read: {<role>: <rule>}, write: {<role>: <rule>}}")
     }
   },
-  async ({ action, kind, key, label, label_plural, attributes, links, attribute, access }) => {
+  async ({ action, kind, key, label, label_plural, attributes, links, attribute, access, visible_to }) => {
     try {
       const cfg = requireConfig();
       if (action === "list") return textResult(await hubGet(cfg, "/api/my-crm/v1/kinds"));
@@ -42840,6 +42842,10 @@ server.registerTool(
         return textResult(await hubPut(cfg, `/api/my-crm/v1/kinds/${k}/access`, { access }));
       }
       if (action === "add_attribute") return textResult(await hubPost(cfg, `/api/my-crm/v1/kinds/${k}/attributes`, { attribute }));
+      if (action === "set_visibility") {
+        if (!key || visible_to === void 0) return errorResult(new Error("set_visibility needs key (the attribute) and visible_to (a list of roles, or null for everyone)."));
+        return textResult(await hubPut(cfg, `/api/my-crm/v1/kinds/${k}/attributes/${encodeURIComponent(key)}/visibility`, { visible_to }));
+      }
       if (action === "archive_attribute") {
         if (!key) return errorResult(new Error("archive_attribute needs key, the attribute."));
         return textResult(await hubDelete(cfg, `/api/my-crm/v1/kinds/${k}/attributes/${encodeURIComponent(key)}`));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awesomate/hosting-mcp",
-  "version": "0.52.0",
+  "version": "0.53.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,12 @@
 {
   "versions": [
+    {
+      "version": "0.53.0",
+      "highlights": [
+        "Fields only your team sees: mark an attribute visible to staff only (awesomate_crm_kinds, set_visibility), such as the cost behind a quote or an internal note on a job. Customers signed in to your portal read it as empty and cannot change it",
+        "Your own database enforces it, not the portal's code, and Bree, answering as the customer, never sees it either. You and Claude always see every field"
+      ]
+    },
     {
       "version": "0.52.0",
       "highlights": [

package/skill/awesomate-portals/SKILL.md

@@ -44,8 +44,13 @@ Ask, one or two at a time:
 
 - **Link the thing to the customer's contact.** That link is what "their own" means.
 - Mark an attribute `readable_by_ai` only when the owner wants Claude and AI assistants to see
-  it. Never for anything sensitive. App people see every attribute of a record they may read;
-  `readable_by_ai` is only about AI.
+  it. Never for anything sensitive. `readable_by_ai` is only about AI.
+- **Fields only the team sees** (a cost, an internal note): give the attribute
+  `visible_to: ['staff']` when defining it, or later with `awesomate_crm_kinds
+  {action:'set_visibility'}`. Customers read it as null and cannot write it; the database
+  enforces it, and so does what the assistant sees. Without `visible_to`, everyone who can read
+  the record sees the attribute. Don't make such an attribute `required` on a kind customers
+  create, or they cannot create one.
 - Show the owner the design ("A job has a title, a status and a quote, and belongs to a
   customer. Messages hang off a job.") and get a yes first.