@apex-inc/mcp-server 0.27.1 → 0.27.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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@apex-inc/mcp-server",
3
- "version": "0.27.1",
3
+ "version": "0.27.2",
4
4
  "description": "MCP server for Apex \u2014 currently in private beta.",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -137,7 +137,7 @@ Read these resources before suggesting communications-related actions to underst
137
137
  1. list_communications(pipeline="transactional", channel="email")
138
138
  → narrow to the pipeline + channel the step needs. 'transactional'
139
139
  bypasses opt-out and is ONLY valid after a recipient-initiated trigger
140
- (user_signup, password_reset_requested). 'marketing' is consent-gated.
140
+ (user_signed_up, password_reset_requested). 'marketing' is consent-gated.
141
141
  2. Read each row's subject + one-line body preview to disambiguate similar
142
142
  titles — you do NOT need to preview_communication every candidate.
143
143
  3. Pick by `id` (+ its version) and attach it to the send step.
@@ -153,7 +153,7 @@ hard-block**. For those journeys, filter to `pipeline="marketing"`.
153
153
  2. generate_communications with the welcome entry ID
154
154
  3. edit_communication to customize copy
155
155
  4. send_test_communication to preview
156
- 5. Show user the apex.track("user_signup") call to add
156
+ 5. Show user the apex.track("user_signed_up") call to add
157
157
  ```
158
158
 
159
159
  ### "My churn rate is high"
@@ -27,7 +27,7 @@ Events are batched and sent to `POST /api/events` automatically. Call `flush()`
27
27
 
28
28
  ```typescript
29
29
  // On signup
30
- track("signup_completed", { method: "email", plan: "free" });
30
+ track("user_signed_up", { method: "email", plan: "free" });
31
31
  identify(user.id, {
32
32
  email: user.email,
33
33
  name: user.name,
@@ -117,7 +117,7 @@ For agent-driven testing through MCP, use the **`send_server_event`** tool — s
117
117
 
118
118
  ## Event naming conventions
119
119
 
120
- - **snake_case**: `signup_completed`, `feature_used`, `invoice_paid`
120
+ - **snake_case**: `user_signed_up`, `feature_used`, `invoice_paid`
121
121
  - Context in **properties**: `track("ui_action", { action: "click", name: "Start trial", location: "pricing" })`
122
122
  - For experiments, include `experimentId` and `variant` in properties
123
123
  - One primary metric per experiment; secondary metrics as properties