nordva

Set up Nordva Launch in one command: changelog, waitlist, feedback, notifications, and revenue, contacts and attribution from Stripe, behind one API key and one MCP server.

npx nordva@latest init

You do not need an account first. Run it in your project folder and it:

1. Signs you in through the browser. It shows a short code and opens the dashboard. Sign in, or sign up free, and confirm the code matches. No key is copied by hand.
2. Asks what the project is called. A new project is named "My Project" with a generated address. Press Enter to take the suggestion from your package.json, or type your own; the address becomes launch.nordva.dev/waitlist/<slug>. Only asked while the project still has the default name.
3. Writes your keys to the env file your framework reads (.env.local for Next.js and Vite, .env otherwise) and makes sure git ignores it. It will not write a secret into a file git already tracks.
4. Installs the MCP server for Claude Code, Cursor, VS Code and Windsurf, whichever it finds. The VS Code file never contains the key; the Cursor file is gitignored; Windsurf's file is in your home directory, shared by all your projects.
5. Adds NORDVA.md, a short guide for you and your AI coding agent, and a pointer to it in CLAUDE.md / AGENTS.md if you have one.
6. Makes one API call to prove it works, then offers to open your live waitlist page next to the dashboard so you can join and watch the signup arrive. (Never in --yes, --no-browser or non-interactive runs.)
7. Hands your AI coding agent a plan to write. It offers to start Claude Code with a prompt (or copy the prompt to your clipboard) that has the agent read your codebase and write NORDVA_PLAN.md: which parts of Launch fit your product, which files change, what to build first. The agent changes no code until you pick a step. The same prompt is in NORDVA.md and on the MCP server as plan_integration. More

It asks before each change and never overwrites what is already there.

Options

| Flag | | |---|---| | -y, --yes | Take every default, ask nothing (scripts, CI) | | --dry-run | Show what would happen, write nothing | | --no-browser | Print the sign-in link instead of opening it | | --skip-env, --skip-mcp, --skip-docs, --skip-plan | Leave that step out | | --name NAME, --slug SLUG | Name the project without being asked | | -v, --version · -h, --help | |

| Variable | | |---|---| | NORDVA_SECRET_KEY | Use this key instead of signing in through the browser | | NORDVA_API_BASE | Point at a local API while developing |

Draft a changelog entry from your commits

npx nordva changelog                  # commits since the last tag
npx nordva changelog --since v1.3.0 --version 1.4.0
npx nordva changelog --since 2026-09-01 --dry-run

It reads the commit subjects (git log --no-merges) since the last tag, or --since a tag, commit or date, and sends them to the API, which groups them into New, Improved, Fixed and Breaking changes (conventional commit prefixes such as feat: and fix:; housekeeping like chore: and merges are left out). The result is saved as a draft: nothing is published and nobody is emailed until you publish it in the dashboard. --dry-run only prints it. The key is NORDVA_SECRET_KEY from the environment or from .env.local, .env or .dev.vars, where init put it.

| Flag | | |---|---| | --since REF | A tag, commit or date (YYYY-MM-DD). Default: the last tag, else the last 50 commits | | --version V, --title T | Set the entry's version and title | | --limit N | At most N commits (up to 500) | | --dry-run | Print the draft, save nothing |

How the sign-in stays safe

The CLI keeps a random secret and sends only its hash. The same short code is shown in your terminal and in the dashboard, and you confirm they match, so approving a link someone else sent you gives them nothing you did not intend. A code lasts ten minutes and works once. The keys are created at the moment your terminal collects them and are never stored in plain text. They are named after your machine, listed under API Keys in the dashboard and revocable there. Signing in again from the same machine replaces that machine's keys.

Requires Node 18 or newer. MIT licensed. Docs: https://docs.nordva.dev