Synapse Layer — Continuous Consciousness Infrastructure
Give Claude Code or Cursor a persistent, encrypted memory layer so long-running agent work survives sessions without leaking PII to the host.
Overview
Synapse Layer is an MCP server for the Build phase that provides persistent zero-knowledge encrypted memory and PII-safe recall for coding agents.
What is this MCP server?
- Persistent zero-knowledge memory with AES-256-GCM at-rest encryption
- Built-in PII redaction and differential privacy via SYNAPSE_PRIVACY_EPSILON (0.1–2.0)
- stdio via uvx/PyPI or remote streamable HTTP at forge.synapselayer.org
- Agent-scoped storage with SYNAPSE_AGENT_ID and optional auto-generated SYNAPSE_ENCRYPTION_KEY
- Continuous consciousness / Neural Handover style context across sessions
- Server version 1.1.5 in manifest
- Default SYNAPSE_PRIVACY_EPSILON 0.5 (range 0.1–2.0)
- Transport: stdio (PyPI synapse-layer) plus remote streamable-http
Community signal: 9 GitHub stars.
What problem does it solve?
Agents forget everything when a session ends, and plain memory plugins store sensitive text where you cannot control encryption or redaction.
Who is it for?
Indie builders running multi-day agent workflows on client or regulated data who need encrypted, agent-scoped memory via MCP.
Skip if: Teams that only need ephemeral chat context or a simple local notes file without encryption setup.
What do I get? / Deliverables
After you register Synapse Layer, agents can store and retrieve context under AES-256-GCM with redaction and privacy knobs instead of stuffing secrets into chat history.
- Encrypted persistent memory store per agent ID
- PII-redacted recall usable across MCP tool calls
- Configurable privacy epsilon for memory queries
Recommended MCP Servers
Journey fit
Memory infrastructure sits in the build phase because you wire it while assembling agent stacks, before you ship customer-facing automation. agent-tooling is the canonical shelf for MCP servers that extend what coding agents remember and hand off between runs.
How it compares
MCP memory infrastructure with crypto and privacy controls, not a general-purpose vector database skill.
Common Questions / FAQ
Who is Synapse Layer for?
Solo and small-team builders who use Claude Code, Cursor, or other MCP clients and want durable agent memory without exposing PII in plaintext.
When should I use Synapse Layer?
Use it while building agent-powered products or internal tools whenever sessions must resume with prior decisions, handoffs, or user-specific context.
How do I add Synapse Layer to my agent?
Add the stdio server with uvx synapse-layer (PyPI) and set SYNAPSE_AGENT_ID; optionally SYNAPSE_ENCRYPTION_KEY and SYNAPSE_PRIVACY_EPSILON, or point your client at the remote MCP URL from the server manifest.