synapse-layer
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| x-connect-token | Yes | Your Synapse Layer connect token (e.g. sk_connect_YOUR_TOKEN), used for header-first authentication. Get your token at https://forge.synapselayer.org → Dashboard → Connect. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| recallA | Retrieve relevant persisted memory using semantic, temporal, priority, or hybrid routing. Governance: requires reason (10–200 chars). Rate limit: 20/min. |
| save_to_synapseA | Persist memory with encryption at rest, sanitization, and deduplication controls. |
| process_textA | Extract candidate memories from free-form text with governance filters and sanitization. |
| searchA | Search persisted memory across agent scopes using full-text matching. Governance: requires reason (10–200 chars) because results contain plaintext content. |
| health_checkA | Check service availability, engine version, and storage health. Public method. |
| initialize_contextA | Initialize a persistent memory context for a conversation or agent session. Returns REDACTED metadata by default (detail="summary"). Use detail="full" with a reason (10–200 chars) to retrieve plaintext content under MEMORY_EXPORT_GOVERNANCE_V1. |
| save_memoryC | Save a memory entry to the persistent store. Alias of save_to_synapse. |
| store_memoryB | Store structured memory with metadata and trust scoring. |
| recall_memoryA | Recall persisted memory by query. Alias of recall. |
| list_memoriesA | List memory metadata with pagination and governance limits. |
| memory_feedbackA | Submit feedback to adjust trust scoring for stored memories. |
| neural_handoverA | Transfer contextual state between agents with continuity controls. |
| slo_reportB | Return uptime and SLO metrics for the MCP service. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
There is overlap between `save_memory` and `save_to_synapse` (aliases), and `recall_memory` and `recall` (aliases), which creates ambiguity. `save_to_synapse` and `store_memory` also have very similar purposes, potentially causing misselection.
Most tools use a verb_noun pattern (e.g., list_memories, save_memory, recall_memory), but `neural_handover` breaks this pattern by using an adjective_noun. `slo_report` is a contraction that doesn't follow the strict verb_noun structure, introducing inconsistency.
With 13 tools, the count is within the well-scoped range (3-15). The presence of aliases inflates the number slightly, but otherwise, each non-alias tool serves a distinct purpose, making the count appropriate.
The tool surface covers core CRUD operations (save, recall, list, search) and lifecycle operations (initialize, feedback, handover). Minor gaps exist, such as missing explicit update or delete tools for memories, but the domain coverage is generally strong.