engageplus
v1.2.4
Published
Set up EngagePlus authentication in your project — zero friction, AI-agent friendly
Maintainers
Readme
engageplus
Zero-friction authentication setup for developers. One command to get EngagePlus authentication running in any web project — designed for vibe coding with AI assistants like Cursor.
Quick Start
npx engageplus initThat's it. The CLI will:
- Open your browser — sign in with GitHub, Google, or any provider
- Create an organization — or select an existing one
- Create an app — or select an existing app within the organization
- Generate an API key — scoped to the app, with full management access
- Register your redirect URI —
http://localhost:PORT/callback - Write config files:
.env.local— credentials for your app.cursor/rules/engageplus.mdc— AI agent instructions
Usage
# Interactive setup (shows login widget)
npx engageplus init
# Auto-login with a specific provider
npx engageplus init --github
npx engageplus init --google
npx engageplus init --microsoftWhat Gets Written
.env.local
ENGAGEPLUS_ORG_SLUG=your_org_slug
ENGAGEPLUS_APP_SLUG=your_app_slug
ENGAGEPLUS_API_KEY=epk_your_key
ENGAGEPLUS_API_BASE=https://api.engageplus.id.cursor/rules/engageplus.mdc
A comprehensive rule file that teaches your AI assistant how to:
- Add the EngagePlus login widget to any framework (React, Vue, Svelte, vanilla JS)
- Handle OAuth callbacks
- Configure authentication providers via the Management API
- Set up webhooks for auth events
- Connect Supabase or Airtable for user data sync
- Customize the widget theme and branding
After Setup
Just tell your AI assistant what you need:
- "Add a login page to my app"
- "Set up Google and GitHub authentication"
- "Connect my Supabase database to sync user data"
- "Add a webhook to notify my backend on login"
The AI reads .cursor/rules/engageplus.mdc and knows your org slug, app slug, API key, and how to use every EngagePlus API.
Requirements
- Node.js 18+
- A browser (for the one-time authentication step)
How It Works
┌─────────────┐ ┌──────────────┐ ┌──────────────────┐
│ Your CLI │────▶│ Browser │────▶│ EngagePlus Auth │
│ (terminal) │◀────│ (localhost) │◀────│ (OIDC/OAuth) │
└──────┬───────┘ └──────────────┘ └──────────────────┘
│
▼
┌──────────────┐ ┌──────────────┐ ┌──────────────────┐
│ Create Org │────▶│ Create App │────▶│ Generate API Key │
└──────┬───────┘ └──────┬───────┘ └────────┬─────────┘
│ │ │
▼ ▼ ▼
.env.local .cursor/rules/engageplus.mdcThe CLI starts a temporary local server, opens your browser for authentication, receives the tokens, then uses them to set up your organization, create an app, and generate an API key. All credentials are written to local files — nothing is stored externally.
