@adrata/adrata-mcp 1.0.46 → 1.0.47

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adrata/adrata-mcp",
-  "version": "1.0.46",
+  "version": "1.0.47",
   "description": "Adrata MCP Server \u2014 connect Claude Code, Codex, Gemini, Cursor, and other AI tools to your CRM. About 275 tools registered at startup for companies, people, deals, actions, buyer groups, warm intros, webhooks and intelligence, plus 65 more behind eight named toolsets you load with enable_toolset.",
   "type": "module",
   "main": "server.js",

package/server.json

@@ -3,7 +3,7 @@
   "name": "com.adrata/adrata-mcp",
   "description": "Adrata revenue-intelligence MCP server: companies, people, opportunities, actions, buyer groups, enrichment, email, and workspace operations for AI agents.",
   "status": "active",
-  "version": "1.0.46",
+  "version": "1.0.47",
   "websiteUrl": "https://adrata.com/developers",
   "repository": {
     "url": "https://github.com/adrata/adrata",
@@ -15,7 +15,7 @@
       "registryType": "npm",
       "registryBaseUrl": "https://registry.npmjs.org",
       "identifier": "@adrata/adrata-mcp",
-      "version": "1.0.46",
+      "version": "1.0.47",
       "transport": {
         "type": "stdio"
       },

package/tools/provisioning/onboarding-tools.js

@@ -392,6 +392,42 @@ export function validateOnboardingArgs(args = {}) {
   return problems;
 }
 
+/**
+ * Whether the adaptive payload (launch, preparedAccountIds, preparedNote,
+ * source) is durable, read FROM the invite response rather than assumed. The
+ * route returns `recorded` alongside `inviteUrl`: `true` means the
+ * workspace_invitation_records row exists; `false` means the link works but
+ * the record was not written. An absent `recorded` is reported as unknown —
+ * `null` — rather than asserted either way.
+ */
+export function describeAdaptivePayloadDurability(payload = {}) {
+  const recorded = payload?.recorded;
+  if (recorded === true) {
+    return {
+      adaptivePayloadDurable: true,
+      adaptivePayloadNote:
+        'The seat and the link are live, and the launch, preparedAccountIds, preparedNote and source'
+        + ' were stored with the invitation (recorded: true).',
+    };
+  }
+  if (recorded === false) {
+    return {
+      adaptivePayloadDurable: false,
+      adaptivePayloadNote:
+        'The seat and the link are live, but the endpoint reported recorded: false — the invitation'
+        + ' record carrying launch, preparedAccountIds, preparedNote and source was not written, so it'
+        + ' will not appear in the issued list and cannot be revoked from it.',
+    };
+  }
+  return {
+    adaptivePayloadDurable: null,
+    adaptivePayloadNote:
+      'The seat and the link are live. The endpoint did not confirm whether the invitation record'
+      + ' carrying launch, preparedAccountIds, preparedNote and source was written (no `recorded`'
+      + ' field in the response), so durability is unknown rather than asserted.',
+  };
+}
+
 /** The exact body this tool would send. Kept in one place so preview and live write cannot drift. */
 export function buildInvitationBody(args = {}) {
   const body = {
@@ -404,19 +440,19 @@ export function buildInvitationBody(args = {}) {
   if (args.managerId) body.managerId = args.managerId;
 
   // ── The adaptive payload ────────────────────────────────────────────────
-  // INTEGRATION POINT (2026-09-06): these four fields are sent and the
-  // DEPLOYED endpoint ignores them. `InviteMemberRequest` in
-  // `code/api/src/routes/v1/entities/org/workspace/members.rs` declares
-  // exactly `email`, `role` and `manager_id`; serde drops unknown fields
-  // silently, so the call succeeds, a link is minted, and the launch is
-  // simply not recorded. They are sent anyway rather than withheld, because
-  // the route change carrying `InvitationContext` is in flight on
-  // `feature/onboarding-grant-record` and the wire shape should not need a
-  // second edit when it lands.
+  // These four fields are stored by the deployed endpoint. `InviteMemberRequest`
+  // in `code/api/src/routes/v1/entities/org/workspace/members.rs` declares
+  // `launch`, `prepared_account_ids`, `prepared_note` and `source` with
+  // `#[serde(default)]` (camelCase via `alias`), and `mint_workspace_invitation`
+  // in `invitations.rs` binds them into `workspace_invitation_records`. The
+  // route answers with `recorded: true|false` saying whether that durable row
+  // was written, and the live-write result below reports durability FROM that
+  // field rather than from an assumption about what the server does.
   //
-  // What this means for a caller TODAY, and it is stated in the tool's own
-  // response rather than only here: the seat and the link are real, and the
-  // adaptive configuration is not yet durable.
+  // (History: until 2026-09-06 the endpoint accepted only email, role and
+  // managerId and dropped the rest; the tool then said so in its response.
+  // That note outlived the fix and told an AE a stored configuration was not
+  // durable — hence the rule above: report what the response says.)
   //
   // Note also that `InviteMemberRequest` carries no
   // `#[serde(rename_all = "camelCase")]` — `manager_id` works only because it
@@ -625,12 +661,12 @@ export function registerProvisioningTools(
           preparedAccountIds: body.preparedAccountIds ?? [],
           preparedAccountCount: body.preparedAccountIds?.length ?? 0,
           preparedNote: body.preparedNote ?? null,
-          adaptivePayloadDurable: false,
+          adaptivePayloadDurable: null,
           adaptivePayloadNote:
-            'INTEGRATION POINT: the deployed invite endpoint accepts email, role and managerId only, so'
-            + ' launch, preparedAccountIds, preparedNote and source are sent but not yet stored. The seat'
-            + ' and the link are real; the adaptive configuration becomes durable when the'
-            + ' workspace_invitation_records route change ships.',
+            'Not known until minted. The invite endpoint stores launch, preparedAccountIds, preparedNote'
+            + ' and source with the invitation (members.rs InviteMemberRequest → invitations.rs'
+            + ' mint_workspace_invitation) and reports `recorded` on the live write; the live result'
+            + ' carries that answer.',
           preview: validation,
           body,
           note:
@@ -712,10 +748,7 @@ export function registerProvisioningTools(
         inviteUrl,
         launch: body.launch ?? null,
         preparedAccountIds: body.preparedAccountIds ?? [],
-        adaptivePayloadDurable: false,
-        adaptivePayloadNote:
-          'The seat and the link are live. launch/preparedAccountIds/preparedNote were sent but the'
-          + ' deployed endpoint does not yet store them — see the integration point in tools/provisioning.js.',
+        ...describeAdaptivePayloadDurability(payload),
         credentialWarning:
           'inviteUrl is a credential: anyone holding it can seat themselves in this workspace. Deliver it'
           + ' over a trusted channel and do not paste it into a log, a ticket, or a shared document.',