OpenClaw Integration

OpenClaw support is specialized local automation around the main Snipara surfaces. Connect agents through Hosted MCP first, then add OpenClaw-specific hooks only when needed.

Developer tooling only

Advanced package and testing surface

OpenClaw packages are adapters. They should not be presented as an equivalent third way to connect to Snipara.

Archived package

snipara-openclaw-install is archived. It overlapped with create-snipara while implementing a narrower subset of setup behavior, which created unnecessary package sprawl and documentation confusion.

Recommended Setup

Step 1: Hosted MCP setup

npx create-snipara

This scaffolds the hosted Snipara setup. If you want code execution as well, it can also install optional snipara-sandbox.

Step 2: OpenClaw-specific hooks

npx snipara-openclaw-hooks install

Use these hooks when you want OpenClaw-specific session automation, persistent memory, and shared team context across agents.

What Each Package Does

Package	Role	Recommended?
`create-snipara`	Core setup and onboarding for Snipara MCP, optionally with Snipara Sandbox	Yes
`snipara-openclaw-hooks`	OpenClaw-specific automation hooks	Yes
`snipara-openclaw-install`	Legacy onboarding wrapper	Archived
`snipara-openclaw`	Legacy or external broader integration surface	Not the primary path

Why This Changed

create-snipara already covers the base setup story much better.
snipara-openclaw-hooks is the clearest specialized surface that remains useful for OpenClaw.
Reducing overlapping onboarding packages makes install guidance and public docs much easier to understand.

OpenClaw Hooks

The hooks package supports flows like:

npx snipara-openclaw-hooks install snipara-persist snipara-stop

npx snipara-openclaw-hooks list

npx snipara-openclaw-hooks status

When to Use OpenClaw Hooks

Scenario	Recommendation
Solo agent	Usually only install the smallest useful hook set
Multi-agent team	Use the full hooks package for shared context and memory
General Snipara setup without OpenClaw automation	Use only `snipara-mcp` or `create-snipara`