Installation

Choose only the tools you need. The quickest way to try the protection CLI is to run it directly from the repository.

Requirements

You want to use	Required
CLI or local protect MCP	Node.js 18.17+
Self-hosted license server SDK	Node.js 22+
Rust commerce MCP / Axum backend	Rust + Cargo
Cloudflare Worker or remote MCP development	Wrangler and appropriate credentials

1. Run the CLI from source

From the nougat-devpay/ directory:

node tools/devpay-cli/devpay.mjs --help
node tools/devpay-cli/devpay.mjs doctor

After installing it globally, the command is yp, not devpay.

2. Optionally install a local tarball

cd tools/devpay-cli
npm pack
npm install -g ./yetdapay-cli-0.2.0.tgz
yp --help

Not published on npm

The CLI package is @yetdapay/cli (private: true): npm pack builds a local tarball, but the package is not a public registry release. Do not run npm publish.

3. Connect an AI agent (optional)

From nougat-devpay/, point your MCP client at:

node tools/devpay-mcp/server.mjs --workspace /absolute/path/to/your-project

This local MCP server calls the yp CLI. It can run trusted project code; it is not a sandbox. For client configuration and authorization boundaries see Local MCP setup.

4. Choose an SDK (optional)

Package	Use it for
@yetdapay/license-web	Browser activation and device proofs
@yetdapay/license-server	Node 22 server-side enforcement
@yetdapay/license-nuxt	Nuxt 3 license integration
@yetdapay/sdk	Copy-in Vue/React donation and feedback widgets

License SDK sources live under sdk/license/ and can be consumed using local file: dependencies or npm pack. They are not publicly published. The commerce widget SDK is a source bundle, not a registry install.

Verify your setup

yp doctor

If doctor reports FAIL, follow Troubleshooting. Local project configuration or a running backend may be needed for particular checks.

Next: Protect a module in five steps · SDK overview · 한국어 설치 안내