
Synapse Layer — Zero-Knowledge Memory
io.github.SynapseLayerPublished by GitHub account SynapseLayerv1.0.7Updated Oct 24, 2026
Zero-Knowledge Context™ & Neural Handover™ for AI Agents. The Trust Layer for AI Memory.
The publisher's own server: Memory.fit
Overview
Gives an assistant persistent, encrypted long-term memory with semantic recall and cross-agent context handover.
- What you can do
- Synapse Layer is a persistent memory layer for AI agents. It exposes 13 MCP tools covering memory capture, semantic recall, structured storage, feedback scoring, agent handoff, and operational reporting, including recall, save_memory, store_memory, list_memories, memory_feedback, neural_handover, and slo_report. Memories are encrypted at rest with AES-256-GCM and indexed for semantic search, and the README states they can be saved in one agent and recalled in another.
- When to use it
- Worth adding when an assistant should remember user preferences, facts, and earlier decisions across sessions, or when several agents need to share context. It also suits teams wanting searchable, scored recall for production agents rather than per-session statelessness.
- Requirements
- Runs as a local stdio process, installed from PyPI as synapse-layer and launched with uvx. The README also shows a remote Forge endpoint reached through mcp-remote with an x-connect-token header, and a Python SDK using a connect token. Environment variables include SYNAPSE_AGENT_ID, LOG_LEVEL, SYNAPSE_PRIVACY_EPSILON, and the secret SYNAPSE_ENCRYPTION_KEY, which is auto-generated if unset. Network access is needed for the hosted Forge service.
Installation
In SourceWeft
- Open Synapse Layer — Zero-Knowledge Memory in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
🧠 Synapse Layer
RAG retrieves. Synapse remembers.
Persistent memory infrastructure for AI agents — AES-256-GCM encrypted at rest, semantic search, MCP-native.
Synapse Layer is open-source persistent memory infrastructure for AI agents and assistants. Memories are encrypted at rest with AES-256-GCM, indexed via pgvector HNSW for semantic recall, and exposed through MCP JSON-RPC for native integration with Claude, GPT, Gemini, and any MCP-compatible client. Apache 2.0 licensed.
[PyPI] [Python] [Downloads] [MCP Compatible] [Official MCP Registry] [CI] [License: Apache-2.0] [Smithery]
⚡ 30-Second Quickstart
Get your Connect Token at forge.synapselayer.org → Connect, then install into any MCP client:
On the Forge dashboard the Smithery card already copies the command with your token embedded (… | bash -s -- sk_connect_…) — a single paste in your terminal is enough.
Or use the Python SDK:
Get your token at forge.synapselayer.org → Dashboard → Connect
What is Synapse Layer?
The persistent memory layer for AI agents — the missing piece between stateless LLMs and real continuity of context.
Your AI agents forget everything between sessions. Synapse Layer fixes that.
Why Synapse Layer?
Your AI agents forget everything between sessions. Synapse Layer fixes that — in one line.
Use Cases
- Long-term assistant memory — persist user preferences, facts, and prior decisions across sessions.
- Cross-agent continuity — save context in one agent and recall it in another.
- Secure memory for MCP clients — connect Claude Desktop, Cursor, and other MCP-compatible tools to a governed memory layer.
- Operational memory for teams — maintain structured context, trust scoring, and searchable recall for production agents.
Install
Quick Start
Python Script
With Context Manager
Get your token at forge.synapselayer.org → Dashboard → Connect
13 MCP Tools at a Glance
Synapse Layer currently exposes 13 MCP tools for persistent memory workflows:
recallsave_to_synapseprocess_textsearchhealth_checkinitialize_contextsave_memorystore_memoryrecall_memorylist_memoriesmemory_feedbackneural_handoverslo_report
These tools cover memory capture, semantic recall, structured storage, feedback loops, agent handoff, and operational observability.
Deployment Modes
Python Script Mode
Use the SDK when you want direct Python access to Forge memory from your application.
Best for:
- prototypes and scripts
- Python-native workflows
- fast integration into existing apps
Cloud / Forge API
Use Forge when you need persistent, cross-session, and cross-agent memory with managed access tokens.
Best for:
- production assistants
- multi-agent systems
- MCP-based integrations
- shared memory across tools and sessions
MCP Integration (one tested path per client)
Claude Code (CLI)
The URL is a positional argument — claude mcp add --transport http <name> <url> — there is no --url flag.
Claude Desktop
Add to claude_desktop_config.json:
Cursor
Add to .cursor/mcp.json in your project root (same JSON block as above).
Any MCP client
Any host that runs npx can use the mcp-remote block above unchanged — it bridges local stdio to the remote endpoint.
Config file locations:
- Claude Desktop — macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Claude Desktop — Windows:
%APPDATA%\Claude\claude_desktop_config.json - Claude Desktop — Linux:
~/.config/Claude/claude_desktop_config.json
API — Header-First Auth
Security
See SECURITY.md for vulnerability reporting.
Related Projects
Governance
- All public claims follow the Public Claims Matrix.
- Architecture details that reveal benefits are public; mechanisms that enable them are private.
- Claim = Reality. If it's not implemented, it's not in the README.
License
Apache-2.0 © Synapse Layer
Source: README.md at commit 96d0706
Tools
0Version history
1- v1.0.7LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Memory integrations

Memory.fit
fit.memoryOfficial publisher
Hosted Memory.fit server that lets an AI read your training, sleep, recovery and nutrition data and write back weekly plans, targets and meal plans.
pg.ddx.io: the PostgreSQL community's memory
io.ddx.pgOfficial publisher
pg.ddx.io: the PostgreSQL community's memory's hosted MCP server, published by pg.ddx.io; no sign-in required; Streamable HTTP; 29 tools.
var.gg Naming Memory
gg.varOfficial publisher
Remote MCP server that suggests and searches code identifier names from domain concepts in Korean, Japanese, Chinese, Vietnamese and English, and exposes ERD…

Counterparts
ai.counterparts
Local-first long-term memory for Claude Code and Claude Desktop: the assistant writes notes about you and your projects and recalls them in later sessions.

LAHZE - Persian AI Memory Platform
Published by GitHub account pedramgholizadeh
LAHZE - Persian AI Memory Platform's hosted MCP server; no sign-in required; Streamable HTTP; 13 tools.