Synapse Layer — Trust Infrastructure for AI Agents
RemoteAbout Synapse Layer — Trust Infrastructure for AI Agents
Synapse Layer is persistent, encrypted memory infrastructure for AI agents and assistants. It provides semantic recall and Trust Quotient scoring, with memory shared across sessions and MCP-compatible clients.
Key features
- 01AES-256-GCM 加密存储
- 02跨会话语义记忆检索
- 03跨 Agent 共享记忆
- 04Trust Quotient 置信度评分
- 05提供 13 个 MCP 工具
Use cases
- 01跨会话保存用户偏好和决策
- 02在不同 Agent 间延续上下文
- 03为 MCP 客户端提供加密记忆
- 04为生产 Agent 检索结构化记忆
MCP support
通过 MCP JSON-RPC 暴露 13 个记忆相关工具,供兼容客户端保存、搜索和检索记忆。
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://forge.synapselayer.org/api/mcpclaude mcp add --transport http synapselayer-synapse-layer https://forge.synapselayer.org/api/mcp{"mcpServers":{"synapselayer-synapse-layer":{"type":"http","url":"https://forge.synapselayer.org/api/mcp"}}}Open in Cursor{"servers":{"synapselayer-synapse-layer":{"type":"http","url":"https://forge.synapselayer.org/api/mcp"}}}Open in VS Code{"mcpServers":{"synapselayer-synapse-layer":{"type":"http","url":"https://forge.synapselayer.org/api/mcp"}}}{"mcpServers":{"synapselayer-synapse-layer":{"serverUrl":"https://forge.synapselayer.org/api/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://forge.synapselayer.org/api/mcpAuth requiredTools
13| Parameter | Type | Required | Description |
|---|---|---|---|
| mode | enum | No | Recall routing mode. "temporal" = pure chronological, "semantic" = FTS + TQ ranking, "priority" = critical/high-TQ first, "hybrid" = weighted blend, "auto" = detect from query (default).auto | temporal | semantic | priority | hybrid |
| limit | number | No | Maximum memories to return (1–50, default: 10). |
| query | string | Yes | What to recall — natural language query for memory retrieval. |
| scope | enum | No | Explicit memory scope. "agent" (default, fail-closed) = limits recall to the given agent_id (or the token agent). "tenant" = cross-agent recall within the authenticated tenant. If omitted with agent_id present, "agent" is inferred; if both omitted, the token agent is used (verified-token scope).agent | tenant |
| reason | string | Yes | REQUIRED (10–200 chars). Audit policy: MEMORY_EXPORT_GOVERNANCE_V1. Human-readable justification for retrieving PLAINTEXT memory. Without this parameter the call WILL fail with code -32602. Example: "User asked me to summarize last week decisions." |
| subject | string | No | ESCOPO1 (optional): opaque 8-128 char token ([A-Za-z0-9._:-]) that isolates memory to a single person within a shared connect-token. Omit for token-scoped behavior. Never include PII/email. |
| agent_id | string | No | Agent identifier (canonical or alias). Used only when scope="agent" or scope is inferred. |
Details
From the project 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.
⚡ 30-Second Quickstart
Get your Connect Token at forge.synapselayer.org → Connect, then install into any MCP client:
curl -fsSL https://forge.synapselayer.org/install/smithery | bash
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:
from synapse_layer import Synapse
s = Synapse(token="sk_connect_YOUR_TOKEN")
s.store("user likes coffee")
print(s.recall("what does user like?"))
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.
| Feature | Description |
|---|---|
| 🔐 Encrypted at rest | AES-256-GCM with per-operation random IV and HMAC-SHA-256 integrity |
| 🧩 One-click connect | Claude Desktop, Cursor, LangChain, CrewAI, n8n |
| 🌐 Cross-agent memory | Save in ChatGPT, recall in Claude |
| ⚡ MCP-native | Any MCP-compatible agent |
| 🔒 Header-first auth | Tokens never in URLs or logs |
| 🎯 Trust Quotient | Deterministic recall — memories ranked by confidence, not recency alone |
Why Synapse Layer?
Your AI agents forget everything between sessions. Synapse Layer fixes that — in one line.
| Without Synapse Layer | With Synapse Layer |
|---|---|
| Agent forgets context every session | Persistent memory across all sessions |
| Memory locked to one model | Cross-agent: save in ChatGPT, recall in Claude |
| No audit trail | Trust Quotient scoring on every memory |
| Complex integration | pip install synapse-layer + 3 lines of code |
| Plaintext stored on servers | AES-256-GCM encrypted at rest |
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
pip install synapse-layer
Quick Start
Python Script
from synapse_layer import Synapse
client = Synapse(token="sk_connect_YOUR_TOKEN")
# Store
client.store("User prefers dark mode and concise answers")
# Recall
results = client.recall("user preferences")
for r in results:
print(r["content"], r["trust_quotient"])
With Context Manager
from synapse_layer import Synapse
with Synapse(token="sk_connect_YOUR_TOKEN") as client:
client.store("User prefers dark mode and concise answers")
results = client.recall("user preferences")
for r in results:
print(r["content"])
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)
claude mcp add --transport http synapse-layer \
https://forge.synapselayer.org/api/mcp \
--header "x-connect-token: sk_connect_YOUR_TOKEN"
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:
{
"mcpServers": {
"synapse-layer": {
"command": "npx",
"args": [
"mcp-remote",
"https://forge.synapselayer.org/api/mcp",
"--header",
"x-connect-token: sk_connect_YOUR_TOKEN"
]
}
}
}
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
# Health check
curl -H "x-connect-token: sk_connect_YOUR_TOKEN" \
https://forge.synapselayer.org/api/connect/health
# Save memory
curl -X POST \
-H "x-connect-token: sk_connect_YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"content": "User is a Python developer"}' \
https://forge.synapselayer.org/api/v1/capture
Security
| Feature | Implementation |
|---|---|
| Encryption | AES-256-GCM at rest with per-operation random IV |
| Integrity | HMAC-SHA-256 on content |
| Auth | Header-first (x-connect-token) — tokens never in URLs or logs |
| Privacy | Content sanitization + tenant-scoped encrypted storage |
| Isolation | 1 user = 1 tenant = 1 private mind |
See SECURITY.md for vulnerability reporting.
Related Projects
| Project | Description |
|---|---|
| synapse-sdk-python | Python SDK — LangChain, CrewAI, and A2A protocol adapters |
| synapse-layer-skill | MCP skill configuration for Claude Desktop, Cursor, Windsurf |
| synapse-layer-langgraph | LangGraph checkpoint saver with encrypted state persistence |
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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.