Developer Packages

Most users should start with create-snipara to connect Context + Memory. Hosted MCP remains the agent surface; snipara-companion is the Git-style continuity surface for local agent work; API / SDK remains the software surface.

Primary path

For LLM agents: use Hosted MCP

Do not start package selection by asking whether to install snipara-mcp. Start by connecting the agent to Hosted MCP.

Primary path

For product integration: use API / SDK

Use SDKs and REST contracts when Snipara is part of your product, backend, or data pipeline.

Default Recommendation

For LLM agents: use Hosted MCP.
For product integration: use API / SDK.
Use create-snipara for Context + Memory onboarding, auth, local config, and doctor checks.
Use snipara-companion for day-two agent workflows: status, briefs, timelines, phase commits, handoffs, and resume.
Use snipara-orchestrator only when production validation, htasks, or explicit multi-agent coordination are required.
Only install specialized packages when you already know you need them.

Quick Matrix

Package	Use it for	Audience	Status
`snipara-mcp`	Local stdio bridge, client package development, advanced MCP testing	Developers and compatibility users	Developer tooling
`create-snipara`	Context + Memory onboarding, free signup, local config generation, doctor, repair, companion workflow setup	Users who want a simple agent connection path	Onboarding
`snipara`	Python SDK, programmatic workflows, config-driven Python integration	App and backend developers	API / SDK
`snipara-memory`	Standalone memory engine when memory itself is the product you want	Specialized teams and OSS adopters	Specialized
`snipara-orchestrator`	Production-first validation, proofs, drift detection, htasks, advanced agent workflows	Advanced teams	Advanced
`snipara-sandbox`	Sandboxed code execution layer that complements Snipara	Users who need execution, not just context	Adjacent
`snipara-openclaw-hooks`	OpenClaw-specific hook automation	OpenClaw users	Specialized
`snipara-companion`	Git-style local continuity CLI: status, brief, timeline, phase commits, handoffs, resume, and hook-oriented workflows	Users who want managed agent work state across sessions and tools	Default helper
`snipara-openclaw-install`	Legacy OpenClaw onboarding wrapper	None for new installs	Archived

Choose by Use Case

MCP for Codex, Claude Code, Cursor, ChatGPT, Gemini, VS Code

Start with create-snipara when the user wants guided onboarding and auth. Start with Hosted MCP directly when they already have the project slug and API key. Use local snipara-mcp only when the client needs stdio, you want browser-login compatibility testing, or you are developing MCP client behavior.

Continuity for agent sessions

Use snipara-companion status, brief, timeline, workflow phase-commit, handoff, and workflow resume when the agent needs a durable work log rather than just a one-time MCP connection.

Codex specifically

Use Hosted MCP config plus AGENTS.md. create-snipara installs snipara-companion by default for compaction-safe workflow commands, but local snipara-mcp is only needed for stdio compatibility, development, or tests.

Business workflows

Use Helvabase for RFP, proposal, client dossier, and reviewed business-source workflows. Snipara package docs stay focused on developer and agent integration.

Python application integration

Use the REST API or snipara SDK. Do not route product backend work through a local agent helper flow.

Production validation and orchestration

Use snipara-orchestrator only if you need proof-based validation and production drift detection, or if you are intentionally coordinating hierarchical tasks across agents. It is an advanced package, not the default install path, and it is not bundled into npx create-snipara --profile full-stack.

Companion vs orchestrator

Do not merge snipara-companion and snipara-orchestrator. They solve different problems: companion is a local helper CLI for hook-oriented workflows, while orchestrator is an advanced Python package for production validation, htasks, and orchestration.

OpenClaw

Connect through Hosted MCP first. Use create-snipara only if you want scaffolding, then add snipara-openclaw-hooks for OpenClaw-specific automation. The older snipara-openclaw-install wrapper is archived.

Recommended Paths

Agent Connection

npx create-snipara

Guided free-account, auth, Hosted MCP, context, and memory onboarding.

Agent Continuity

snipara-companion status

Git-style status, briefs, timelines, handoffs, and resume for long-running agent work.

Product Integration

pip install snipara

Use API / SDK contracts for backend-to-backend and application workflows.