Synapse Layer — Trust Infrastructure for AI Agents

Official registry Cloud and DevOps

MCP-native Trust Infrastructure for AI Agents. Persistent encrypted memory with Trust Quotient.

What can you do with Synapse Layer — Trust Infrastructure for AI Agents?

  • 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

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http synapse-layer-trust-infrastructure-for-a 'https://forge.synapselayer.org/api/mcp' --header 'x-connect-token: <Connect token for API authentication (sk_connect_*). Obtain via Forge → Dashboard → Connect.>'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "synapse-layer-trust-infrastructure-for-a": {
            "type": "http",
            "url": "https://forge.synapselayer.org/api/mcp",
            "headers": {
                "x-connect-token": "<Connect token for API authentication (sk_connect_*). Obtain via Forge → Dashboard → Connect.>"
            }
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. 🧠 Synapse Layer
  2. ⚡ 30-Second Quickstart
  3. What is Synapse Layer?
  4. Why Synapse Layer?
  5. Use Cases
  6. Install
  7. Quick Start
  8. 13 MCP Tools at a Glance
  9. Deployment Modes
  10. MCP Integration (one tested path per client)
  11. API — Header-First Auth
  12. Security
  13. Related Projects
  14. Governance
  15. License

🧠 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.

Website · Docs · PyPI · Forge


⚡ 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.

FeatureDescription
🔐 Encrypted at restAES-256-GCM with per-operation random IV and HMAC-SHA-256 integrity
🧩 One-click connectClaude Desktop, Cursor, LangChain, CrewAI, n8n
🌐 Cross-agent memorySave in ChatGPT, recall in Claude
⚡ MCP-nativeAny MCP-compatible agent
🔒 Header-first authTokens never in URLs or logs
🎯 Trust QuotientDeterministic 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 LayerWith Synapse Layer
Agent forgets context every sessionPersistent memory across all sessions
Memory locked to one modelCross-agent: save in ChatGPT, recall in Claude
No audit trailTrust Quotient scoring on every memory
Complex integrationpip install synapse-layer + 3 lines of code
Plaintext stored on serversAES-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:

  • recall
  • save_to_synapse
  • process_text
  • search
  • health_check
  • initialize_context
  • save_memory
  • store_memory
  • recall_memory
  • list_memories
  • memory_feedback
  • neural_handover
  • slo_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

FeatureImplementation
EncryptionAES-256-GCM at rest with per-operation random IV
IntegrityHMAC-SHA-256 on content
AuthHeader-first (x-connect-token) — tokens never in URLs or logs
PrivacyContent sanitization + tenant-scoped encrypted storage
Isolation1 user = 1 tenant = 1 private mind

See SECURITY.md for vulnerability reporting.


ProjectDescription
synapse-sdk-pythonPython SDK — LangChain, CrewAI, and A2A protocol adapters
synapse-layer-skillMCP skill configuration for Claude Desktop, Cursor, Windsurf
synapse-layer-langgraphLangGraph 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

Frequently asked questions

What is Synapse Layer — Trust Infrastructure for AI Agents?

MCP-native Trust Infrastructure for AI Agents. Persistent encrypted memory with Trust Quotient.

How do I install Synapse Layer — Trust Infrastructure for AI Agents?

It runs as a remote server. In Claude Code: claude mcp add --transport http synapse-layer-trust-infrastructure-for-a 'https://forge.synapselayer.org/api/mcp' --header 'x-connect-token: <Connect token for API authentication (sk_connect_*). Obtain via Forge → Dashboard → Connect.>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Synapse Layer — Trust Infrastructure for AI Agents need an API key?

Yes. It expects x-connect-token, which you set in its configuration.

Is Synapse Layer — Trust Infrastructure for AI Agents open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains Synapse Layer — Trust Infrastructure for AI Agents?

It is published by SynapseLayer. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.