@xenia-martech/mcp 1.0.0 → 1.2.0-dev.1

package/README.md

@@ -2,6 +2,7 @@
 
 [![npm version](https://img.shields.io/npm/v/@xenia-martech/mcp.svg)](https://www.npmjs.com/package/@xenia-martech/mcp)
 [![npm downloads](https://img.shields.io/npm/dm/@xenia-martech/mcp.svg)](https://www.npmjs.com/package/@xenia-martech/mcp)
+[![coverage](https://img.shields.io/endpoint?url=https%3A%2F%2Fcdn.jsdelivr.net%2Fnpm%2F%40xenia-martech%2Fmcp%40latest%2Fcoverage.json)](https://www.npmjs.com/package/@xenia-martech/mcp)
 [![node](https://img.shields.io/node/v/@xenia-martech/mcp.svg)](https://www.npmjs.com/package/@xenia-martech/mcp)
 [![license](https://img.shields.io/npm/l/@xenia-martech/mcp.svg)](https://www.npmjs.com/package/@xenia-martech/mcp)
 
@@ -21,6 +22,26 @@ you> wire the abandoned-cart journey into my checkout
   → detects your stack, writes .env, and edits your component
 ```
 
+## What it wires
+
+After you choose how to get the SDK token, the assistant does the rest without stopping:
+
+- **One-time setup** for your stack (`xenia_setup_project`). In Next.js: `proxy.ts` (or merges into
+  your existing one) for the visitor cookie and page URL, a `lib/xenia.ts` server helper with a
+  timeout and circuit breaker, consent from your cookie banner, and form conversions.
+- **Each journey** you name, in your real components: server-side with `{ fallback: null }` so an
+  outage renders your default content; `track()` for event triggers.
+- **Checks** — a type-check/build and `xenia_verify`, plus warnings about the journey itself (an
+  A/B split that would show the same visitor different variants, a journey that's stopped) with the
+  dashboard fix.
+
+One SDK token covers everything, webhook triggers that require auth included, and a minted token
+never expires unless you ask for an expiry (it can always be revoked). Connected to a non-default
+engine with `--base-url`? The mint tool also writes `XENIA_URL`, so your app calls that same engine.
+
+It stops to ask only for the token choice, a production write, or — if your site has no consent
+banner — whether analytics needs consent.
+
 ## Install
 
 Pick your assistant — each command registers the server via the assistant's own MCP config.
@@ -68,10 +89,11 @@ can be disconnected there at any time.
 | `xenia_status` | Who is connected, and the active workspace |
 | `xenia_list_scopes` / `xenia_select_scope` | See and switch org / tenant / environment |
 | `xenia_list_journeys` | The journeys in the active workspace, each with its trigger(s) — flagged `can't connect` for a scheduler or a Shopify/HubSpot trigger whose connector isn't connected |
-| `xenia_get_journey` | Trigger id, method, request fields, content keys, and a stack-matched SDK snippet |
+| `xenia_get_journey` | Trigger id, method, request fields, content keys, a stack-matched SDK snippet, and journey warnings (e.g. a non-sticky A/B split) |
 | `xenia_list_content_keys` | Every personalization key, and which journeys resolve it |
 | `xenia_detect_stack` | Framework, SDK entry point, and which token type this project needs |
-| `xenia_mint_sdk_token` | Mint a token and write it to your env file |
+| `xenia_setup_project` | The one-time wiring plan for this stack: files to create or merge, consent, forms, verification |
+| `xenia_mint_sdk_token` | Mint a token (never expires unless `expiresInDays` is given) and write it, plus the engine URL when it isn't the default, to your env file |
 | `xenia_verify` | Read journeys, resolve a content key, optionally fire a test event |
 | `xenia_logout` | Revoke the session and forget the local credential |
 

package/coverage.json

@@ -0,0 +1 @@
+{"schemaVersion":1,"label":"coverage","message":"97%","color":"brightgreen"}