picked 0.0.107-next.1 → 0.0.107-next.2

package/docs/how-to/point-one-entry-at-another.md

@@ -64,9 +64,7 @@ You can also do this task with the [Management API](/reference/management-api/sc
 | Add a Reference field | [`contentModelUpdate`](/reference/management-api/schema/cms-models#contentmodelupdate) | [`update_content_model`](/reference/tools/mcp#update_content_model) | `tools.update_content_model({ content_model_id, schema })` |
 | Find the target entry | [`contentEntries`](/reference/management-api/schema/cms-models#contententries) | [`list_content_entries`](/reference/tools/mcp#list_content_entries) | `tools.list_content_entries({ workspace_id, content_model_id })` |
 | Choose a target on an entry | [`contentEntryUpdate`](/reference/management-api/schema/cms-models#contententryupdate) | [`update_content_entry`](/reference/tools/mcp#update_content_entry) | `tools.update_content_entry({ content_entry_id, data })` |
-| Delete a target | [`contentEntryDelete`](/reference/management-api/schema/cms-models#contententrydelete) | [`guide_delete_content_entry`](/reference/tools/mcp#guide_delete_content_entry) | `tools.guide_delete_content_entry({ content_entry_id })` |
-
-The MCP server does not delete an entry. `guide_delete_content_entry` gives the link to the entry in the dashboard, where you delete it.
+| Delete a target | [`contentEntryDelete`](/reference/management-api/schema/cms-models#contententrydelete) | [`delete_content_entry`](/reference/tools/mcp#delete_content_entry) | `tools.delete_content_entry({ content_entry_id })` |
 
 ## Related
 

package/docs/reference/dashboard/content/content-entries.mdx

@@ -95,9 +95,7 @@ You can also do this task with the [Management API](/reference/management-api/sc
 | Bind an entry to a page or a step | [`stepUpdate`](/reference/management-api/schema/step#stepupdate) | [`update_step`](/reference/tools/mcp#update_step) | `tools.update_step({ step_id, layout_content_entry_id })` |
 | Edit the entry data | [`contentEntryUpdate`](/reference/management-api/schema/cms-models#contententryupdate) | [`update_content_entry`](/reference/tools/mcp#update_content_entry) | `tools.update_content_entry({ content_entry_id, data })` |
 | Find the entries that are not valid | [`workspaceContentEntryValidation`](/reference/management-api/schema/cms-models#workspacecontententryvalidation) | [`validate_workspace_content_entries`](/reference/tools/mcp#validate_workspace_content_entries) | `tools.validate_workspace_content_entries({ workspace_id })` |
-| Delete an entry | [`contentEntryDelete`](/reference/management-api/schema/cms-models#contententrydelete) | [`guide_delete_content_entry`](/reference/tools/mcp#guide_delete_content_entry) | `tools.guide_delete_content_entry({ content_entry_id })` |
-
-The MCP server does not delete an entry. `guide_delete_content_entry` gives the link to the entry in the dashboard, where you delete it.
+| Delete an entry | [`contentEntryDelete`](/reference/management-api/schema/cms-models#contententrydelete) | [`delete_content_entry`](/reference/tools/mcp#delete_content_entry) | `tools.delete_content_entry({ content_entry_id })` |
 
 ## Related
 

package/docs/reference/dashboard/lead-search.md

@@ -21,7 +21,7 @@ so you can share the link.
 | The visitor | `userId` | `userId:sess_7x2k9q3m1n4a` |
 | The visit that captured the lead | `session.field` | `session.utm_source:google` |
 
-A path of two parts is a label, unless it starts with `session.`: that path reads the visit.
+A path of two parts is a label, unless it starts with `session.`: that path reads the visit. A `session.` path needs `ORGANIZATION_SESSIONS_READ`.
 A label namespace and a label key cannot contain a full stop. A path of one part is the key
 of a field, unless the name is `createdAt` or `userId`.
 

package/docs/reference/dashboard/leads.md

@@ -102,6 +102,7 @@ On a narrow screen, the page shows the cards on three tabs.
 | Surface                | Scopes                                                                                                       |
 | ---------------------- | ------------------------------------------------------------------------------------------------------------ |
 | Leads, Lead            | `ORGANIZATION_LEADS_READ`                                                                                    |
+| **Session** columns, **Session** card, report tabs | `ORGANIZATION_SESSIONS_READ`                                                     |
 | Saved views            | `ORGANIZATION_PROJECTS_READ` to see them, and `ORGANIZATION_PROJECTS_UPDATE` to save, change and delete them |
 | The labels of a lead   | Refer to [Owners](/reference/dashboard/labels#owners).                                                       |
 | **Workflow runs** card | Refer to [Access](/reference/dashboard/workflow-runs#access).                                                |

package/docs/reference/management-api/authorization-and-scopes.md

@@ -68,7 +68,7 @@ These are the scopes:
 | `organization_projects/delete` | `ORGANIZATION_PROJECTS_DELETE` | Delete a project                 |
 
 A scope on content inside a project also gives `organization_projects/read`. The
-workspace, integration, lead, action run, and report scopes all give it. They do
+workspace, integration, lead, session, action run, and report scopes all give it. They do
 not give `organization_projects/create`, `organization_projects/update`, or
 `organization_projects/delete`.
 
@@ -98,6 +98,18 @@ not give `organization_projects/create`, `organization_projects/update`, or
 | `organization_reports/update` | `ORGANIZATION_REPORTS_UPDATE` | Update the settings of a report |
 | `organization_reports/delete` | `ORGANIZATION_REPORTS_DELETE` | Delete a report                 |
 
+### Organization sessions
+
+| Scope                        | GraphQL Enum                 | Description                                                                                 |
+| ---------------------------- | ---------------------------- | ------------------------------------------------------------------------------------------- |
+| `organization_sessions/read` | `ORGANIZATION_SESSIONS_READ` | Read the analytics sessions of a project, and the Leads and Sessions reports on the project |
+
+A lead scope does not give `organization_sessions/read`. A client manager can hold it at
+the account level, which gives it in every organization.
+
+The owner and member roles do not include a lead scope or `organization_sessions/read`. You
+must grant them to each person who must see leads or sessions.
+
 ## Roles
 
 Each member of an organization holds one of two roles:

package/docs/reference/management-api/schema/analytics-session.md

@@ -23,7 +23,7 @@ type AnalyticsSession {
   """
   What the visit adds up to: when it started and ended, how the visitor arrived, and their device
   and location.
-  Scope: `ORGANIZATION_LEADS_READ`.
+  Scope: `ORGANIZATION_SESSIONS_READ`.
   """
   summary: AnalyticsSessionSummary! @auth
   """
@@ -31,7 +31,7 @@ type AnalyticsSession {
   event, or on its latest event when it captured no lead: `last` ends the page there, `first`
   starts it there, and with neither the page is the 20 events ending there. A page holds at most
   100 events. The newest events can take a few minutes to arrive.
-  Scope: `ORGANIZATION_LEADS_READ`.
+  Scope: `ORGANIZATION_SESSIONS_READ`.
   """
   events(first: Int, after: String, last: Int, before: String): AnalyticsEventConnection! @auth
   """
@@ -42,7 +42,7 @@ type AnalyticsSession {
   lead: Lead @auth
   """
   The Session reports on the visit: the overview, the journey and the event log, in that order.
-  Scope: `ORGANIZATION_LEADS_READ`.
+  Scope: `ORGANIZATION_SESSIONS_READ`.
   """
   reports: [AnalyticsSessionReport!]! @auth
 }

package/docs/reference/management-api/schema/common.md

@@ -180,6 +180,10 @@ enum Scope {
   ORGANIZATION_LEADS_UPDATE
   """Delete leads and their labels."""
   ORGANIZATION_LEADS_DELETE
+  """
+  View a project's analytics sessions, and the Leads and Sessions reports.
+  """
+  ORGANIZATION_SESSIONS_READ
   """Read the action run a workflow was started by."""
   ORGANIZATION_ACTION_RUNS_READ
   """Record a response against an action run."""

package/docs/reference/management-api/schema/lead.md

@@ -80,7 +80,7 @@ type Lead {
   """
   The visit in which the visitor gave the lead. Null when the lead has no capture event, or when
   analytics holds no event for it yet or the capture happened outside production.
-  Scope: `ORGANIZATION_LEADS_READ`.
+  Scope: `ORGANIZATION_SESSIONS_READ`.
   """
   session: AnalyticsSession @auth
   """When the lead was captured."""

package/docs/reference/management-api/schema/project.md

@@ -248,7 +248,7 @@ type Project {
   The Leads reports on the project, in order: how leads are acquired, the journeys behind them,
   and how visits convert to leads. Each is a signed embed URL locked to the project, with an
   editable date range.
-  Scope: `ORGANIZATION_LEADS_READ` or `ORGANIZATION_REPORTS_READ`.
+  Scope: `ORGANIZATION_SESSIONS_READ`.
   """
   leadReports: [LeadReport!]! @auth
   """
@@ -272,13 +272,13 @@ type Project {
   The Sessions reports on the project, in order: how its sessions arrive, the journeys they take,
   and which of them convert. Each is a signed embed URL locked to the project, with an editable
   date range.
-  Scope: `ORGANIZATION_LEADS_READ` or `ORGANIZATION_REPORTS_READ`.
+  Scope: `ORGANIZATION_SESSIONS_READ`.
   """
   analyticsSessionsReports: [AnalyticsSessionsReport!]! @auth
   """
   One visitor session on the project's sites, across all of its events, anchored on its latest
   lead capture, else on its latest timeline event. Null when no event of it is recorded.
-  Scope: `ORGANIZATION_LEADS_READ`.
+  Scope: `ORGANIZATION_SESSIONS_READ`.
   """
   analyticsSession(
     """The ID of the session."""
@@ -289,7 +289,7 @@ type Project {
   inside `window`, and its `summary` adds up those events alone. `first` and `after` read older
   sessions, `last` and `before` newer ones, at most 100 a page. The newest events can take a few
   minutes to arrive.
-  Scope: `ORGANIZATION_LEADS_READ`.
+  Scope: `ORGANIZATION_SESSIONS_READ`.
   """
   analyticsSessions(
     first: Int
@@ -322,7 +322,7 @@ type Project {
   """
   Suggests up to four session searches for what was typed into a sessions search box, each with
   how many sessions it keeps within the window. Requires the `lead-search-suggestions` feature flag.
-  Scope: `ORGANIZATION_LEADS_READ`.
+  Scope: `ORGANIZATION_SESSIONS_READ`.
   """
   analyticsSessionSearchSuggestions(
     """What was typed, at most 200 characters."""

package/docs/reference/tools/mcp.md

@@ -31,6 +31,11 @@ Reads the live version of the project, and the draft of a workspace with its exp
 
 Reads the brief that the project owner wrote about the project, its goals and its entry points.
 
+#### `get_project_settings`
+
+Gives the name, the time zone, and the stored settings of a project, with the link to the
+project settings page. You change the settings in the dashboard.
+
 #### `guide_create_organisation`
 
 Gives the link to create an organization in the dashboard. The MCP server cannot create an organization.
@@ -39,6 +44,42 @@ Gives the link to create an organization in the dashboard. The MCP server cannot
 
 Gives the link to create a project in the dashboard. The MCP server cannot create a project.
 
+### Workspaces
+
+#### `create_workspace`
+
+Creates an empty draft workspace in a project.
+
+#### `update_workspace`
+
+Changes the name of a workspace.
+
+#### `duplicate_workspace`
+
+Copies a workspace into a new draft workspace in the same project. Use the copy to make
+a large change without a risk to the workspace that you edit.
+
+#### `archive_workspace`
+
+Removes a workspace from the default list of workspaces. The contents do not change. You
+cannot archive the live workspace.
+
+#### `unarchive_workspace`
+
+Puts an archived workspace back in the list as a draft.
+
+#### `export_workspace`
+
+Gives a workspace as a bundle that you can import. The bundle can be large.
+
+#### `import_workspace`
+
+Creates a draft workspace from a bundle, in the same project or in a different project.
+If the content uses assets, upload the assets to the project first and give `asset_map`.
+If the tool refuses the bundle, it creates nothing and gives all the errors.
+
+You cannot delete or publish a workspace with these tools. Do these in the dashboard.
+
 ### Documentation
 
 #### `get_schema_info`
@@ -71,9 +112,9 @@ Creates an experience.
 
 Creates, updates, or deletes steps, conditions, actions, fields, nodes, and edges as one operation.
 
-#### `guide_delete_experience`
+#### `delete_experience`
 
-Gives the link to the experience in the dashboard, where you delete it.
+Deletes an experience from the workspace draft. Live visitors see the change after you publish the workspace.
 
 ### Steps, fields, conditions, and actions
 
@@ -89,9 +130,9 @@ Reads a step, with its fields.
 
 Renames a step, or binds it to the content entry that it renders.
 
-#### `guide_delete_step`
+#### `delete_step`
 
-Gives the link to the step in the dashboard, where you delete it.
+Deletes a step from the workspace draft. You cannot delete a step that a flow uses. Live visitors see the change after you publish the workspace.
 
 #### `list_fields`
 
@@ -101,9 +142,14 @@ Lists the fields in a workspace. A step ID filters the list.
 
 Reads a field, with its options and the steps that use it.
 
-#### `guide_delete_field`
+#### `create_field`
 
-Gives the link to the field in the dashboard, where you delete it.
+Creates a field in a workspace. To show the field to visitors, add it to a step with
+`update_experience_flow`.
+
+#### `delete_field`
+
+Deletes a field from the workspace draft. You cannot delete a field that a step uses. Live visitors see the change after you publish the workspace.
 
 #### `list_conditions`
 
@@ -121,6 +167,11 @@ Lists the actions in a workspace.
 
 Reads an action.
 
+#### `create_action`
+
+Creates an action in a workspace, with the fields that it gets. The action runs when a
+flow gets to it: add it to a flow with `update_experience_flow`.
+
 ### Feature flags
 
 #### `list_features`
@@ -139,6 +190,10 @@ Creates a feature flag.
 
 Updates the name, description, state, or weight of a feature flag.
 
+#### `delete_feature`
+
+Deletes a feature flag from the workspace draft. Live visitors see the change after you publish the workspace.
+
 ### Content
 
 #### `list_content_models`
@@ -157,6 +212,11 @@ Creates a content model.
 
 Renames a content model, or changes its schema. A schema change migrates the entries of the model.
 
+#### `delete_content_model`
+
+Deletes a content model from the workspace draft. You cannot delete a content model
+while a content entry uses it. Live visitors see the change after you publish the workspace.
+
 #### `list_content_blocks`
 
 Lists the content blocks in a workspace.
@@ -173,6 +233,10 @@ Creates a content block.
 
 Renames a content block, or changes its schema. The entries do not change.
 
+#### `delete_content_block`
+
+Deletes a content block from the workspace draft. Live visitors see the change after you publish the workspace.
+
 #### `list_content_entries`
 
 Lists the content entries in a workspace. Give the ID of a content model to show only its entries.
@@ -189,9 +253,10 @@ Creates a content entry of a content model.
 
 Changes the data of a content entry.
 
-#### `guide_delete_content_entry`
+#### `delete_content_entry`
 
-Gives the link to the content entry in the dashboard, where you delete it.
+Deletes a content entry from the workspace draft. You cannot delete an entry that a
+step or a different entry uses. Live visitors see the change after you publish the workspace.
 
 #### `validate_workspace_content_entries`
 
@@ -215,6 +280,11 @@ Gives a URL to upload the file of an asset to.
 
 Records the asset after you upload its file.
 
+#### `delete_asset`
+
+Deletes an asset from the project, with its files. You cannot delete an asset that a
+published version uses. The deletion occurs immediately.
+
 ### Design systems
 
 #### `list_design_systems`
@@ -233,6 +303,37 @@ Creates a design system from a Markdown asset.
 
 Renames a design system, or replaces its Markdown asset.
 
+#### `delete_design_system`
+
+Deletes a design system from the project. The deletion occurs immediately.
+
+### Preview environments
+
+A preview environment is a site with the Picked SDK installed, for example your
+production site or your test site. A preview opens on it.
+
+#### `list_preview_environments`
+
+Lists the preview environments of a project, with the URL of each site. Give a URL to
+`get_preview_url` to see your unpublished work on that site.
+
+#### `create_preview_environment`
+
+Adds a preview environment to a project.
+
+#### `update_preview_environment`
+
+Changes the name or the URL of a preview environment. You cannot delete a preview
+environment with the MCP server. Delete it in the dashboard.
+
+### Integrations
+
+#### `list_external_apis`
+
+Lists the external APIs of a project. A workflow `http` node can call only a URL on one
+of these APIs. The list shows the name, the origin, and the type of the credential of each API.
+It does not show a credential value. You register an API in the dashboard.
+
 ### Workflows
 
 A workflow runs a graph of nodes when its trigger occurs. The trigger is a domain
@@ -262,9 +363,10 @@ Renames a workflow, and sets its visit cap.
 
 Creates, updates, or deletes nodes and edges as one operation.
 
-#### `guide_delete_workflow`
+#### `delete_workflow`
 
-Gives the link to the workflow in the dashboard, where you delete it.
+Deletes a workflow from the workspace draft. The published workflow continues to run
+until you publish the workspace.
 
 #### `list_workflow_runs`
 
@@ -311,6 +413,15 @@ Gives the number of leads that match a search, and a link to the leads list in t
 dashboard. It does not give the leads. Use `list_lead_fields` first to get the fields
 that you can search by.
 
+### Analytics reports
+
+#### `list_analytics_reports`
+
+Lists the Metabase reports of a project: the Leads and Sessions dashboards, and the reports
+that you added to the project. Each report has its Metabase ID and the parameters that
+limit it to the project, for example `project_id`. To read the data, use the Metabase MCP
+server with the ID, and filter by all these parameters.
+
 ### Publish
 
 #### `get_preview_url`

package/package.json

@@ -1,13 +1,13 @@
 {
   "name": "picked",
   "description": "The Picked SDK front door: the client, the picked.config helpers, and the picked CLI in one install",
-  "version": "0.0.107-next.1",
+  "version": "0.0.107-next.2",
   "bin": {
     "picked": "dist/esm/bin.js"
   },
   "dependencies": {
-    "@picked/cli": "0.0.107-next.1",
-    "@picked/config": "0.0.107-next.1"
+    "@picked/cli": "0.0.107-next.2",
+    "@picked/config": "0.0.107-next.2"
   },
   "devDependencies": {
     "@picked/client": "workspace:*",
@@ -64,7 +64,7 @@
   "main": "./dist/cjs/index.js",
   "module": "./dist/esm/index.js",
   "peerDependencies": {
-    "@picked/client": "0.0.107-next.1"
+    "@picked/client": "0.0.107-next.2"
   },
   "private": false,
   "publishConfig": {