Set Up Snipara with create-snipara and snipara-business
A first-day setup guide for direct customers and partners: connect Context + Memory, open GitHub automation for code repos, prepare business context with snipara-business, and validate one real workflow.
Alex Lopez
Founder, Snipara
- Readable in 8 minutes
- Published 2026-04-27
- 7 context themes covered
A new Snipara workspace does not need a two-week migration project. The fastest path is to connect the LLM first, then use the right onboarding package for the first real workspace:create-snipara for Context + Memory and GitHub-backed code projects, or snipara-business when the first job is company context, proposals, or RFP work.
Key Takeaways
- Start with auth and MCP so Claude, Codex, Cursor, or another client can use Snipara without dashboard handholding.
- Use GitHub automation for code when the current folder has a GitHub remote.
- Use snipara-business for business context so old offers, decks, templates, diagrams, and current client truth are separated correctly.
- Validate with one real task before uploading the whole company archive.
The Two Entry Points
Code or general agent setup
Creates or reuses the free Context + Memory account, writes Hosted MCP config, and can open GitHub App automation with --github.
Business-first workspace
Runs the same account setup when needed, then prepares company and mission context from local, Drive, or SharePoint-synced folders.
The 30-Minute Plan
| Time | Action | Outcome |
|---|---|---|
| 0-5 min | Run npx create-snipara | Account, Context + Memory, and Hosted MCP config are ready |
| 5-12 min | For code, run npx create-snipara --github | The GitHub App setup opens with repo and branch carried through |
| 12-18 min | For business, run npx snipara-business init | Company context and mission manifest prompts are created |
| 18-24 min | Review the first sync surface | Noisy files, stale exports, and historical precedent are kept out of current truth |
| 24-30 min | Run one real agent task | You validate retrieval and memory before scaling uploads |
What to Add First
Business first batch
- Business Response Playbook
- one core methodology document
- one or two offer templates
- one company presentation
- one reference diagram set
Code first batch
- GitHub repository via
--github - README and architecture notes
- schema or migration rules
- deployment or runbook docs
- coding standards and review checklist
What to Test Immediately
- Business query: “Use the current client project and reusable context to outline the response structure for this RFP.”
- Code query: “Explain how auth works in this repo and which files own the checkout path.”
- Health check: verify whether uploaded files are fresh, parsed correctly, and available after reindex.
Do not optimize the whole workspace on day one. First prove that one real code or business workflow benefits from the setup. Scale uploads after that.