← Registry

Developer Tools

synapselayer.org

Provides persistent memory management for AI agents with recall, storage, and search capabilities.

1 endpoint13 known toolsFirst detected June 5, 2026Last detected July 25, 2026

ENDPOINT 1

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

No auth detected

MCP server metadata

Name
synapse-layer
Version
2.4.4
Capabilities
tools
Server instructions

Synapse Layer MCP — persistent memory for AI agents. Authenticate with your x-connect-token to enable memory tools. Get your token at https://forge.synapselayer.org/dashboard/connect

Known tools 13

recall

Retrieve relevant persisted memory using semantic, temporal, priority, or hybrid routing.

Inferred read-only
save_to_synapse

Persist memory with encryption at rest, sanitization, and deduplication controls.

Inferred read-only
process_text

Extract candidate memories from free-form text with governance filters and sanitization.

Inferred read-only
search

Search persisted memory across agent scopes using full-text matching.

Inferred read-only
health_check

Check service availability, engine version, and storage health.

Inferred read-only
initialize_context

Initialize a persistent memory context for a conversation or agent session.

Inferred read-only
save_memory

Save a memory entry to the persistent store.

Inferred read-only
store_memory

Store structured memory with metadata and trust scoring.

Inferred read-only
recall_memory

Recall persisted memory by query.

Inferred read-only
list_memories

List memory metadata with pagination and governance limits.

Inferred read-only
memory_feedback

Submit feedback to adjust trust scoring for stored memories.

Inferred read-only
neural_handover

Transfer contextual state between agents with continuity controls.

Potential side effects
slo_report

Return uptime and SLO metrics for the MCP service.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.synapse-layer]
url = "https://forge.synapselayer.org/api/mcp"
enabled = true
Claude Code

.mcp.json

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

Settings → Connectors → Add custom connector

Name: synapse-layer
Remote MCP URL: https://forge.synapselayer.org/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "synapse-layer": {
      "type": "http",
      "url": "https://forge.synapselayer.org/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "synapse-layer",
  "transport": "streamable-http",
  "url": "https://forge.synapselayer.org/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.