Sniparaproject brain
Menu
Product
Context layerProject context and memory for coding agents without a new chat surface.Project BrainDefinition, boundaries, and the project state an agent starts from.60s demoWatch a cold ACME agent become a briefed agent before the first edit.Proof replaySee what changes when the agent starts from reviewed project state.InstallConnect the hosted MCP endpoint to the agent you already use.Agent surfacesHow the same Project Brain reaches the coding agents teams already use.
Developers
QuickstartConnect an AI coding agent in minutes.Project Brain modelWhat changed, why, impact, next step, safety.Hosted MCPTool contracts for agent clients.API ReferenceProgrammatic context and project intelligence access.GitHub AppRepository sync and PR Answer Packs.Multi-agentCoordinate swarms, claims, state, events and htasks.Snipara SandboxRepeatable execution when validation needs proof.Companion CLIWorkflow continuity for long agent work.
ProofPhilosophyPricingDocs
Sign inStart Free

OpenClaw Integration

Prefer OpenClaw's native Snipara plugin path. Hosted MCP supplies project context; optional npm packages add guided setup or lifecycle hooks when your OpenClaw workflow needs them.

Primary path
For LLM agents: use Hosted MCP
Start with the native plugin and Hosted MCP. Add hook automation deliberately instead of treating every local package as mandatory.

Package status

SurfaceCurrent roleStatus
Native OpenClaw pluginPreferred integration pathRecommended
snipara-openclaw-installGuided onboarding wrapperPublished on npm
snipara-openclaw-hooksOpenClaw-specific lifecycle automationPublished on npm

No archived-package claim

The npm registry does not mark snipara-openclaw-install as deprecated. It may overlap with the preferred native plugin, but overlap is not the same as archival. This page will only call the wrapper deprecated after its distribution metadata says so.

Recommended setup

  1. Install and enable the native Snipara plugin in OpenClaw.
  2. Connect the plugin to the project-scoped Hosted MCP endpoint.
  3. Keep the project API key in OpenClaw's local secret mechanism.
  4. Add snipara-openclaw-hooks only when you need explicit lifecycle automation.

Optional guided installer

npx -y snipara-openclaw-install@latest

Review what the installer will write before accepting changes, especially when an existing OpenClaw or Snipara configuration is already present.

Related guides