@theronap/agnoclast-mcp 0.9.204 → 0.9.206

package/lib/member_remove_render.mjs

@@ -0,0 +1,29 @@
+// PURE: what remove_member prints (2026-10-02). Out of server.mjs so a test can reach it.
+//
+// ⚠ THE FIRST ANSWER IS A QUESTION FOR THE PERSON, NOT AN ERROR. Removing someone from a brain takes
+// access away from a real person, so the server changes nothing until it is called again with the token
+// for exactly the picture shown: who, from which brain, and where every one of their pages goes.
+//
+// Names, emails and brain names are other people's text: one line each, bounded.
+const one = (s, n = 160) => String(s ?? '').replace(/\s+/g, ' ').trim().slice(0, n)
+
+export function renderRemovalQuestion(out) {
+  const p = out?.preview ?? {}
+  const lines = [
+    `NOT REMOVED — this needs the person's yes.${out?.stale ? ' (The picture changed since the last confirmation; this is the current one.)' : ''}`,
+    `Remove ${one(p.name, 80)} (${one(p.email, 120)}) from the brain "${one(p.brain, 80)}"?`,
+    'They lose access to this brain only. Their login, their other brains and everything they wrote stay.',
+  ]
+  for (const s of Array.isArray(p.summary) ? p.summary : []) lines.push(one(s, 400))
+  lines.push(`Tell the person exactly this and ask. Only if they say yes: remove_member again with confirm: "${one(out?.confirm_token, 40)}".`)
+  return lines.join('\n')
+}
+
+export function renderRemoved(out, person) {
+  const name = one(out?.displayName || person, 80)
+  const lines = [out?.alreadyInactive
+    ? `${name} was already removed from this brain — nothing more to do.`
+    : `Removed ${name} from "${one(out?.orgName, 80)}". They can no longer open anything in it.`]
+  for (const w of Array.isArray(out?.warnings) ? out.warnings : []) lines.push(`- ${one(w, 400)}`)
+  return lines.join('\n')
+}

package/lib/server.mjs

@@ -20,6 +20,7 @@ import { repoFullNameFrom, workingFilesFrom } from './capture.mjs'
 import { findTranscript, createWorkedFilesTracker } from './working_files.mjs'
 import { spawnObligationWorker } from './obligations_worker.mjs'
 import { renderObligations, renderPageObligations, tierReads, who } from './obligations_render.mjs'
+import { renderRemovalQuestion, renderRemoved } from './member_remove_render.mjs'
 import { renderSettings } from './settings_render.mjs'
 import { formatCreated, formatDryRun, formatSources, homeFromArgs, pickSource, renderHomeProblem } from './custom_sources.mjs'
 
@@ -3033,6 +3034,38 @@ function renderNudge(payload) {
     },
   )
 
