Synapse Layer MCP MCP server

An official MCP server providing persistent, encrypted memory for AI agents. It enables agents to store decisions, preferences, and project rules, recall them across sessions, and perform cross-agent handovers, ensuring context continuity and security.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Synapse Layer

MCP endpoint (Streamable HTTP)

https://forge.synapselayer.org/api/mcp

Vendor documentation

What you can do with it

Store user preferences and project rules in encrypted memory
Recall prior decisions and context at the start of new tasks
Hand over project context between different AI agents or sessions

Tools advertised by the last live check:

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

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http synapse-layer-mcp https://forge.synapselayer.org/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add synapse-layer-mcp --url https://forge.synapselayer.org/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable synapse-layer-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "synapse-layer-mcp": {
      "url": "https://forge.synapselayer.org/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "synapse-layer-mcp": {
      "type": "streamableHttp",
      "url": "https://forge.synapselayer.org/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start synapse-layer-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "synapse-layer-mcp": {
      "type": "http",
      "url": "https://forge.synapselayer.org/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http synapse-layer-mcp https://forge.synapselayer.org/api/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "synapse-layer-mcp": {
      "url": "https://forge.synapselayer.org/api/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "synapse-layer-mcp": {
      "serverUrl": "https://forge.synapselayer.org/api/mcp"
    }
  }
}

See all 782

Do you run Synapse Layer MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing