@sentientui/mcp 0.24.0 → 0.24.1

package/dist/{chunk-V3A552VK.js → chunk-G6WGJ7A5.js}

@@ -1904,7 +1904,7 @@ function registerVariantWriteTools(server, client) {
     "create_variant",
     {
       title: "Create managed variant",
-      description: "Create a NO-CODE managed text variant for a component (content stored in SentientUI, rendered by <AdaptiveText>). Use this ONLY for text-only variants the user wants without a code change. For variants that will live in the codebase (full components \u2014 copy, markup, styling), use get_variant_brief and write the variant in code instead; those auto-register on deploy and do not need create_variant. Works on every plan with an editor/admin login or the project's sk_ server key (anonymous demo tokens are read-only). The variant is created as a DRAFT \u2014 it serves no traffic until activated with update_variant (status 'active'). Confirm the text with the user before calling.",
+      description: "Create a NO-CODE managed text variant for a component (content stored in SentientUI, rendered by <AdaptiveText>). Use this ONLY for text-only variants the user wants without a code change. For variants that will live in the codebase (full components \u2014 copy, markup, styling), use get_variant_brief and write the variant in code instead; those auto-register on deploy and do not need create_variant. Works on every plan with an editor/admin login or the project's sk_ server key (anonymous demo tokens are read-only). The variant is created as a DRAFT \u2014 it serves no traffic until activated with update_variant (status 'active'). Confirm the text with the user before calling. On a component that has moved to the shared track, the text is added to the component's versions instead (still a draft until activated), and text is required there (an empty create is refused); the call and its result are otherwise the same.",
       inputSchema: {
         projectId: projectIdSchema,
         componentId: z11.string().min(1).max(200).describe("The component ID to add a variant to"),
@@ -2023,7 +2023,7 @@ function registerVariantWriteTools(server, client) {
     "update_variant",
     {
       title: "Update managed variant",
-      description: "Edit a NO-CODE managed variant (one created with create_variant or in the dashboard): its display name, its text, or its status \u2014 'active' starts serving it to visitors, 'draft' takes it back out of rotation. Code-native variants cannot be edited here (change the code). Overwriting text or activating changes what live visitors see, so CONFIRM with the user first. Omit a field to leave it unchanged.",
+      description: "Edit a NO-CODE managed variant (one created with create_variant or in the dashboard): its display name, its text, or its status \u2014 'active' starts serving it to visitors, 'draft' takes it back out of rotation. Code-native variants cannot be edited here (change the code). Overwriting text or activating changes what live visitors see, so CONFIRM with the user first. Omit a field to leave it unchanged. On a component that has moved to the shared track (one experiment with its versions), the text is edited on that component's version instead; the call and its result are the same.",
       inputSchema: {
         projectId: projectIdSchema,
         componentId: z11.string().min(1).max(200).describe("The component ID"),
@@ -3190,7 +3190,7 @@ function registerCellTools(server, client) {
 }
 
 // src/server.ts
-var PKG_VERSION = true ? "0.24.0" : "0.0.0-dev";
+var PKG_VERSION = true ? "0.24.1" : "0.0.0-dev";
 function createMcpServer(client) {
   const server = new McpServer(
     {

package/dist/index.cjs

@@ -1908,7 +1908,7 @@ function registerVariantWriteTools(server, client) {
     "create_variant",
     {
       title: "Create managed variant",
-      description: "Create a NO-CODE managed text variant for a component (content stored in SentientUI, rendered by <AdaptiveText>). Use this ONLY for text-only variants the user wants without a code change. For variants that will live in the codebase (full components \u2014 copy, markup, styling), use get_variant_brief and write the variant in code instead; those auto-register on deploy and do not need create_variant. Works on every plan with an editor/admin login or the project's sk_ server key (anonymous demo tokens are read-only). The variant is created as a DRAFT \u2014 it serves no traffic until activated with update_variant (status 'active'). Confirm the text with the user before calling.",
+      description: "Create a NO-CODE managed text variant for a component (content stored in SentientUI, rendered by <AdaptiveText>). Use this ONLY for text-only variants the user wants without a code change. For variants that will live in the codebase (full components \u2014 copy, markup, styling), use get_variant_brief and write the variant in code instead; those auto-register on deploy and do not need create_variant. Works on every plan with an editor/admin login or the project's sk_ server key (anonymous demo tokens are read-only). The variant is created as a DRAFT \u2014 it serves no traffic until activated with update_variant (status 'active'). Confirm the text with the user before calling. On a component that has moved to the shared track, the text is added to the component's versions instead (still a draft until activated), and text is required there (an empty create is refused); the call and its result are otherwise the same.",
       inputSchema: {
         projectId: projectIdSchema,
         componentId: import_zod11.z.string().min(1).max(200).describe("The component ID to add a variant to"),
@@ -2027,7 +2027,7 @@ function registerVariantWriteTools(server, client) {
     "update_variant",
     {
       title: "Update managed variant",
-      description: "Edit a NO-CODE managed variant (one created with create_variant or in the dashboard): its display name, its text, or its status \u2014 'active' starts serving it to visitors, 'draft' takes it back out of rotation. Code-native variants cannot be edited here (change the code). Overwriting text or activating changes what live visitors see, so CONFIRM with the user first. Omit a field to leave it unchanged.",
+      description: "Edit a NO-CODE managed variant (one created with create_variant or in the dashboard): its display name, its text, or its status \u2014 'active' starts serving it to visitors, 'draft' takes it back out of rotation. Code-native variants cannot be edited here (change the code). Overwriting text or activating changes what live visitors see, so CONFIRM with the user first. Omit a field to leave it unchanged. On a component that has moved to the shared track (one experiment with its versions), the text is edited on that component's version instead; the call and its result are the same.",
       inputSchema: {
         projectId: projectIdSchema,
         componentId: import_zod11.z.string().min(1).max(200).describe("The component ID"),
@@ -3194,7 +3194,7 @@ function registerCellTools(server, client) {
 }
 
 // src/server.ts
-var PKG_VERSION = true ? "0.24.0" : "0.0.0-dev";
+var PKG_VERSION = true ? "0.24.1" : "0.0.0-dev";
 function createMcpServer(client) {
   const server = new import_mcp.McpServer(
     {

package/dist/index.js

@@ -2,7 +2,7 @@
 import {
   ApiClient,
   createMcpServer
-} from "./chunk-V3A552VK.js";
+} from "./chunk-G6WGJ7A5.js";
 
 // src/index.ts
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";

package/dist/lib.cjs

@@ -1934,7 +1934,7 @@ function registerVariantWriteTools(server, client) {
     "create_variant",
     {
       title: "Create managed variant",
-      description: "Create a NO-CODE managed text variant for a component (content stored in SentientUI, rendered by <AdaptiveText>). Use this ONLY for text-only variants the user wants without a code change. For variants that will live in the codebase (full components \u2014 copy, markup, styling), use get_variant_brief and write the variant in code instead; those auto-register on deploy and do not need create_variant. Works on every plan with an editor/admin login or the project's sk_ server key (anonymous demo tokens are read-only). The variant is created as a DRAFT \u2014 it serves no traffic until activated with update_variant (status 'active'). Confirm the text with the user before calling.",
+      description: "Create a NO-CODE managed text variant for a component (content stored in SentientUI, rendered by <AdaptiveText>). Use this ONLY for text-only variants the user wants without a code change. For variants that will live in the codebase (full components \u2014 copy, markup, styling), use get_variant_brief and write the variant in code instead; those auto-register on deploy and do not need create_variant. Works on every plan with an editor/admin login or the project's sk_ server key (anonymous demo tokens are read-only). The variant is created as a DRAFT \u2014 it serves no traffic until activated with update_variant (status 'active'). Confirm the text with the user before calling. On a component that has moved to the shared track, the text is added to the component's versions instead (still a draft until activated), and text is required there (an empty create is refused); the call and its result are otherwise the same.",
       inputSchema: {
         projectId: projectIdSchema,
         componentId: import_zod11.z.string().min(1).max(200).describe("The component ID to add a variant to"),
@@ -2053,7 +2053,7 @@ function registerVariantWriteTools(server, client) {
     "update_variant",
     {
       title: "Update managed variant",
-      description: "Edit a NO-CODE managed variant (one created with create_variant or in the dashboard): its display name, its text, or its status \u2014 'active' starts serving it to visitors, 'draft' takes it back out of rotation. Code-native variants cannot be edited here (change the code). Overwriting text or activating changes what live visitors see, so CONFIRM with the user first. Omit a field to leave it unchanged.",
+      description: "Edit a NO-CODE managed variant (one created with create_variant or in the dashboard): its display name, its text, or its status \u2014 'active' starts serving it to visitors, 'draft' takes it back out of rotation. Code-native variants cannot be edited here (change the code). Overwriting text or activating changes what live visitors see, so CONFIRM with the user first. Omit a field to leave it unchanged. On a component that has moved to the shared track (one experiment with its versions), the text is edited on that component's version instead; the call and its result are the same.",
       inputSchema: {
         projectId: projectIdSchema,
         componentId: import_zod11.z.string().min(1).max(200).describe("The component ID"),
@@ -3220,7 +3220,7 @@ function registerCellTools(server, client) {
 }
 
 // src/server.ts
-var PKG_VERSION = true ? "0.24.0" : "0.0.0-dev";
+var PKG_VERSION = true ? "0.24.1" : "0.0.0-dev";
 function createMcpServer(client) {
   const server = new import_mcp.McpServer(
     {

package/dist/lib.js

@@ -4,7 +4,7 @@ import {
   ApiError,
   PUBLIC_UI_RESOURCE_URIS,
   createMcpServer
-} from "./chunk-V3A552VK.js";
+} from "./chunk-G6WGJ7A5.js";
 
 // src/tool-catalog.ts
 var TOOL_CATALOG = [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sentientui/mcp",
-  "version": "0.24.0",
+  "version": "0.24.1",
   "description": "MCP server for SentientUI — exposes project data and actions to AI agents",
   "license": "MIT",
   "homepage": "https://sentient-ui.com",