+  // 2026-10-02. Removal was built in August with this tool planned and never wired, so an assistant could
+  // add people to a brain but not remove them. Two calls, always: the first changes nothing.
+  server.registerTool(
+    'remove_member',
+    {
+      title: 'Remove someone from a brain',
+      description: "Remove a member from one of the person's brains — ONLY when the person asked you to. It takes access away from a real person, so the FIRST call changes nothing: it answers with who would be removed, from which brain, and where every one of their pages would go, plus a confirm token. Tell the person exactly that and ask. Only if they say yes, call again with `confirm` set to that token. Never pass a confirm token the person has not just approved. Removal is soft and per brain: the person keeps their login, their other brains and everything they wrote; their pages go to a steward (usually their manager), and their own profile becomes a person page. Only an owner or admin of the brain can remove anyone, never themselves, and never the last owner. Use an email address when a name could match two people.",
+      inputSchema: {
+        person: z.string().describe("who to remove: their email address, or their name as it appears in the brain"),
+        brain: z.string().optional().describe('which brain — required if the person belongs to more than one'),
+        confirm: z.string().optional().describe('ONLY after the person has seen the removal and said yes: the confirm token from the first call'),
+      },
+    },
+    async ({ person, brain, confirm }) => {
+      let res
+      try {
+        res = await fetchCortex(`${BASE}/api/members/remove`, {
+          method: 'POST',
+          headers: { Authorization: `Bearer ${TOKEN}`, 'Content-Type': 'application/json' },
+          body: JSON.stringify({ person, brain, confirm }),
+        })
+      } catch (e) { return toolError(`Could not reach Agnoclast: ${e.message}`) }
+      const out = await res.json().catch(() => null)
+      if (res.status === 409 && out?.error === 'confirm_removal') {
+        // Not an error: a person has to decide. Said as the question it is.
+        return { content: [{ type: 'text', text: renderRemovalQuestion(out) }] }
+      }
+      if (!res.ok) return toolError(`Not removed: ${out?.detail ?? out?.error ?? res.status}`)
+      return { content: [{ type: 'text', text: renderRemoved(out, person) }] }
+    },
+  )
+
   server.registerTool(
     'set_obligation_tier',
     {
@@ -4081,7 +4114,7 @@ function renderNudge(payload) {
     'add_to_brain',
     {
       title: 'Add someone to one of your brains',
-      description: "Add a person to one of your brains, or work out what it would take. Resolves which brain, whether you may add to it, and the manager id they are placed under. WITHOUT execute:true it only reports the plan and hands back a console link — call it that way first and show the user what you are about to do. WITH execute:true it performs the add, and then `brain` is REQUIRED: an access grant must never be aimed by a shared write pointer. Adding cannot be undone through the API. IF THE BRAIN PAYS FOR ITS MEMBERS' SEATS, adding someone raises its owner's monthly charge: the first execute is refused with the new total, you ASK THE USER whether to accept that charge, and only on a yes re-run with confirm_seat_total set to that number. Use when asked to invite/add someone to a brain.",
+      description: "Add a person to one of your brains, or work out what it would take. Resolves which brain, whether you may add to it, and the manager id they are placed under. WITHOUT execute:true it only reports the plan and hands back a console link — call it that way first and show the user what you are about to do. WITH execute:true it performs the add, and then `brain` is REQUIRED: an access grant must never be aimed by a shared write pointer. To undo an add later, use remove_member — it shows the person what removal would do and asks first. IF THE BRAIN PAYS FOR ITS MEMBERS' SEATS, adding someone raises its owner's monthly charge: the first execute is refused with the new total, you ASK THE USER whether to accept that charge, and only on a yes re-run with confirm_seat_total set to that number. Use when asked to invite/add someone to a brain.",
       inputSchema: {
         email: z.string().describe("the person's email address — the login their Agnoclast account is (or will be) on"),
         name: z.string().optional().describe('their full name; falls back to the email local-part'),
@@ -4225,7 +4258,7 @@ function renderNudge(payload) {
         // What the seat sync did, in the server's words: the new monthly total, or that the seat
         // could NOT be charged and the brain is not paying for them yet.
         const seatLine = typeof r.seatNote === 'string' && r.seatNote ? `\n${r.seatNote}` : ''
-        return { content: [{ type: 'text', text: `Added ${payload.name} <${payload.email}> to ${target.name} as ${payload.role}, placed under you.\n${how}${page}${seatLine}\n\nThis cannot be undone through the API — removing a membership currently needs direct database access.` }] }
+        return { content: [{ type: 'text', text: `Added ${payload.name} <${payload.email}> to ${target.name} as ${payload.role}, placed under you.\n${how}${page}${seatLine}\n\nTo undo this, remove_member takes them out of this brain — it shows you what that would do and asks first.` }] }
       }
 
       // ADR-0023: does this brain already have a page about them? The inviter decides — list, never pick.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theronap/agnoclast-mcp",
-  "version": "0.9.204",
+  "version": "0.9.206",
   "description": "Connect your AI assistant to Cortex — your org's projects, activity, gaps, and directives, scoped to you.",
   "type": "module",
   "bin": {