@sentientui/mcp 0.30.0 → 0.30.2

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.
@@ -606,7 +606,8 @@ function registerProjectTools(server, client) {
606
606
  text: [
607
607
  `Created project "${name}" (id: ${created.id}, type: ${resolvedContextType}).`,
608
608
  `Public key: ${created.apiKey}`,
609
- `Next: install @sentientui/react with this key. Ask me to pull the setup guide (get_integration_guide) and I'll wrap your first component.`
609
+ `Next: install @sentientui/react with this key. Ask me to pull the setup guide (get_integration_guide) and I'll wrap your first component.`,
610
+ `Once the site is deployed, its origin must be allowed (add_origin) \u2014 the first https origin is allowed automatically, once, while the project is new and has no live domain.`
610
611
  ].join("\n")
611
612
  }],
612
613
  structuredContent: {
@@ -622,7 +623,7 @@ function registerProjectTools(server, client) {
622
623
  "add_origin",
623
624
  {
624
625
  title: "Add allowed origin",
625
- description: "Allow-list a site origin (scheme + host, e.g. https://www.example.com) so the SDK's events from it are accepted. Idempotent: an origin already on the list is left as is. Removing an origin is dashboard-only. Needs an editor/admin login or the project's sk_ server key. Confirm the exact origin with the user first \u2014 an allowed origin can send events into this project.",
626
+ description: "Allow-list a site origin (scheme + host, e.g. https://www.example.com) so the SDK's events from it are accepted. Call it right after you deploy or publish a site that uses SentientUI (a ChatGPT Sites, Lovable, v0, Vercel or Netlify URL, or a custom domain): until its origin is allowed, every request from it gets 403 origin_not_allowed (the response body and a browser console warning name the refused origin) and nothing is recorded. A project in its first 14 days with no live domain yet allows its first https origin by itself, once \u2014 every later domain (www vs apex, staging, previews) needs this. Idempotent: an origin already on the list is left as is. Removing an origin is dashboard-only. Needs an editor/admin login or the project's sk_ server key. Confirm the exact origin with the user first \u2014 an allowed origin can send events into this project.",
626
627
  inputSchema: {
627
628
  projectId: projectIdSchema,
628
629
  origin: z2.string().min(1).max(500).describe("The site origin, e.g. https://www.example.com (a pasted page URL is reduced to its origin)")
@@ -3472,6 +3473,13 @@ exception is a visitor arriving on a campaign link, whose first page can already
3472
3473
  heuristic. No API key needed. Against a real project the key must be one you declared.
3473
3474
  4. To learn from real traffic: create a project at https://sentient-ui.com and set
3474
3475
  NEXT_PUBLIC_SENTIENT_API_KEY=pk_... in .env.local.
3476
+ 5. After you deploy or publish the site, allow its origin (scheme + host, e.g.
3477
+ https://my-site.lovable.app) with add_origin, or dashboard -> Settings -> Allowed domains.
3478
+ Until then every request from it is refused (403 origin_not_allowed \u2014 the JSON body names the
3479
+ origin and the fix, and the browser console shows "[sentient] Not in Allowed domains (MCP
3480
+ add_origin): <origin>") and nothing is recorded. A project under 14 days old with no live domain yet allows its
3481
+ first https origin by itself, once; each further domain (www vs apex, staging, preview deploys,
3482
+ a custom domain added later) must be added. localhost:3000/3001 are allowed from the start.
3475
3483
 
3476
3484
  ## Rung 1 \u2014 Style (CSS only)
3477
3485
 
@@ -3951,7 +3959,7 @@ function registerSiteAreasTools(server, client) {
3951
3959
  "get_site_areas",
3952
3960
  {
3953
3961
  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 }.",
3962
+ 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
3963
  inputSchema: { projectId: projectIdSchema },
3956
3964
  outputSchema: {
3957
3965
  split: z25.boolean().describe("True once the project has split its site into before and after sign-up"),
@@ -4891,7 +4899,7 @@ var TOOLS = {
4891
4899
  manage_campaigns: {
4892
4900
  title: "Manage campaigns and audiences",
4893
4901
  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
4902
+ 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
4903
  },
4896
4904
  manage_settings: {
4897
4905
  title: "Manage project settings",
@@ -4982,7 +4990,7 @@ userId must be the id the site identifies the visitor with (<AdaptiveRoot userId
4982
4990
 
4983
4991
  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
4992
 
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.
4993
+ 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
4994
 
4987
4995
  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
4996
 
@@ -4993,7 +5001,7 @@ Known people (get_known_people): a person is "known" once they have reached the
4993
5001
  Write tools change what real visitors see: confirm with the user first. Call get_agent_access before a manage_* write.`;
4994
5002
 
4995
5003
  // src/server.ts
4996
- var PKG_VERSION = true ? "0.30.0" : "0.0.0-dev";
5004
+ var PKG_VERSION = true ? "0.30.2" : "0.0.0-dev";
4997
5005
  function createMcpServer(client) {
4998
5006
  const server = new McpServer(
4999
5007
  {
package/dist/index.cjs CHANGED
@@ -334,7 +334,8 @@ function registerProjectTools(server, client) {
334
334
  text: [
335
335
  `Created project "${name}" (id: ${created.id}, type: ${resolvedContextType}).`,
336
336
  `Public key: ${created.apiKey}`,
337
- `Next: install @sentientui/react with this key. Ask me to pull the setup guide (get_integration_guide) and I'll wrap your first component.`
337
+ `Next: install @sentientui/react with this key. Ask me to pull the setup guide (get_integration_guide) and I'll wrap your first component.`,
338
+ `Once the site is deployed, its origin must be allowed (add_origin) \u2014 the first https origin is allowed automatically, once, while the project is new and has no live domain.`
338
339
  ].join("\n")
339
340
  }],
340
341
  structuredContent: {
@@ -350,7 +351,7 @@ function registerProjectTools(server, client) {
350
351
  "add_origin",
351
352
  {
352
353
  title: "Add allowed origin",
353
- description: "Allow-list a site origin (scheme + host, e.g. https://www.example.com) so the SDK's events from it are accepted. Idempotent: an origin already on the list is left as is. Removing an origin is dashboard-only. Needs an editor/admin login or the project's sk_ server key. Confirm the exact origin with the user first \u2014 an allowed origin can send events into this project.",
354
+ description: "Allow-list a site origin (scheme + host, e.g. https://www.example.com) so the SDK's events from it are accepted. Call it right after you deploy or publish a site that uses SentientUI (a ChatGPT Sites, Lovable, v0, Vercel or Netlify URL, or a custom domain): until its origin is allowed, every request from it gets 403 origin_not_allowed (the response body and a browser console warning name the refused origin) and nothing is recorded. A project in its first 14 days with no live domain yet allows its first https origin by itself, once \u2014 every later domain (www vs apex, staging, previews) needs this. Idempotent: an origin already on the list is left as is. Removing an origin is dashboard-only. Needs an editor/admin login or the project's sk_ server key. Confirm the exact origin with the user first \u2014 an allowed origin can send events into this project.",
354
355
  inputSchema: {
355
356
  projectId: projectIdSchema,
356
357
  origin: import_v32.z.string().min(1).max(500).describe("The site origin, e.g. https://www.example.com (a pasted page URL is reduced to its origin)")
@@ -3476,6 +3477,13 @@ exception is a visitor arriving on a campaign link, whose first page can already
3476
3477
  heuristic. No API key needed. Against a real project the key must be one you declared.
3477
3478
  4. To learn from real traffic: create a project at https://sentient-ui.com and set
3478
3479
  NEXT_PUBLIC_SENTIENT_API_KEY=pk_... in .env.local.
3480
+ 5. After you deploy or publish the site, allow its origin (scheme + host, e.g.
3481
+ https://my-site.lovable.app) with add_origin, or dashboard -> Settings -> Allowed domains.
3482
+ Until then every request from it is refused (403 origin_not_allowed \u2014 the JSON body names the
3483
+ origin and the fix, and the browser console shows "[sentient] Not in Allowed domains (MCP
3484
+ add_origin): <origin>") and nothing is recorded. A project under 14 days old with no live domain yet allows its
3485
+ first https origin by itself, once; each further domain (www vs apex, staging, preview deploys,
3486
+ a custom domain added later) must be added. localhost:3000/3001 are allowed from the start.
3479
3487
 
3480
3488
  ## Rung 1 \u2014 Style (CSS only)
3481
3489
 
@@ -3955,7 +3963,7 @@ function registerSiteAreasTools(server, client) {
3955
3963
  "get_site_areas",
3956
3964
  {
3957
3965
  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 }.",
3966
+ 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
3967
  inputSchema: { projectId: projectIdSchema },
3960
3968
  outputSchema: {
3961
3969
  split: import_v325.z.boolean().describe("True once the project has split its site into before and after sign-up"),
@@ -4895,7 +4903,7 @@ var TOOLS = {
4895
4903
  manage_campaigns: {
4896
4904
  title: "Manage campaigns and audiences",
4897
4905
  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
4906
+ 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
4907
  },
4900
4908
  manage_settings: {
4901
4909
  title: "Manage project settings",
@@ -4986,7 +4994,7 @@ userId must be the id the site identifies the visitor with (<AdaptiveRoot userId
4986
4994
 
4987
4995
  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
4996
 
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.
4997
+ 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
4998
 
4991
4999
  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
5000
 
@@ -4997,7 +5005,7 @@ Known people (get_known_people): a person is "known" once they have reached the
4997
5005
  Write tools change what real visitors see: confirm with the user first. Call get_agent_access before a manage_* write.`;
4998
5006
 
4999
5007
  // src/server.ts
5000
- var PKG_VERSION = true ? "0.30.0" : "0.0.0-dev";
5008
+ var PKG_VERSION = true ? "0.30.2" : "0.0.0-dev";
5001
5009
  function createMcpServer(client) {
5002
5010
  const server = new import_mcp.McpServer(
5003
5011
  {
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-5BO3KNZF.js";
6
6
 
7
7
  // src/index.ts
8
8
  import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
package/dist/lib.cjs CHANGED
@@ -360,7 +360,8 @@ function registerProjectTools(server, client) {
360
360
  text: [
361
361
  `Created project "${name}" (id: ${created.id}, type: ${resolvedContextType}).`,
362
362
  `Public key: ${created.apiKey}`,
363
- `Next: install @sentientui/react with this key. Ask me to pull the setup guide (get_integration_guide) and I'll wrap your first component.`
363
+ `Next: install @sentientui/react with this key. Ask me to pull the setup guide (get_integration_guide) and I'll wrap your first component.`,
364
+ `Once the site is deployed, its origin must be allowed (add_origin) \u2014 the first https origin is allowed automatically, once, while the project is new and has no live domain.`
364
365
  ].join("\n")
365
366
  }],
366
367
  structuredContent: {
@@ -376,7 +377,7 @@ function registerProjectTools(server, client) {
376
377
  "add_origin",
377
378
  {
378
379
  title: "Add allowed origin",
379
- description: "Allow-list a site origin (scheme + host, e.g. https://www.example.com) so the SDK's events from it are accepted. Idempotent: an origin already on the list is left as is. Removing an origin is dashboard-only. Needs an editor/admin login or the project's sk_ server key. Confirm the exact origin with the user first \u2014 an allowed origin can send events into this project.",
380
+ description: "Allow-list a site origin (scheme + host, e.g. https://www.example.com) so the SDK's events from it are accepted. Call it right after you deploy or publish a site that uses SentientUI (a ChatGPT Sites, Lovable, v0, Vercel or Netlify URL, or a custom domain): until its origin is allowed, every request from it gets 403 origin_not_allowed (the response body and a browser console warning name the refused origin) and nothing is recorded. A project in its first 14 days with no live domain yet allows its first https origin by itself, once \u2014 every later domain (www vs apex, staging, previews) needs this. Idempotent: an origin already on the list is left as is. Removing an origin is dashboard-only. Needs an editor/admin login or the project's sk_ server key. Confirm the exact origin with the user first \u2014 an allowed origin can send events into this project.",
380
381
  inputSchema: {
381
382
  projectId: projectIdSchema,
382
383
  origin: import_v32.z.string().min(1).max(500).describe("The site origin, e.g. https://www.example.com (a pasted page URL is reduced to its origin)")
@@ -3502,6 +3503,13 @@ exception is a visitor arriving on a campaign link, whose first page can already
3502
3503
  heuristic. No API key needed. Against a real project the key must be one you declared.
3503
3504
  4. To learn from real traffic: create a project at https://sentient-ui.com and set
3504
3505
  NEXT_PUBLIC_SENTIENT_API_KEY=pk_... in .env.local.
3506
+ 5. After you deploy or publish the site, allow its origin (scheme + host, e.g.
3507
+ https://my-site.lovable.app) with add_origin, or dashboard -> Settings -> Allowed domains.
3508
+ Until then every request from it is refused (403 origin_not_allowed \u2014 the JSON body names the
3509
+ origin and the fix, and the browser console shows "[sentient] Not in Allowed domains (MCP
3510
+ add_origin): <origin>") and nothing is recorded. A project under 14 days old with no live domain yet allows its
3511
+ first https origin by itself, once; each further domain (www vs apex, staging, preview deploys,
3512
+ a custom domain added later) must be added. localhost:3000/3001 are allowed from the start.
3505
3513
 
3506
3514
  ## Rung 1 \u2014 Style (CSS only)
3507
3515
 
@@ -3981,7 +3989,7 @@ function registerSiteAreasTools(server, client) {
3981
3989
  "get_site_areas",
3982
3990
  {
3983
3991
  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 }.",
3992
+ 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
3993
  inputSchema: { projectId: projectIdSchema },
3986
3994
  outputSchema: {
3987
3995
  split: import_v325.z.boolean().describe("True once the project has split its site into before and after sign-up"),
@@ -4921,7 +4929,7 @@ var TOOLS = {
4921
4929
  manage_campaigns: {
4922
4930
  title: "Manage campaigns and audiences",
4923
4931
  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
4932
+ 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
4933
  },
4926
4934
  manage_settings: {
4927
4935
  title: "Manage project settings",
@@ -5012,7 +5020,7 @@ userId must be the id the site identifies the visitor with (<AdaptiveRoot userId
5012
5020
 
5013
5021
  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
5022
 
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.
5023
+ 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
5024
 
5017
5025
  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
5026
 
@@ -5023,7 +5031,7 @@ Known people (get_known_people): a person is "known" once they have reached the
5023
5031
  Write tools change what real visitors see: confirm with the user first. Call get_agent_access before a manage_* write.`;
5024
5032
 
5025
5033
  // src/server.ts
5026
- var PKG_VERSION = true ? "0.30.0" : "0.0.0-dev";
5034
+ var PKG_VERSION = true ? "0.30.2" : "0.0.0-dev";
5027
5035
  function createMcpServer(client) {
5028
5036
  const server = new import_mcp.McpServer(
5029
5037
  {
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-5BO3KNZF.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.2",
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",