@apex-inc/mcp-server 0.48.8 → 0.48.9
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/dist/comm-experiment-create.d.ts +52 -0
- package/dist/comm-experiment-create.d.ts.map +1 -0
- package/dist/comm-experiment-create.js +38 -0
- package/dist/comm-experiment-create.js.map +1 -0
- package/dist/setup-catchup-tools.d.ts +10 -0
- package/dist/setup-catchup-tools.d.ts.map +1 -1
- package/dist/setup-catchup-tools.js +10 -2
- package/dist/setup-catchup-tools.js.map +1 -1
- package/dist/smoke-tools.d.ts +1 -1
- package/dist/smoke-tools.d.ts.map +1 -1
- package/dist/smoke-tools.js +1 -0
- package/dist/smoke-tools.js.map +1 -1
- package/dist/tool-groups.d.ts.map +1 -1
- package/dist/tool-groups.js +1 -0
- package/dist/tool-groups.js.map +1 -1
- package/dist/tools/ad-platforms.js +1 -1
- package/dist/tools/ad-platforms.js.map +1 -1
- package/dist/tools/experiments.d.ts +6 -6
- package/dist/tools/experiments.d.ts.map +1 -1
- package/dist/tools/experiments.js +6 -1
- package/dist/tools/experiments.js.map +1 -1
- package/dist/tools/letters.d.ts +77 -24
- package/dist/tools/letters.d.ts.map +1 -1
- package/dist/tools/letters.js +14 -8
- package/dist/tools/letters.js.map +1 -1
- package/dist/tools/measurement.d.ts +2 -2
- package/dist/tools/measurement.d.ts.map +1 -1
- package/dist/tools/measurement.js +20 -1
- package/dist/tools/measurement.js.map +1 -1
- package/dist/tools.d.ts +96 -32
- package/dist/tools.d.ts.map +1 -1
- package/package.json +1 -1
- package/skills/apex-integration-cookbook/SKILL.md +1 -1
- package/skills/apex-setup/SKILL.md +1 -1
|
@@ -34,7 +34,7 @@ Ask the owner which event is the sale, signup, or lead that matters. Save it wit
|
|
|
34
34
|
Call get_setup_state after every write and work the next step with the tool it names. When the owner says a step or area is not for them, record it with skip_setup_step or decline_setup_area, in their words. Never record one to make progress look finished. No tool marks a step done; steps finish when the real thing happens.
|
|
35
35
|
|
|
36
36
|
## 7. Browser steps
|
|
37
|
-
When the next step needs a person (payment, an ad or app store console, DNS, legal acknowledgements), give the link and the reason from the checklist and wait. Use start_integration_install for GitHub, Stripe, ad platforms, and Google Analytics; it polls until connected. After ads are connected, make a paid Apex Link before inventing UTMs.
|
|
37
|
+
When the next step needs a person (payment, an ad or app store console, DNS, legal acknowledgements), give the link and the reason from the checklist and wait. Use start_integration_install for GitHub, Stripe, ad platforms, and Google Analytics; it polls until connected. After ads are connected, make a paid Apex Link before inventing UTMs. Apex sends nothing to an ad platform until someone says whether another tool already sends there: check the repo for AppsFlyer, Adjust, Branch or Singular, ask about Shopify's app or a pixel, and record the answer with set_conversion_source_of_truth. If the app already uses AppsFlyer, record AppsFlyer as the sender for its networks before wiring ad sends, then follow get_mmp_migration: keep AppsFlyer in the app until its remove step, and use the event names and SKAN report address it gives.
|
|
38
38
|
|
|
39
39
|
## 8. First value
|
|
40
40
|
Once events are live, show the owner what arrived with apex_recent_events, and give them the live stream link it returns so they can watch their own site talk to Apex. Then propose exactly one first step from what you learned about the organization: one experiment with plan_experiment, or one message with recommend_communications. Say why it fits this workspace in a sentence. Create nothing live without the owner's yes; a draft they can open is fine.
|