Docs / Integrations

Choose the right connection method.

Snipara has two primary product surfaces. Hosted MCP is for LLM agents. API / SDK is for software systems. Local tooling helps only when a workstation workflow needs it.

Primary path

For LLM agents: use Hosted MCP

Connect Claude Code, Codex, Cursor, Windsurf, ChatGPT Desktop, or any MCP-compatible assistant to https://api.snipara.com/mcp/YOUR_PROJECT_SLUG.

Primary path

For product integration: use API / SDK

Use REST endpoints and SDKs for app backends, bulk upload, sync, provisioning, health, analytics, and client lifecycle workflows.

Recommended path

For agents, use Hosted MCP first.

Use HTTP MCP when the client supports it. Use SSE only when the client requires streaming transport. Local stdio and snipara-mcp are advanced compatibility and testing paths, not the main product promise.

Transport Matrix

Use the project slug consistently across all MCP transports. Pick the transport your client actually supports instead of mixing setup stories.

Project slug

HTTP direct

Recommended

Best when the client accepts plain remote MCP over HTTP and you want the simplest setup.

https://api.snipara.com/mcp/YOUR_PROJECT_SLUG

SSE

Advanced

Use only for clients that explicitly require streaming Server-Sent Events transport.

https://api.snipara.com/mcp/YOUR_PROJECT_SLUG/sse

Local stdio

Local only

Use for stdio compatibility, client package development, and advanced tests powered by uvx snipara-mcp. Prefer Hosted MCP when remote MCP is supported.

SNIPARA_PROJECT_SLUG=YOUR_PROJECT_SLUG

Code Graph v1

In v1, snipara_context_query stays doc-first. It remains the right default for docs, notes, markdown, and narrative context.

For structural code questions, use snipara_code_callers, snipara_code_imports, snipara_code_neighbors, or snipara_code_shortest_path.

Connect with MCP

Primary path for LLM agents and MCP-compatible assistants.

Integrate with API

Primary path for apps, backends, integrators, and pipelines.

create-snipara

Guided free account, auth, Hosted MCP, Context, and Memory onboarding.

AI agent setup

Copy-ready rules and templates for Codex, Claude Code, Cursor, and ChatGPT.

Use Companion locally

Optional helper on top of hosted Snipara.

snipara-business

Business context onboarding and verified mission manifests.

Claude Code

Hosted MCP setup for Anthropic CLI.

Claude Code MCP plugin

Optional plugin layer with slash commands, skills, hooks, and Snipara Sandbox helpers.

ChatGPT / OpenAI

Desktop and API wiring.

OpenClaw

OpenClaw-specific hooks and the recommended Snipara setup for coordinated agents.

Developer packages

Package map for advanced, testing, and compatibility work.

Keep the story simple

LLM agents use Hosted MCP.
Apps, integrators, backends, and pipelines use API / SDK.
Companion is optional local workflow help, not a replacement for MCP or API.
create-snipara is the simple Context + Memory onboarding package.
snipara-business is for business-context onboarding and mission manifest workflows.
snipara-mcp is developer tooling for local stdio, testing, and compatibility.
Code graph questions should go to the `snipara_code_*` tools, not generic docs search.

Common setup

{
  "mcpServers": {
    "snipara": {
      "type": "url",
      "url": "https://api.snipara.com/mcp/YOUR_PROJECT_SLUG",
      "headers": {
        "X-API-Key": "snp-YOUR-API-KEY"
      }
    }
  }
}

If you prefer local stdio, use the same project slug through SNIPARA_PROJECT_SLUG instead of switching to raw IDs.

Integrate with API Companion snipara-business Snipara Sandbox