Install and run the OfflineCreator MCP CLI

Install the CLI on demand or pin it to a project

The shortest supported path is `npx -y @offlinecreator/mcp`. The package currently published in the npm registry is `0.1.2`, and its package metadata requires Node.js 20 or newer. For a repeatable script, name the version explicitly: `npx -y @offlinecreator/mcp@0.1.2 --help`.

Use on-demand execution when you want a quick interactive command and are comfortable resolving the requested package version at run time. Use a project-local, exact dependency when a repository or CI workflow needs the same reviewed package until you deliberately update it. That choice controls package resolution; authentication remains a separate setup step.

Check the runtime before installing

Run `node --version` and confirm the major version is at least 20. The package's declared floor is `>=20`, but that floor is not the same as a recommendation to start a new installation on Node 20. The Node.js release schedule lists version 20 as end-of-life after April 30, 2026, while versions 22 and 24 remain supported LTS lines on the research date.

For a new workstation or build image, choose a currently supported LTS release that also satisfies the package floor. Existing Node 20 environments may satisfy npm's engine check, but the runtime no longer receives ordinary Node.js project maintenance. Recheck both the package `engines` field and the Node.js release table when updating this guide.

Choose how npm resolves the package

For an occasional manual run, use `npx -y @offlinecreator/mcp@0.1.2 <command>`. npm documents that `npx` can run a binary from a local or remote package. If the requested package is absent from local dependencies, npm places it in its cache and adds that location to the child process path; `-y` suppresses the installation prompt.

For a repository-owned workflow, add an exact dependency with `npm install --save-exact @offlinecreator/mcp@0.1.2`, review the resulting lockfile, and invoke the package from a project script. This keeps package selection in normal dependency review instead of silently following a future registry `latest` tag. Do not describe this as a permanent system-wide install: the useful distinction is ephemeral resolution versus a version and integrity record committed with one project.

On demand

`npx -y @offlinecreator/mcp@0.1.2 --help`Explicitly names the researched registry release and avoids an interactive npm prompt.

Project pinned

`npm install --save-exact @offlinecreator/mcp@0.1.2`Records the selected dependency in the project so updates can be reviewed with its lockfile.

Verify the binary before adding an account key

Start with the researched release's help path: `npx -y @offlinecreator/mcp@0.1.2 --help`. The published package exposes one executable named `offlinecreator-mcp`, and its CLI entrypoint handles `help`, `--help`, and `-h` before loading account configuration. A successful help response verifies Node, npm resolution, the downloaded package, and executable dispatch without making an authenticated Studio request.

Then configure `OFFLINECREATOR_API_KEY` through the environment and run the specific CLI task you need. The official installation guide requires that environment value for local stdio operation and warns against placing a key in a URL, committed file, or remote OAuth configuration. This research does not perform a live authenticated command because production credentials are outside the page-research scope.

Diagnose install and launch failures in order

If npm reports an engine mismatch, stop and update Node rather than bypassing the package requirement. If `npx` pauses for permission to install, add `-y` before the package name; npm notes that npx options must precede positional arguments. If package behavior differs from this page, rerun with the explicit `@0.1.2` version and compare it with an unversioned run.

A missing-key error after the help check is an authentication setup issue, not proof that package installation failed. Configure the environment through the focused authentication guide. Conversely, a help failure before account configuration points first to Node, npm, network or registry resolution, and executable dispatch. Keeping those stages separate prevents replacing a key, changing Studio settings, or debugging generation while the package itself has not launched.

Treat the registry release as the executable boundary

On August 9, 2026 UTC, npm's `latest` metadata returned `0.1.2`, published at 2026-08-08T19:13:50.984Z. The public repository's `package.json` and README also identified `0.1.2`, so this page pins the release that was available through the registry at verification time.

Before copying these commands later, inspect the registry version, its Node engine, and its packaged help output again. Source-repository documentation can describe work ahead of the registry, while an unversioned npx command can begin resolving a newer release after publication. Version pinning makes the example reproducible; removing the pin is an explicit decision to follow the current registry release.