@apex-inc/mcp-server 0.29.0 → 0.30.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@apex-inc/mcp-server",
-  "version": "0.29.0",
+  "version": "0.30.0",
   "description": "MCP server for Apex \u2014 currently in private beta.",
   "type": "module",
   "main": "dist/index.js",

package/skills/apex-communications/SKILL.md

@@ -218,6 +218,10 @@ Examples:
 
 When generating communications for a journey, **mention exit rules in the same breath**. The apex-journeys skill has the full pattern.
 
+## Sender domain is a hop
+
+`start_sender_domain` issues DNS records. That is not green. The shop pastes them at the registrar; you cannot click the registrar for them. Poll `get_sender_domain` until status is verified.
+
 ## Proactive nudge: missing exit rules
 
 When a user generates or creates a marketing journey with `wait` steps and a purchase or activation goal, proactively check whether exit rules exist:

package/skills/apex-integration-cookbook/SKILL.md

@@ -334,3 +334,14 @@ ad accounts + Stripe in their workspace; per-client spend/revenue/ROI
 and the transparent at-risk rule roll up on the agency org
 (`GET /api/agency/clients` — org owner/admin sessions only; it is a
 financial boundary with no API-key lane).
+
+## Recipe: Set up Apex from this repo
+
+If get_setup_state shows first-run incomplete, name the shop before inventing events.
+
+1. Call `get_setup_state`. If the shop has no name, no vertical, or no conversion model, stop.
+2. `update_organization` with the shop's real name. `update_workspace` with `workspace_name`, `vertical`, `conversion_model`, and `website_url` when you know them. The rail finishes from those saves — do not look for a mark-complete tool.
+3. Name Production (and optional Beta) sites with `list_workspace_environments` / `set_workspace_environments` before you trust the Production slice.
+4. Install the snippet or SDK and wire the events the shop actually fires. Do not invent event names to make a step look done.
+5. Finish writable setup with the matching tools (`claim_links_subdomain`, `set_consent_posture`, webhooks, scoring, invitations, engagement, app platforms, attribution, sender domain, push keys, protect auto-pause). Consent answers are not a live-site tap. Sender-domain records issued are not green — poll `get_sender_domain` until verified.
+6. Hop only when the next incomplete step is a hop: `start_integration_install` for GitHub, Stripe, Meta, Google, LinkedIn, or TikTok. Legal acknowledgements stay on the opened page. You cannot click the ad consoles or the DNS registrar for them.

package/skills/apex-partner-network/SKILL.md

@@ -188,4 +188,5 @@ Policies:
 
 - `apex-integration-cookbook` — end-to-end patterns combining partner network + communications + experiments
 - MCP tools: `list_partner_programs`, `create_partner_program`, `invite_partner`, `approve_payouts`, `vouch_for_partner`, `get_effective_fees`
+- Stripe Connect for the shop is a hop: `start_integration_install` with `type: "stripe"`. Legal acknowledgements stay on the opened page.
 - Docs: `/docs/partner-network/` for concept walkthroughs + integration guides