Claude Desktop Integration
Give Claude persistent, encrypted memory in 3 steps. Every conversation builds on previous context — preferences, decisions, and project history are remembered across sessions.
Overview
Claude Desktop supports the Model Context Protocol (MCP), allowing Claude to use external tools. By connecting Synapse Layer, Claude gains 13 memory tools including store_memory, recall_memory, and search.
The tested setup uses the mcp-remote bridge — a small local stdio process that proxies Claude Desktop to the hosted Synapse Layer endpoint and carries your Connect Token in the auth header.
Setup (mcp-remote bridge)
Edit claude_desktop_config.json and add this server:
{
"mcpServers": {
"synapse-layer": {
"command": "npx",
"args": [
"mcp-remote",
"https://forge.synapselayer.org/api/mcp",
"--header",
"x-connect-token: sk_connect_YOUR_TOKEN"
]
}
}
}Note
sk_connect_YOUR_TOKEN with your actual Connect Token from forge.synapselayer.org → Dashboard → Connect. Requires Node.js 18+ (npx ships with it).Verify It Works
After restarting Claude Desktop, ask Claude:
"Run health_check to verify Synapse Layer is connected."
Then test memory storage:
"Remember that I prefer concise, technical responses with code examples."
In a new conversation, ask Claude to recall your preferences — it will retrieve the stored memory.
Usage Tips
- ▸Explicit save — Tell Claude "save this to memory" for important decisions or preferences
- ▸Cross-session recall — Start new conversations with "recall my project context" to load previous state
- ▸Agent isolation — each Connect Token is scoped to one agent; generate separate tokens per project in Dashboard → Connect
- ▸PII safety — Sensitive data (emails, phone numbers, IPs) is automatically detected and redacted before storage