featurely-cli

Official CLI for setting up and managing Featurely integrations.

Quick start

npx featurely-cli@latest init

init is a guided, interactive setup that handles everything in one run:

1. Opens a browser to authenticate with your Featurely account
2. Asks which packages to set up (featurely-mcp is configured as an MCP server, not installed as a dependency)
3. Creates an API key with the right permissions for your chosen packages
4. Detects your framework and injects initialization code
5. Writes NEXT_PUBLIC_FEATURELY_API_KEY and NEXT_PUBLIC_FEATURELY_PROJECT_ID to .env.local
6. Optionally syncs env vars to Vercel if a .vercel/ folder is detected
7. If featurely-mcp was selected: configures the MCP server for Claude Desktop, Cursor, VS Code, or Windsurf

Requirements

• Node.js ≥ 18
• A Featurely account (sign up free)

Commands

init

npx featurely-cli@latest init

Full guided setup. Run this once per project.

login

npx featurely-cli@latest login [--force]

Authenticate your machine via browser. If already signed in, use --force to re-authenticate.

logout

npx featurely-cli@latest logout

Remove the locally stored session token.

whoami

npx featurely-cli@latest whoami

Print the currently signed-in account, user ID, and session token expiry.

scan

npx featurely-cli@latest scan [--project-id <id>] [--api-key <key>]

Upload the current project's full dependency list to your Featurely dashboard for tracking.

Requires a project API key. By default reads NEXT_PUBLIC_FEATURELY_PROJECT_ID and NEXT_PUBLIC_FEATURELY_API_KEY from .env.local. Override with flags.

Note: scan uses your project API key directly — it does not use the session token from login.

mcp setup

npx featurely-cli@latest mcp setup

Configure the featurely-mcp server for your AI editor without running the full init flow. Supports Claude Desktop, Cursor, VS Code Copilot, and Windsurf.

Available packages

| Package | Description | Auto-init | | ---------------------------- | ------------------------------------------ | ------------------------------------------------------------------- | | featurely-error-tracker | Automatic JS error reporting | Yes | | featurely-feature-reporter | Feedback widget & bug reports | Yes | | featurely-site-manager | Feature flags, maintenance mode, analytics | Yes | | featurely-i18n | Translation management | Yes | | featurely-logger | Structured event logging | Manual — see docs | | featurely-mcp | AI assistant integration (MCP server) | Configured via mcp setup, not installed as a dep |

Framework support

The CLI detects your framework from package.json and directory structure:

| Framework | Detection | | -------------------- | ----------------------------------- | | Next.js App Router | next in deps + app/ directory | | Next.js Pages Router | next in deps + pages/ directory | | React | react in deps (no next) | | Vue | vue in deps | | Nuxt | nuxt in deps | | Node.js | fallback |

Package managers detected by lockfile: npm, yarn, pnpm, bun.

Global install

# npm
npm install -g featurely-cli

# pnpm
pnpm add -g featurely-cli

# yarn
yarn global add featurely-cli

# bun
bun add -g featurely-cli

Local testing (without installing globally)

# Build and run directly
npm run build
node dist/index.js init

License

MIT