Snipara
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.Benchmark protocolReview the controlled study, reported results, and public artifact status.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
Docs / Getting Started

Connect your agent. Verify one sourced answer.

Start in the project you already work in. One guided command connects your coding client; one precise question confirms that Snipara can retrieve your project sources.

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.
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
Client-specific setupProject IntelligenceIntegrate an applicationAdvanced profiles