@sutraspaces/mcp-server 1.0.1 → 1.1.2

package/README.md

@@ -1,6 +1,6 @@
 # Sutra MCP Server
 
-An [MCP](https://modelcontextprotocol.io) server that connects AI agents to the [Sutra Admin API](https://sutra.co). Manage spaces, members, content, discussions, surveys, plans, broadcasts, and more — all through your AI tools.
+An MCP server that connects AI agents to the Sutra Admin API. Manage spaces, members, contacts, content, discussions, surveys, plans, broadcasts, and more — all through your AI tools. See the [Sutra developer docs](https://sutra.co/developers/docs) for API documentation.
 
 ## Quick Start
 
@@ -52,6 +52,8 @@ Point your MCP client at `npx -y @sutraspaces/mcp-server` with the `SUTRA_API_TO
 |---|---|---|
 | `SUTRA_API_TOKEN` | Yes | Your Sutra Admin API token (`sutra_live_sk_...`) |
 | `SUTRA_BASE_URL` | No | Override the API URL (default: `https://api.sutra.co/api/admin/v1`) |
+| `SUTRA_HELP_CENTER_TOKEN` | No | Internal scoped admin key (`sutra_admin_...`) for Lotus Help Center tools |
+| `SUTRA_HELP_CENTER_BASE_URL` | No | Override the Help Center API URL (default: `https://api.sutra.co/api/v4/lotus/help`) |
 
 ## Available Tools
 
@@ -60,15 +62,22 @@ Point your MCP client at `npx -y @sutraspaces/mcp-server` with the `SUTRA_API_TO
 
 ### Spaces
 - **list_spaces** — List all spaces the API token can access
+- **list_membership_spaces** — List basic read-only information about spaces where the API token owner is a member
 - **get_space** — Get details for a single space
 - **list_child_spaces** — List direct child spaces
 - **create_space** — Create a new space (top-level or child)
+- **create_child_space** — Create a child space and make it visible through placement
+- **attach_child_space** — Attach an existing space under a parent and make it visible
+- **update_child_space_placement** — Move or repair a child space display
+- **detach_child_space** — Detach a child from one parent without deleting it
 - **update_space** — Update space name, description, type, privacy, or state
 - **delete_space** — Delete/archive a space
 - **reorder_child_spaces** — Reorder children within a parent
 
+Use `sp_...` IDs, not slugs. For normal course and section pages, use `placement.surface = "auto"`.
+
 ### Members
-- **list_members** — List space members with optional email/user_id filtering
+- **list_members** — List space members with optional email, user_id, search, role, state, and custom property filtering
 - **get_member** — Get member details
 - **add_member** — Add a member by email or user ID
 - **update_member** — Update role or notification settings
@@ -77,15 +86,42 @@ Point your MCP client at `npx -y @sutraspaces/mcp-server` with the `SUTRA_API_TO
 - **bulk_add_members** — Add up to 100 members at once
 - **bulk_remove_members** — Remove up to 100 members at once
 
+### Contacts
+- **list_contacts** — List CRM contacts from the Contacts/Interested layer with optional email, search, and custom property filtering
+- **get_contact** — Get contact details
+- **get_contact_property_values** — Read property values for a contact
+- **update_contact_property_values** — Set or clear property values for a contact
+- **bulk_update_contact_property_values** — Set or clear property values for up to 100 contacts at once
+
 ### Content & Discussions
-- **list_content** / **get_content_block** / **create_content** / **update_content** / **delete_content** — Manage content blocks
+- **get_document_capabilities** / **get_document** — Read document editing rules and the visible Tiptap document
+- **replace_document** / **insert_document_nodes** / **update_document_node** / **delete_document_node** / **move_document_node** — Edit visible document content by Tiptap node UID
+- **list_content** / **get_content_block** / **create_content** / **update_content** / **delete_content** — Legacy content-block mirror tools
 - **reorder_content** — Reorder content blocks within a space
+
+### Media Uploads
+- **create_media_upload** — Create a server-mediated direct-to-S3 upload session
+- **complete_media_upload** — Verify the uploaded object and queue video processing
+- **get_media_upload** — Read upload and processing status
+- **cancel_media_upload** — Abandon a pending upload
+- **create_media_reference** — Insert a Loom, YouTube, or Vimeo embed without uploading a file
+
+### Design Tools
+
+- **get_design_capabilities** — Read Sutra's renderer-aware design manifest
+- **get_space_design** — Read current page-design nodes and digest for a space
+- **validate_space_design** — Validate proposed page-design nodes
+- **create_or_update_design_draft** — Create or update a digest-guarded design draft
+- **publish_design_draft** — Publish a draft with conflict and destructive-omission protection
+- **restore_design_draft** — Restore the pre-publish backup for a published design draft
+- **import_design_asset** — Re-host an external image URL and return the canonical Sutra URL
 - **list_messages** / **get_message** / **create_message** / **update_message** / **delete_message** — Manage discussion messages
 - **list_reflections** / **get_reflection** / **create_reflection** / **update_reflection** / **delete_reflection** — Manage threaded replies
 
 ### Properties
 - **list_member_properties** / **create_member_property** / **update_member_property** / **delete_member_property** — Manage custom member property definitions
-- **get_member_property_values** / **update_member_property_values** — Read and set property values per member
+- **get_member_property_values** / **update_member_property_values** / **bulk_update_member_property_values** — Read, set, and bulk set property values for members
+- **get_contact_property_values** / **update_contact_property_values** / **bulk_update_contact_property_values** — Read, set, and bulk set property values for contacts
 - **list_space_properties** / **create_space_property** / **update_space_property** / **delete_space_property** — Manage custom space property definitions
 - **get_space_property_values** / **update_space_property_values** — Read and set property values per space
 
@@ -111,27 +147,52 @@ Point your MCP client at `npx -y @sutraspaces/mcp-server` with the `SUTRA_API_TO
 - **send_broadcast** — Send a broadcast to space members
 - **get_broadcast_delivery_status** — Check delivery progress
 
+### Help Center
+These tools are available only when `SUTRA_HELP_CENTER_TOKEN` is set.
+
+- **help_list_articles** / **help_get_article** — Read Lotus Help Center articles, metadata, and version history
+- **help_create_article** / **help_update_article** — Human/admin-style create and update through Lotus
+- **help_propose_article** — Submit an AI-authored draft as `ai_cobolt` and mark it pending human review
+- **help_propose_article_update** — Submit AI-authored changes to an existing article without publishing them
+- **help_review_article** — Approve or reject a pending article version
+- **help_publish_article** — Explicitly publish an article version
+- **help_list_collections** / **help_create_collection** / **help_update_collection** / **help_delete_collection** — Manage Help Center collections
+
+## Available Resources
+
+- **sutra://admin-api/overview** — Core Admin API concepts, public ID prefixes, scopes, pagination, and filtering
+- **sutra://admin-api/membership-spaces** — Difference between admin-manageable spaces and limited membership-space inventory
+- **sutra://admin-api/contacts-properties** — Contact listing and member/contact property value workflows
+- **sutra://admin-api/people-filtering** — Member and contact search, email, state, role, and custom property filtering
+- **sutra://design/capabilities** — Renderer-aware design rules and supported fonts for Sutra page-design tools
+
 ## API Concepts
 
 **Spaces** are the core building block — they can be courses, communities, forums, or any structured container. Spaces form hierarchies through parent-child relationships.
 
+**Membership spaces** are spaces where the API token owner is enrolled as a member. Use `list_membership_spaces` for basic read-only inventory. Use `list_spaces` for spaces where the token has admin access; membership-only spaces may still return 404 or 403 from admin subresource tools.
+
 **Members** belong to spaces. They have roles (member, editor, moderator) and can have custom properties attached.
 
+**Contacts** are CRM people in a space who are not enrolled members. Contacts use the same member property definitions as members, so AI agents can tag imported contacts before they join.
+
 **Content blocks** are structured content created by facilitators. **Messages** are discussion posts from participants. **Reflections** are threaded replies to messages.
 
-**All IDs** use readable prefixes: `sp_` (space), `mem_` (member), `usr_` (user), `blk_` (block/message), `reply_` (reflection), `surv_` (survey), `plan_` (plan), `enr_` (enrollment), `pay_` (payment), `cpn_` (coupon), `bcst_` (broadcast), `inv_` (invitation), `mprop_` / `sprop_` (property definitions).
+**All IDs** use readable prefixes: `sp_` (space), `mem_` (member), `contact_` (contact), `usr_` (user), `blk_` (block/message), `reply_` (reflection), `surv_` (survey), `plan_` (plan), `enr_` (enrollment), `pay_` (payment), `cpn_` (coupon), `bcst_` (broadcast), `inv_` (invitation), `mprop_` / `sprop_` (property definitions).
 
 **Pagination** is cursor-based. List endpoints return `{ data, pagination: { next_cursor, has_more } }`. Pass `cursor` to get the next page.
 
 **Filtering & Search** — most list endpoints accept optional query parameters to narrow results:
-- `q` — case-insensitive text search (spaces by name, members by name/email, surveys/broadcasts/plans by title/name, coupons by code)
+- `q` — case-insensitive text search (spaces by name, members/contacts by name/email when scoped, surveys/broadcasts/plans by title/name, coupons by code)
 - `state` / `status` — exact-match enum filters (e.g. `state=active` for spaces, `status=sent` for broadcasts)
 - `role` — filter members or invitations by role
 - `type` / `privacy` / `frequency` — filter by type, privacy level, or billing frequency
 - `user_id` — filter messages or payments by author/user
-- `email` — filter invitations by email (requires `members.email:read` scope)
+- `email` — filter members, contacts, or invitations by email (requires `members.email:read` scope)
+- `property_key` / `property_value` — filter members or contacts by one custom member property (requires `member_properties:read` scope)
+- `property_filters` — filter members or contacts by multiple custom member properties
 
-**Scopes** control what the API token can access. Tokens have read/write scope pairs like `spaces:read`, `members:write`, etc. Operations that exceed the token's scopes will return 403.
+**Scopes** control what the API token can access. Tokens have read/write scope pairs like `spaces:read`, `members:write`, etc. `membership_spaces:read` is required for read-only membership-space inventory. Operations that exceed the token's scopes will return 403.
 
 ## Architecture
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@sutraspaces/mcp-server",
-  "version": "1.0.1",
-  "description": "MCP server for the Sutra Admin API — manage spaces, members, content, and more via AI agents",
+  "version": "1.1.2",
+  "description": "MCP server for the Sutra Admin API — manage spaces, members, contacts, content, and more via AI agents",
   "type": "module",
   "main": "src/index.js",
   "bin": {
@@ -33,12 +33,12 @@
   ],
   "author": "Sutra <support@sutra.co> (https://sutra.co)",
   "license": "MIT",
-  "homepage": "https://github.com/joinsutra/mcp-server",
+  "homepage": "https://github.com/lorenzsell/sutra-mcp",
   "repository": {
     "type": "git",
-    "url": "https://github.com/joinsutra/mcp-server.git"
+    "url": "git+https://github.com/lorenzsell/sutra-mcp.git"
   },
   "bugs": {
-    "url": "https://github.com/joinsutra/mcp-server/issues"
+    "url": "https://github.com/lorenzsell/sutra-mcp/issues"
   }
 }

package/src/client.js

@@ -47,6 +47,10 @@ export class SutraAdminClient {
     return this.request("PATCH", path, { body, headers });
   }
 
+  put(path, body, headers) {
+    return this.request("PUT", path, { body, headers });
+  }
+
   delete(path, headers) {
     return this.request("DELETE", path, { headers });
   }

package/src/index.js

@@ -7,6 +7,8 @@ import { SutraAdminClient } from "./client.js";
 import { registerSpaceTools } from "./tools/spaces.js";
 import { registerMemberTools } from "./tools/members.js";
 import { registerContentTools } from "./tools/content.js";
+import { registerDocumentTools } from "./tools/documents.js";
+import { registerMediaTools } from "./tools/media.js";
 import { registerPropertyTools } from "./tools/properties.js";
 import { registerInvitationTools } from "./tools/invitations.js";
 import { registerSurveyTools } from "./tools/surveys.js";
@@ -14,6 +16,12 @@ import { registerPlanTools } from "./tools/plans.js";
 import { registerCouponTools } from "./tools/coupons.js";
 import { registerBroadcastTools } from "./tools/broadcasts.js";
 import { registerDeepTool } from "./tools/deep.js";
+import { registerAutomationTools } from "./tools/automations.js";
+import { registerHelpCenterTools } from "./tools/help-center.js";
+import { registerBlogTools } from "./tools/blog.js";
+import { registerDesignTools } from "./tools/design.js";
+import { registerAdminApiResources } from "./resources/admin-api.js";
+import { registerDesignResources } from "./resources/design.js";
 
 const SUTRA_API_TOKEN = process.env.SUTRA_API_TOKEN;
 const SUTRA_BASE_URL = process.env.SUTRA_BASE_URL;
@@ -29,9 +37,9 @@ if (!SUTRA_API_TOKEN) {
 
 const server = new McpServer({
   name: "sutra",
-  version: "1.0.0",
+  version: "1.1.0",
   description:
-    "Sutra Admin API — manage spaces, members, content, discussions, surveys, plans, broadcasts, and more.",
+    "Sutra Admin API — manage spaces, members, contacts, content, discussions, surveys, plans, broadcasts, and more.",
 });
 
 const client = new SutraAdminClient(SUTRA_API_TOKEN, SUTRA_BASE_URL);
@@ -39,6 +47,8 @@ const client = new SutraAdminClient(SUTRA_API_TOKEN, SUTRA_BASE_URL);
 registerSpaceTools(server, client);
 registerMemberTools(server, client);
 registerContentTools(server, client);
+registerDocumentTools(server, client);
+registerMediaTools(server, client);
 registerPropertyTools(server, client);
 registerInvitationTools(server, client);
 registerSurveyTools(server, client);
@@ -46,6 +56,12 @@ registerPlanTools(server, client);
 registerCouponTools(server, client);
 registerBroadcastTools(server, client);
 registerDeepTool(server, client);
+registerAutomationTools(server, client);
+registerDesignTools(server, client);
+registerHelpCenterTools(server);
+registerBlogTools(server);
+registerAdminApiResources(server);
+registerDesignResources(server, client);
 
 async function main() {
   const transport = new StdioServerTransport();

package/src/resources/admin-api.js

@@ -0,0 +1,136 @@
+const RESOURCES = [
+  {
+    name: "sutra-admin-api-overview",
+    title: "Sutra Admin API Overview",
+    uri: "sutra://admin-api/overview",
+    description: "Core Sutra Admin API concepts, IDs, scopes, pagination, and filtering.",
+    text: `# Sutra Admin API Overview
+
+The Sutra Admin API lets authorized tokens manage spaces, members, contacts, content, invitations, properties, surveys, plans, coupons, and broadcasts.
+
+Important IDs:
+- Spaces use sp_ IDs.
+- Members use mem_ IDs.
+- Contacts use contact_ IDs.
+- Users use usr_ IDs.
+- Member property definitions use mprop_ IDs.
+- Space property definitions use sprop_ IDs.
+
+Pagination:
+- List tools return data and pagination.
+- Pass cursor to fetch the next page.
+- Limit defaults to 25 unless the tool says otherwise.
+
+Scopes:
+- members:read reads members and contacts.
+- members:write writes member/contact-related values where supported.
+- spaces:read lists spaces where the token owner has admin access.
+- membership_spaces:read lists basic read-only inventory for spaces where the token owner is a member.
+- members.email:read is required to see or filter by email.
+- member_properties:read is required to list definitions, read values, and filter people by properties.
+- member_properties:write is required to create/update definitions or set values.
+`,
+  },
+  {
+    name: "sutra-contacts-properties",
+    title: "Contacts and Member Properties",
+    uri: "sutra://admin-api/contacts-properties",
+    description: "How to list contacts and set custom property values for members or contacts.",
+    text: `# Contacts and Member Properties
+
+Contacts are CRM people in a space who are not enrolled members. They appear in Sutra's Contacts/Interested layer and use the same member property definitions as members.
+
+Useful tools:
+- list_contacts: list contacts in a space.
+- get_contact: get one contact by contact_ ID.
+- get_contact_property_values: read values for one contact.
+- update_contact_property_values: set or clear values for one contact.
+- bulk_update_contact_property_values: set or clear values for up to 100 contacts in one idempotent request.
+- bulk_update_member_property_values: set or clear values for up to 100 members in one idempotent request.
+
+Property value payloads are objects keyed by property key or mprop_ ID. Use null to clear a value.
+
+Example contact bulk update item:
+{
+  "contact_id": "contact_abc123",
+  "properties": {
+    "mailing_list_opt_in": "Not yet subscribed",
+    "in_person_workshop": "Sweden"
+  }
+}
+
+Use an idempotency_key for bulk updates so retries are safe.
+`,
+  },
+  {
+    name: "sutra-people-filtering",
+    title: "Member and Contact Filtering",
+    uri: "sutra://admin-api/people-filtering",
+    description: "Filtering members and contacts by search, email, state, role, and custom property values.",
+    text: `# Member and Contact Filtering
+
+list_members supports:
+- email: exact email filter, requires members.email:read.
+- q: case-insensitive name/email search.
+- user_id: exact usr_ filter.
+- role: member, editor, or moderator.
+- state: active or pending.
+- property_key and property_value: filter by one custom property.
+- property_filters: filter by multiple custom properties.
+
+list_contacts supports:
+- email: exact email filter, requires members.email:read.
+- q: case-insensitive name/email search.
+- property_key and property_value: filter by one custom property.
+- property_filters: filter by multiple custom properties.
+
+Property filtering requires member_properties:read. property_key can be a property key or an mprop_ ID. Select and multi_select filters may use option names or stored option values.
+
+Example multiple filters:
+[
+  { "property_key": "mailing_list_opt_in", "property_value": "Not yet subscribed" },
+  { "property_key": "in_person_workshop", "property_value": "Sweden" }
+]
+`,
+  },
+  {
+    name: "sutra-membership-spaces",
+    title: "Membership Spaces",
+    uri: "sutra://admin-api/membership-spaces",
+    description: "Difference between admin-manageable spaces and limited membership-space inventory.",
+    text: `# Membership Spaces
+
+Use list_spaces when you need spaces where the API token can perform admin operations.
+
+Use list_membership_spaces when you only need a basic inventory of spaces where the token owner is a member. It returns IDs, names, type, state, privacy, timestamps, membership state, membership role, joined_at, and admin_access.
+
+Membership-space results are read-only. A space with admin_access: false is included for inventory, but admin subresource tools such as list_members, list_content, list_child_spaces, or get_space can still return 404 or 403 for that space.
+
+Required scope:
+- membership_spaces:read
+`,
+  },
+];
+
+export function registerAdminApiResources(server) {
+  for (const resource of RESOURCES) {
+    server.registerResource(
+      resource.name,
+      resource.uri,
+      {
+        title: resource.title,
+        description: resource.description,
+        mimeType: "text/markdown",
+      },
+      async () => ({
+        contents: [
+          {
+            uri: resource.uri,
+            mimeType: "text/markdown",
+            text: resource.text,
+          },
+        ],
+      })
+    );
+  }
+}

package/src/resources/design.js

@@ -0,0 +1,77 @@
+const BUNDLED_CAPABILITIES_MARKDOWN = `# Sutra Design Capabilities
+
+Read this before designing Sutra pages.
+
+- Use get_design_capabilities for the live manifest whenever possible.
+- Read get_space_design before changing a page and keep its content_digest as base_digest.
+- Validate nodes before creating or publishing a draft.
+- Use create_or_update_design_draft and publish_design_draft instead of raw content writes.
+- If publish returns 409 conflict, re-read the design and rebase instead of retrying blindly.
+- Do not emit image_keywords; direct design writes require real image URLs.
+- Use actionCallbackValue and actionCallbackTarget for action buttons.
+- Use 12-unit grid dist arrays such as [6,6], [8,4], or [4,4,4].
+- Use only font families returned by get_design_capabilities fonts.available; other fonts fall back at render time.
+`;
+
+export function registerDesignResources(server, client) {
+  server.registerResource(
+    "sutra-design-capabilities",
+    "sutra://design/capabilities",
+    {
+      title: "Sutra Design Capabilities",
+      description: "Renderer-aware Sutra design rules and supported fonts for page-generation tools.",
+      mimeType: "text/markdown",
+    },
+    async () => {
+      let text = BUNDLED_CAPABILITIES_MARKDOWN;
+      try {
+        const live = await client.get("/design/capabilities");
+        text = manifestToMarkdown(live.data || live);
+      } catch (_err) {
+        text += "\n\nLive capabilities could not be fetched; this bundled guidance may be stale.\n";
+      }
+
+      return {
+        contents: [
+          {
+            uri: "sutra://design/capabilities",
+            mimeType: "text/markdown",
+            text,
+          },
+        ],
+      };
+    }
+  );
+}
+
+function manifestToMarkdown(manifest) {
+  const lines = [
+    "# Sutra Design Capabilities",
+    "",
+    `Version: ${manifest.version || "unknown"}`,
+    "",
+    "## Rules",
+  ];
+
+  for (const rule of Object.values(manifest.rules || {})) lines.push(`- ${rule}`);
+  lines.push("", "## Node Types");
+  for (const [type, spec] of Object.entries(manifest.nodes || {})) {
+    lines.push(`- \`${type}\` attrs: ${(spec.attrs || []).map((attr) => `\`${attr}\``).join(", ")}`);
+  }
+  lines.push("", "## Marks");
+  for (const [type, spec] of Object.entries(manifest.marks || {})) {
+    lines.push(`- \`${type}\` attrs: ${(spec.attrs || []).map((attr) => `\`${attr}\``).join(", ")}`);
+  }
+  const fonts = manifest.fonts || {};
+  const availableFonts = fonts.available || [];
+  lines.push("", "## Fonts");
+  if (availableFonts.length > 0) {
+    for (const font of availableFonts) lines.push(`- ${font}`);
+  } else {
+    lines.push("- No font list returned by the live manifest.");
+  }
+  if (fonts.note) lines.push(`- ${fonts.note}`);
+  lines.push("", "## Anti-patterns");
+  for (const rule of manifest.anti_patterns || []) lines.push(`- ${rule}`);
+  return lines.join("\n");
+}

package/src/tools/automations.js

@@ -0,0 +1,89 @@
+import { z } from "zod";
+
+export function registerAutomationTools(server, client) {
+  server.tool(
+    "list_automations",
+    "List automations configured on a space. Returns automation IDs (auto_...), trigger type, step summary, and member counts.",
+    {
+      space_id: z.string().describe("Space ID (sp_...)"),
+      limit: z.number().optional().describe("Max results (default 25)"),
+      cursor: z.string().optional().describe("Pagination cursor"),
+    },
+    async ({ space_id, limit, cursor }) => {
+      const data = await client.get(`/spaces/${space_id}/automations`, { limit, cursor });
+      return json(data);
+    }
+  );
+
+  server.tool(
+    "get_automation",
+    "Get details for a specific automation, including its steps.",
+    {
+      automation_id: z.string().describe("Automation ID (auto_...)"),
+    },
+    async ({ automation_id }) => {
+      const data = await client.get(`/automations/${automation_id}`);
+      return json(data);
+    }
+  );
+
+  server.tool(
+    "list_automation_members",
+    "List members enrolled in an automation. Filter by status (ongoing or completed).",
+    {
+      automation_id: z.string().describe("Automation ID (auto_...)"),
+      status: z.enum(["ongoing", "completed"]).optional().describe("Filter by enrollment status"),
+      limit: z.number().optional().describe("Max results (default 25)"),
+      cursor: z.string().optional().describe("Pagination cursor"),
+    },
+    async ({ automation_id, status, limit, cursor }) => {
+      const data = await client.get(`/automations/${automation_id}/members`, { status, limit, cursor });
+      return json(data);
+    }
+  );
+
+  server.tool(
+    "get_automation_member",
+    "Get a specific member's enrollment status in an automation.",
+    {
+      automation_id: z.string().describe("Automation ID (auto_...)"),
+      enrollment_id: z.string().describe("Automation enrollment ID (aenr_...)"),
+    },
+    async ({ automation_id, enrollment_id }) => {
+      const data = await client.get(`/automations/${automation_id}/members/${enrollment_id}`);
+      return json(data);
+    }
+  );
+
+  server.tool(
+    "add_automation_member",
+    "Enroll a member in an automation. This triggers the automation flow for that member. Identify the member by member_id, user_id, or email.",
+    {
+      automation_id: z.string().describe("Automation ID (auto_...)"),
+      member_id: z.string().optional().describe("Member ID (mem_...) — member must belong to the automation's space"),
+      user_id: z.string().optional().describe("User ID (usr_...) — alternative to member_id"),
+      email: z.string().optional().describe("User email — alternative to member_id or user_id"),
+    },
+    async ({ automation_id, ...body }) => {
+      const data = await client.post(`/automations/${automation_id}/members`, body);
+      return json(data);
+    }
+  );
+
+  server.tool(
+    "remove_automation_member",
+    "Remove a member from an automation, stopping the automation flow for them.",
+    {
+      automation_id: z.string().describe("Automation ID (auto_...)"),
+      enrollment_id: z.string().describe("Automation enrollment ID (aenr_...)"),
+    },
+    async ({ automation_id, enrollment_id }) => {
+      const data = await client.delete(`/automations/${automation_id}/members/${enrollment_id}`);
+      return json(data);
+    }
+  );
+}
+
+function json(data) {
+  return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
+}