| name | sales-memberstack |
| description | Memberstack platform help — no-code membership, auth, and Stripe-payments layer for sites you build yourself (memberstack.com): add login (email/password, passwordless, social, 2FA), paid memberships, and content gating to Webflow, WordPress, or any custom site via a script tag + data attributes. Developer surface: a front-end DOM package (public key) plus an Admin REST API (base admin.memberstack.com, X-API-KEY secret key, member CRUD, verify-token, cursor pagination, 25 req/s) and 8 webhooks (member.created/updated/deleted, member.plan.*, team.*). Use when building a Memberstack Admin API or webhook integration, syncing members from your backend, verifying a member JWT to gate your own API, webhook signatures can't be verified via REST, a PATCH wiped the json field, or transaction-fee/plan questions. Do NOT use for course/membership-platform strategy or comparison (use /sales-membership), checkout-conversion optimization across tools (use /sales-checkout), or email marketing (use /sales-email-marketing). |
| argument-hint | [describe what you need help with in Memberstack] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","membership","no-code","platform"] |
| github | https://github.com/memberstack |
Memberstack Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
-
What are you trying to do?
- A) Manage members from your backend (create/read/update/delete) via the Admin REST API
- B) Verify a member's JWT to gate your own API or app
- C) React to events via webhooks (member.created, member.plan.*) — sync to a CRM/warehouse
- D) Configure front-end auth, gating, or Stripe checkout (DOM package + data attributes)
- E) Pick a plan / understand transaction fees
- F) Fix a problem — webhook verification, json overwrite, member-not-found, 1.0→2.0 migration
-
Front-end or back-end? Browser auth/gating/checkout = DOM package (public key). Server-side member ops + token/webhook verification = Admin REST/Node (secret key). This decides everything.
Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2.
Step 2 — Route or answer directly
| If the question is about... | Route to... |
|---|
| Choosing or comparing membership/course platforms | /sales-membership {question} |
| Checkout-conversion / order-bump / upsell strategy across tools | /sales-checkout {question} |
| Email sequences and broadcasts (Memberstack doesn't send email) | /sales-email-marketing {question} |
| Wiring Memberstack into a CRM/warehouse or other tools | /sales-integration {question} |
| Membership/community structure, pricing, and retention strategy | /sales-membership {question} |
When routing, give the exact command, e.g. "Platform comparison — run: /sales-membership Memberstack vs a hosted course platform".
Step 3 — Memberstack platform reference
Read references/platform-guide.md for the full reference — the module map (DOM vs Admin, what's front-end vs server-side vs webhook), the plan/transaction-fee gates, the member data model with JSON shapes, and quick-start recipes (create a member server-side; verify a member JWT to gate your API; sync member.created to a CRM via webhook).
Read for the Admin REST API — base , auth ( test / live, server-side only), the member CRUD + verify-token + add/remove-plan endpoints, cursor pagination, the 25 req/s limit, the 8 webhook events, and the webhook-signature-verification caveat.
