snipara-openclaw-install

OpenClaw-only Snipara onboarding wrapper.

Use this when the user wants one command that configures Snipara Hosted MCP for the current project, writes OpenClaw environment variables, installs the OpenClaw plugin/hook package, and tells them exactly what still needs a runtime restart.

This package is deliberately narrow:

• create-snipara remains the canonical general Snipara onboarding CLI.
• snipara-openclaw-hooks remains the canonical OpenClaw hook package.
• snipara-openclaw-install is the OpenClaw convenience wrapper around those setup surfaces and the OpenClaw config file.

Quick Start

npx snipara-openclaw-install

With an existing key, prefer environment variables so the key is not recorded in shell history:

SNIPARA_API_KEY=snp-your-key \
SNIPARA_PROJECT_SLUG=openclaw \
npx snipara-openclaw-install --yes

The legacy --api-key flag remains supported for compatibility, but the CLI prints a warning because command-line secrets can leak through shell history or process lists.

What It Does

1. Resolves the project slug from --slug, SNIPARA_PROJECT_SLUG, existing OpenClaw config, git remote, or the current folder.
2. Resolves the API key from --api-key, SNIPARA_API_KEY, existing .mcp.json, existing OpenClaw config, or a hidden prompt.
3. Writes .mcp.json with the hosted HTTP MCP endpoint https://api.snipara.com/mcp/<slug>.
4. Writes ~/.openclaw/openclaw.json env values: SNIPARA_API_KEY and SNIPARA_PROJECT_SLUG.
5. Installs the native OpenClaw plugin with openclaw plugins install npm:snipara-openclaw-hooks.
6. Prints the exact openclaw hooks enable ... commands for the remaining internal hooks (snipara-session, snipara-bootstrap).
7. Optionally tests hosted MCP with tools/list.
8. Prints restart and runtime verification guidance.

Files that contain API keys are written with mode 600 where the platform supports POSIX file modes.

Options

| Option | Description | | ------------------------ | ---------------------------------------------------------------- | | --slug <slug> | Project slug | | --project <slug> | Alias for --slug | | --api-key <key> | Existing key; prefer SNIPARA_API_KEY for secret hygiene | | --base-url <url> | Snipara API base URL | | --skip-mcp | Do not write .mcp.json | | --skip-openclaw-config | Do not update ~/.openclaw/openclaw.json | | --skip-hooks | Do not install hooks | | --enable-hooks | Run openclaw hooks enable ... for the supported internal hooks | | --skip-test | Skip hosted MCP connectivity test | | --dry-run | Print planned files and commands without writing or executing | | -y, --yes | Accept defaults in non-interactive mode |

Verification

After installation, restart OpenClaw or the OpenClaw gateway. The install can prove that the files were written and hosted MCP is reachable, but the current OpenClaw process may not reload new MCP servers or hooks until restart.

npx snipara-openclaw-hooks status
openclaw hooks list --verbose
openclaw plugins inspect snipara-openclaw-hooks --runtime --json

If OpenClaw prints no output for hooks enable or hooks list, use npx snipara-openclaw-hooks status to verify local files and then restart the gateway before testing a new session.

Release Notes

This package is an active npm release surface when OpenClaw-specific onboarding changes are shipped. Publish it together with compatible changes to snipara-openclaw-hooks, create-snipara, docs, or hosted API contracts when those surfaces depend on one another.