Declade/lucairn-sdks

Official client libraries for **Lucairn** — an EU-based privacy-preserving AI gateway. Lucairn sits between your application (or AI agent) and the upstream LLM provider you choose, removes personal data from prompts before the model ever sees them, and returns a signed Lucairn Certificate proving what was redacted, when, and by which sanitizer layer.
This monorepo hosts four packages at parity:
- **@lucairn/mcp-server** — Model Context Protocol server (one-line npx install for Claude Desktop, Cursor, Cline, Continue, …)
- **@lucairn/sdk** — TypeScript / Node SDK
- **lucairn** — Python SDK
- **github.com/declade/lucairn-sdks/go** — Go SDK
Quick start (MCP)
For most agent use cases, the fastest path is the MCP server. No build step, no install — npx runs it on demand:
Add it to your MCP client config (Claude Desktop's claude_desktop_config.json, Cursor's mcp.json, Cline's cline_mcp_settings.json, Continue, etc.):
Restart your client. The chat_via_lucairn tool becomes available immediately. See mcp-server/README.md for full details.
What it does
Each request through any Lucairn SDK follows the same pipeline:
1. **PII detection** runs on every user message in three layers:
- **Layer 1** — Known-entity matching (your tenant's named entities)
- **Layer 2** — Presidio NER (names, emails, IBANs, addresses, phone numbers, customer IDs, …)
- **Layer 3** — GPU-hosted custom-trained PII shield (**Enterprise tier only**, optionally trained on your domain corpus)
2. Detected PII is replaced with placeholders ([PERSON_1], [EMAIL_2], [IBAN_3], …) **before** the request reaches the upstream LLM.
3. The selected upstream model sees only the sanitized text. It never receives raw personal data.
4. The response is returned with a signed compliance certificate (Ed25519 witness signature + RFC 3161 timestamp + Sigstore Rekor inclusion proof).
5. **Response handling depends on tier:**
- **Developer (free)** — placeholders are returned verbatim. Useful for testing the redaction surface.
- **Pro / Enterprise** — placeholders are re-linked back to the originals on the gateway before the response reaches your application.
For Lucairn-hosted Developer-tier callers, on-gateway pseudonymization happens before your LLM sees the request. Enterprise self-host deployments can run the entire stack inside the customer environment, in which case no raw identity data leaves that environment at all.
Provider routing
The gateway picks the upstream provider from the model parameter you send:
| Model prefix | Upstream provider | BYOK env var |
|------------------------------------------------------|-------------------|---------------------|
| claude-*, anthropic-* | Anthropic | ANTHROPIC_API_KEY |
| gpt-*, openai-*, o1-*, o3-*, o4-* | OpenAI | OPENAI_API_KEY |
Cross-provider BYOK shipped in @lucairn/mcp-server@1.1.0 — set one or both keys in the same MCP config and the server forwards the matching one as X-Upstream-Key per request, so your provider account is billed directly.
Per-language SDKs
| Language | Package | Version | README |
|----------------|-------------------------------------------|---------|-------------------------------------|
| MCP server | @lucairn/mcp-server | 1.2.7 | mcp-server/README.md |