@sentientui/mcp 0.30.0 → 0.30.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -3951,7 +3951,7 @@ function registerSiteAreasTools(server, client) {
3951
3951
  "get_site_areas",
3952
3952
  {
3953
3953
  title: "Site areas (before and after sign-up)",
3954
- description: "Read which parts of the site are before sign-up (anonymous visitors; the main goal is to convert them: a sign-up, a sale, a form) and which are after sign-up (inside the product, where the site knows who its users are) \u2014 dashboard Settings \u2192 Site areas. Each area is an allowed site, optionally narrowed to a path; a page no area covers is before sign-up. A component gets versions only for audiences of its own side: campaign, arrival and retargeting audiences are before sign-up, declared personas after (unless declared for before), discovered groups wherever their visits happen. An empty list means the site is not split and nothing is restricted. Also lists every allowed site with how many visitors were signed in (30 days) and a suggested side. To change: manage_settings set_site_areas; a declared persona's side: manage_campaigns update_audience with { side }.",
3954
+ description: "Read which parts of the site are before sign-up (anonymous visitors; the main goal is to convert them: a sign-up, a sale, a form) and which are after sign-up (inside the product, where the site knows who its users are) \u2014 dashboard Settings \u2192 Site areas. Each area is an allowed site, optionally narrowed to a path; a page no area covers is before sign-up. A component gets versions only for audiences of its own side, and serving follows the same line: campaign, arrival and retargeting audiences are before sign-up; declared personas are after sign-up only (they are people already using the product, so they never count toward winning new ones); discovered groups wherever their visits happen. An empty list means the site is not split and nothing is restricted. Also lists every allowed site with how many visitors were signed in (30 days) and a suggested side. To change: manage_settings set_site_areas.",
3955
3955
  inputSchema: { projectId: projectIdSchema },
3956
3956
  outputSchema: {
3957
3957
  split: z25.boolean().describe("True once the project has split its site into before and after sign-up"),
@@ -4891,7 +4891,7 @@ var TOOLS = {
4891
4891
  manage_campaigns: {
4892
4892
  title: "Manage campaigns and audiences",
4893
4893
  destructive: true,
4894
- description: 'Manage campaigns, retargeting and audiences: create, update or tag campaigns, start retargeting and change its group, declare or edit audiences, promote or roll back the discovered audiences, promote labels, and set the shopping-stage settings, search categories and stage serving. Promote and roll back change who sees what. A declared audience carries a side of sign-up (declare_audiences / update_audience with side "before" or "after"; default after \u2014 see get_site_areas). Pick one `action`; pass the ids it needs.' + REFUSAL_NOTE
4894
+ description: "Manage campaigns, retargeting and audiences: create, update or tag campaigns, start retargeting and change its group, declare or edit audiences, promote or roll back the discovered audiences, promote labels, and set the shopping-stage settings, search categories and stage serving. Promote and roll back change who sees what. A declared audience is after sign-up only (see get_site_areas). Pick one `action`; pass the ids it needs." + REFUSAL_NOTE
4895
4895
  },
4896
4896
  manage_settings: {
4897
4897
  title: "Manage project settings",
@@ -4982,7 +4982,7 @@ userId must be the id the site identifies the visitor with (<AdaptiveRoot userId
4982
4982
 
4983
4983
  Excluding the team and test sites (dashboard Settings -> Internal traffic): visits marked internal still see versions (QA works) but never count in any report and never teach the optimizer; get_traffic_breakdown lists them as "Your team / test sites". They are marked by internal sites (allowed domains such as staging or localhost), team emails and domains (they match visitors the site identifies with identify(userId, { email }); the SDK sends only a SHA-256 of the address and its domain, never the address), a browser link, or the code flag (the internal prop on <AdaptiveRoot>/<AdaptiveProvider>, init({ internal }), window.sentient.internal). There is no report filter or IP rule, and visits from before a rule was turned on cannot be separated. Read the rules with get_internal_traffic_rules; change them with manage_settings set_internal_sites / add_internal_email / remove_internal_email (Agent access: Project settings), after confirming the list with the user.
4984
4984
 
4985
- Two sides of sign-up (dashboard Settings -> Site areas; read with get_site_areas): before sign-up the visitor is anonymous and the goal is to convert them; after sign-up the visitor is inside the product and known. Once a project splits its site, a component gets versions only for audiences of its own side: campaign, arrival and retargeting audiences are before sign-up, declared personas after (unless declared for before), discovered groups wherever their visits happen. A version, pin or approval across the line is refused (error other_side) \u2014 pick an audience of the component's side instead of retrying.
4985
+ Two sides of sign-up (dashboard Settings -> Site areas; read with get_site_areas): before sign-up the visitor is anonymous and the goal is to convert them; after sign-up the visitor is inside the product and known. Once a project splits its site, a component gets versions only for audiences of its own side: campaign, arrival and retargeting audiences are before sign-up, declared personas after sign-up only (people already using the product never count toward winning new ones), discovered groups wherever their visits happen. Serving follows the same line: on a before-sign-up page a declared persona is never in force (that visitor is Everyone or a campaign). A version, pin or approval across the line is refused (error other_side) \u2014 pick an audience of the component's side instead of retrying.
4986
4986
 
4987
4987
  The main funnel (get_main_funnel): "how is my funnel doing" is answered by the one journey that ends at the project's main goal \u2014 Arrived, the marketer's own steps, the main goal \u2014 counted in people, with those who had already converted left out. It is chosen with manage_goals set_main_funnel and must end at the main goal; with none chosen it is just Arrived -> main goal. Stores get their checkout journey as the main funnel on connect. Use get_funnel_report only for a side journey: it counts one funnel's goals inside a window and includes people who had already converted, so its numbers and the main funnel's do not add up.
4988
4988
 
@@ -4993,7 +4993,7 @@ Known people (get_known_people): a person is "known" once they have reached the
4993
4993
  Write tools change what real visitors see: confirm with the user first. Call get_agent_access before a manage_* write.`;
4994
4994
 
4995
4995
  // src/server.ts
4996
- var PKG_VERSION = true ? "0.30.0" : "0.0.0-dev";
4996
+ var PKG_VERSION = true ? "0.30.1" : "0.0.0-dev";
4997
4997
  function createMcpServer(client) {
4998
4998
  const server = new McpServer(
4999
4999
  {
package/dist/index.cjs CHANGED
@@ -3955,7 +3955,7 @@ function registerSiteAreasTools(server, client) {
3955
3955
  "get_site_areas",
3956
3956
  {
3957
3957
  title: "Site areas (before and after sign-up)",
3958
- description: "Read which parts of the site are before sign-up (anonymous visitors; the main goal is to convert them: a sign-up, a sale, a form) and which are after sign-up (inside the product, where the site knows who its users are) \u2014 dashboard Settings \u2192 Site areas. Each area is an allowed site, optionally narrowed to a path; a page no area covers is before sign-up. A component gets versions only for audiences of its own side: campaign, arrival and retargeting audiences are before sign-up, declared personas after (unless declared for before), discovered groups wherever their visits happen. An empty list means the site is not split and nothing is restricted. Also lists every allowed site with how many visitors were signed in (30 days) and a suggested side. To change: manage_settings set_site_areas; a declared persona's side: manage_campaigns update_audience with { side }.",
3958
+ description: "Read which parts of the site are before sign-up (anonymous visitors; the main goal is to convert them: a sign-up, a sale, a form) and which are after sign-up (inside the product, where the site knows who its users are) \u2014 dashboard Settings \u2192 Site areas. Each area is an allowed site, optionally narrowed to a path; a page no area covers is before sign-up. A component gets versions only for audiences of its own side, and serving follows the same line: campaign, arrival and retargeting audiences are before sign-up; declared personas are after sign-up only (they are people already using the product, so they never count toward winning new ones); discovered groups wherever their visits happen. An empty list means the site is not split and nothing is restricted. Also lists every allowed site with how many visitors were signed in (30 days) and a suggested side. To change: manage_settings set_site_areas.",
3959
3959
  inputSchema: { projectId: projectIdSchema },
3960
3960
  outputSchema: {
3961
3961
  split: import_v325.z.boolean().describe("True once the project has split its site into before and after sign-up"),
@@ -4895,7 +4895,7 @@ var TOOLS = {
4895
4895
  manage_campaigns: {
4896
4896
  title: "Manage campaigns and audiences",
4897
4897
  destructive: true,
4898
- description: 'Manage campaigns, retargeting and audiences: create, update or tag campaigns, start retargeting and change its group, declare or edit audiences, promote or roll back the discovered audiences, promote labels, and set the shopping-stage settings, search categories and stage serving. Promote and roll back change who sees what. A declared audience carries a side of sign-up (declare_audiences / update_audience with side "before" or "after"; default after \u2014 see get_site_areas). Pick one `action`; pass the ids it needs.' + REFUSAL_NOTE
4898
+ description: "Manage campaigns, retargeting and audiences: create, update or tag campaigns, start retargeting and change its group, declare or edit audiences, promote or roll back the discovered audiences, promote labels, and set the shopping-stage settings, search categories and stage serving. Promote and roll back change who sees what. A declared audience is after sign-up only (see get_site_areas). Pick one `action`; pass the ids it needs." + REFUSAL_NOTE
4899
4899
  },
4900
4900
  manage_settings: {
4901
4901
  title: "Manage project settings",
@@ -4986,7 +4986,7 @@ userId must be the id the site identifies the visitor with (<AdaptiveRoot userId
4986
4986
 
4987
4987
  Excluding the team and test sites (dashboard Settings -> Internal traffic): visits marked internal still see versions (QA works) but never count in any report and never teach the optimizer; get_traffic_breakdown lists them as "Your team / test sites". They are marked by internal sites (allowed domains such as staging or localhost), team emails and domains (they match visitors the site identifies with identify(userId, { email }); the SDK sends only a SHA-256 of the address and its domain, never the address), a browser link, or the code flag (the internal prop on <AdaptiveRoot>/<AdaptiveProvider>, init({ internal }), window.sentient.internal). There is no report filter or IP rule, and visits from before a rule was turned on cannot be separated. Read the rules with get_internal_traffic_rules; change them with manage_settings set_internal_sites / add_internal_email / remove_internal_email (Agent access: Project settings), after confirming the list with the user.
4988
4988
 
4989
- Two sides of sign-up (dashboard Settings -> Site areas; read with get_site_areas): before sign-up the visitor is anonymous and the goal is to convert them; after sign-up the visitor is inside the product and known. Once a project splits its site, a component gets versions only for audiences of its own side: campaign, arrival and retargeting audiences are before sign-up, declared personas after (unless declared for before), discovered groups wherever their visits happen. A version, pin or approval across the line is refused (error other_side) \u2014 pick an audience of the component's side instead of retrying.
4989
+ Two sides of sign-up (dashboard Settings -> Site areas; read with get_site_areas): before sign-up the visitor is anonymous and the goal is to convert them; after sign-up the visitor is inside the product and known. Once a project splits its site, a component gets versions only for audiences of its own side: campaign, arrival and retargeting audiences are before sign-up, declared personas after sign-up only (people already using the product never count toward winning new ones), discovered groups wherever their visits happen. Serving follows the same line: on a before-sign-up page a declared persona is never in force (that visitor is Everyone or a campaign). A version, pin or approval across the line is refused (error other_side) \u2014 pick an audience of the component's side instead of retrying.
4990
4990
 
4991
4991
  The main funnel (get_main_funnel): "how is my funnel doing" is answered by the one journey that ends at the project's main goal \u2014 Arrived, the marketer's own steps, the main goal \u2014 counted in people, with those who had already converted left out. It is chosen with manage_goals set_main_funnel and must end at the main goal; with none chosen it is just Arrived -> main goal. Stores get their checkout journey as the main funnel on connect. Use get_funnel_report only for a side journey: it counts one funnel's goals inside a window and includes people who had already converted, so its numbers and the main funnel's do not add up.
4992
4992
 
@@ -4997,7 +4997,7 @@ Known people (get_known_people): a person is "known" once they have reached the
4997
4997
  Write tools change what real visitors see: confirm with the user first. Call get_agent_access before a manage_* write.`;
4998
4998
 
4999
4999
  // src/server.ts
5000
- var PKG_VERSION = true ? "0.30.0" : "0.0.0-dev";
5000
+ var PKG_VERSION = true ? "0.30.1" : "0.0.0-dev";
5001
5001
  function createMcpServer(client) {
5002
5002
  const server = new import_mcp.McpServer(
5003
5003
  {
package/dist/index.js CHANGED
@@ -2,7 +2,7 @@
2
2
  import {
3
3
  ApiClient,
4
4
  createMcpServer
5
- } from "./chunk-RXCALHF6.js";
5
+ } from "./chunk-OTJE277E.js";
6
6
 
7
7
  // src/index.ts
8
8
  import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
package/dist/lib.cjs CHANGED
@@ -3981,7 +3981,7 @@ function registerSiteAreasTools(server, client) {
3981
3981
  "get_site_areas",
3982
3982
  {
3983
3983
  title: "Site areas (before and after sign-up)",
3984
- description: "Read which parts of the site are before sign-up (anonymous visitors; the main goal is to convert them: a sign-up, a sale, a form) and which are after sign-up (inside the product, where the site knows who its users are) \u2014 dashboard Settings \u2192 Site areas. Each area is an allowed site, optionally narrowed to a path; a page no area covers is before sign-up. A component gets versions only for audiences of its own side: campaign, arrival and retargeting audiences are before sign-up, declared personas after (unless declared for before), discovered groups wherever their visits happen. An empty list means the site is not split and nothing is restricted. Also lists every allowed site with how many visitors were signed in (30 days) and a suggested side. To change: manage_settings set_site_areas; a declared persona's side: manage_campaigns update_audience with { side }.",
3984
+ description: "Read which parts of the site are before sign-up (anonymous visitors; the main goal is to convert them: a sign-up, a sale, a form) and which are after sign-up (inside the product, where the site knows who its users are) \u2014 dashboard Settings \u2192 Site areas. Each area is an allowed site, optionally narrowed to a path; a page no area covers is before sign-up. A component gets versions only for audiences of its own side, and serving follows the same line: campaign, arrival and retargeting audiences are before sign-up; declared personas are after sign-up only (they are people already using the product, so they never count toward winning new ones); discovered groups wherever their visits happen. An empty list means the site is not split and nothing is restricted. Also lists every allowed site with how many visitors were signed in (30 days) and a suggested side. To change: manage_settings set_site_areas.",
3985
3985
  inputSchema: { projectId: projectIdSchema },
3986
3986
  outputSchema: {
3987
3987
  split: import_v325.z.boolean().describe("True once the project has split its site into before and after sign-up"),
@@ -4921,7 +4921,7 @@ var TOOLS = {
4921
4921
  manage_campaigns: {
4922
4922
  title: "Manage campaigns and audiences",
4923
4923
  destructive: true,
4924
- description: 'Manage campaigns, retargeting and audiences: create, update or tag campaigns, start retargeting and change its group, declare or edit audiences, promote or roll back the discovered audiences, promote labels, and set the shopping-stage settings, search categories and stage serving. Promote and roll back change who sees what. A declared audience carries a side of sign-up (declare_audiences / update_audience with side "before" or "after"; default after \u2014 see get_site_areas). Pick one `action`; pass the ids it needs.' + REFUSAL_NOTE
4924
+ description: "Manage campaigns, retargeting and audiences: create, update or tag campaigns, start retargeting and change its group, declare or edit audiences, promote or roll back the discovered audiences, promote labels, and set the shopping-stage settings, search categories and stage serving. Promote and roll back change who sees what. A declared audience is after sign-up only (see get_site_areas). Pick one `action`; pass the ids it needs." + REFUSAL_NOTE
4925
4925
  },
4926
4926
  manage_settings: {
4927
4927
  title: "Manage project settings",
@@ -5012,7 +5012,7 @@ userId must be the id the site identifies the visitor with (<AdaptiveRoot userId
5012
5012
 
5013
5013
  Excluding the team and test sites (dashboard Settings -> Internal traffic): visits marked internal still see versions (QA works) but never count in any report and never teach the optimizer; get_traffic_breakdown lists them as "Your team / test sites". They are marked by internal sites (allowed domains such as staging or localhost), team emails and domains (they match visitors the site identifies with identify(userId, { email }); the SDK sends only a SHA-256 of the address and its domain, never the address), a browser link, or the code flag (the internal prop on <AdaptiveRoot>/<AdaptiveProvider>, init({ internal }), window.sentient.internal). There is no report filter or IP rule, and visits from before a rule was turned on cannot be separated. Read the rules with get_internal_traffic_rules; change them with manage_settings set_internal_sites / add_internal_email / remove_internal_email (Agent access: Project settings), after confirming the list with the user.
5014
5014
 
5015
- Two sides of sign-up (dashboard Settings -> Site areas; read with get_site_areas): before sign-up the visitor is anonymous and the goal is to convert them; after sign-up the visitor is inside the product and known. Once a project splits its site, a component gets versions only for audiences of its own side: campaign, arrival and retargeting audiences are before sign-up, declared personas after (unless declared for before), discovered groups wherever their visits happen. A version, pin or approval across the line is refused (error other_side) \u2014 pick an audience of the component's side instead of retrying.
5015
+ Two sides of sign-up (dashboard Settings -> Site areas; read with get_site_areas): before sign-up the visitor is anonymous and the goal is to convert them; after sign-up the visitor is inside the product and known. Once a project splits its site, a component gets versions only for audiences of its own side: campaign, arrival and retargeting audiences are before sign-up, declared personas after sign-up only (people already using the product never count toward winning new ones), discovered groups wherever their visits happen. Serving follows the same line: on a before-sign-up page a declared persona is never in force (that visitor is Everyone or a campaign). A version, pin or approval across the line is refused (error other_side) \u2014 pick an audience of the component's side instead of retrying.
5016
5016
 
5017
5017
  The main funnel (get_main_funnel): "how is my funnel doing" is answered by the one journey that ends at the project's main goal \u2014 Arrived, the marketer's own steps, the main goal \u2014 counted in people, with those who had already converted left out. It is chosen with manage_goals set_main_funnel and must end at the main goal; with none chosen it is just Arrived -> main goal. Stores get their checkout journey as the main funnel on connect. Use get_funnel_report only for a side journey: it counts one funnel's goals inside a window and includes people who had already converted, so its numbers and the main funnel's do not add up.
5018
5018
 
@@ -5023,7 +5023,7 @@ Known people (get_known_people): a person is "known" once they have reached the
5023
5023
  Write tools change what real visitors see: confirm with the user first. Call get_agent_access before a manage_* write.`;
5024
5024
 
5025
5025
  // src/server.ts
5026
- var PKG_VERSION = true ? "0.30.0" : "0.0.0-dev";
5026
+ var PKG_VERSION = true ? "0.30.1" : "0.0.0-dev";
5027
5027
  function createMcpServer(client) {
5028
5028
  const server = new import_mcp.McpServer(
5029
5029
  {
package/dist/lib.js CHANGED
@@ -4,7 +4,7 @@ import {
4
4
  ApiError,
5
5
  PUBLIC_UI_RESOURCE_URIS,
6
6
  createMcpServer
7
- } from "./chunk-RXCALHF6.js";
7
+ } from "./chunk-OTJE277E.js";
8
8
 
9
9
  // src/tool-catalog.ts
10
10
  var TOOL_CATALOG = [
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sentientui/mcp",
3
- "version": "0.30.0",
3
+ "version": "0.30.1",
4
4
  "description": "MCP server for SentientUI — exposes project data and actions to AI agents",
5
5
  "license": "MIT",
6
6
  "homepage": "https://sentient-ui.com",