Snipara
Menu
Docs / Getting Started

Get started in your project folder.

Choose shared project knowledge with Project Brain, or add saved plans and checkpoints with Companion. Both connect to your project’s Snipara MCP.

Primary path
For LLM agents: use Hosted MCP
This path is for Claude Code, Codex, Cursor, Gemini CLI, Mistral, VS Code, ChatGPT Desktop, and other MCP-compatible assistants.

Choose your starting point

Project Brain

Shared sources, decisions and memory in your coding client. Start with the minimal Hosted MCP setup.

npx create-snipara@latest
Connect and verify your first source

Companion

Project knowledge plus local workflow plans, phases and checkpoints you can resume with another agent.

npx create-snipara@latest --profile hosted-companion
Save and resume your first workflow

To switch agents, give the next client access to the same project folder, saved .snipara state and referenced artifacts, and configure its access to the project’s Snipara MCP.

Prerequisites

Node.js 18 or later, an existing project folder, and a supported coding client.

01

Open your existing project

In a terminal, go to the root folder your coding agent already uses. A README or project document should be present so you can verify the first answer.

02

Run the guided setup

Run npx create-snipara@latest. Choose your coding client, then sign in or use an existing Snipara API key.

03

Restart your client

Open a new agent session after setup. The client should now expose Snipara MCP tools for this project.

npx create-snipara@latest

Expected result

Setup confirms the Snipara project, writes the selected client configuration, and starts indexing available project context. After you restart the client, ask it to run snipara_help. A tool list or help response confirms the MCP connection.

First sourced answer

Ask a question you can verify in the README.

In your coding client, ask:

Use Snipara to answer: What command does this project use to run its test suite? Cite the source file and section you used.
  1. Open the cited README or project document.
  2. Confirm that the command and section match the source.
  3. If the answer has no source, ask the agent to use snipara_context_query.

Success means the answer is backed by indexed project context. Installation alone is not the finish line.

If it does not work

Diagnose the same client and project folder.

No Snipara tools

Restart the client, then run npx create-snipara@latest doctor --client <client>.

401 or permission error

Check that the API key belongs to the configured project, then rerun setup.

No sourced answer

Let indexing finish, then retry with a question whose answer is clearly present in the README.

Open full troubleshooting
Next steps

Last updated: September 24, 2026