Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OPENAI_MODELNoModel name for the OpenAI-compatible LLM provider.gpt-4o-mini
SYNAPSE_MODELNoOptional dedicated Synapse endpoint override model name.
OPENAI_API_KEYNoAPI key for the OpenAI-compatible LLM provider. May be left blank for local runners such as Ollama or vLLM.
OPENAI_BASE_URLNoBase URL for any OpenAI-compatible LLM provider (OpenAI, Ollama, vLLM, Groq, etc.).https://api.openai.com/v1
SYNAPSE_API_KEYNoOptional dedicated Synapse endpoint override API key.
SYNAPSE_DB_PATHNoSQLite database location. For the MCP server, defaults to ~/.synapse/synapse.db so all assistants share the same memory pool; set this to isolate memory per project../data/synapse.db
SYNAPSE_BASE_URLNoOptional dedicated Synapse endpoint override for the LLM base URL.
SYNAPSE_VAULT_PATHNoOptional Markdown knowledge base / vault path../vault
SYNAPSE_TOKEN_BUDGETNoContext packing token budget for recall results.250
OPENAI_EMBEDDING_MODELNoOptional OpenAI-compatible embedding model to use for semantic search instead of the default zero-dependency subword vectorizer or sentence-transformers.
SYNAPSE_EMBEDDING_MODELNoOptional embedding model override when using sentence-transformers.all-MiniLM-L6-v2

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
synapse_recallA

Recall memories, SOPs, and past architectural decisions from Synapse Memory Engine using hybrid semantic vector and BM25 search.

synapse_retainB

Save an atomic fact, architectural decision, permanent directive, or SOP into Synapse Memory.

synapse_record_episodeC

Record an episodic learning memory (Situation -> Action -> Outcome -> Lesson) so agents never repeat past mistakes.

synapse_get_statsA

Get real-time statistics and node counts of the Synapse memory cortex.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 4 tools

Disambiguation4/5

The read/write split is clear: synapse_recall and synapse_get_stats are retrieval, while synapse_retain and synapse_record_episode are storage. synapse_retain and synapse_record_episode both write memories, which could be confused, but the descriptions distinguish atomic facts/SOPs from structured Situation-Action-Outcome-Lesson episodes.

Naming Consistency4/5

All tools share the synapse_ namespace prefix and use verb-based names, giving a predictable pattern. Minor deviation: recall and retain are bare verbs while record_episode and get_stats use verb_noun form, but the set still reads consistently.

Tool Count4/5

Four tools is a tight, focused surface for a memory engine, and each one has a distinct role (store fact, store episode, recall, stats). It sits at the low end of the comfortable range, with room for lifecycle operations without feeling padded.

Completeness3/5

Core workflows (store and retrieve memories, check stats) are covered, but the lifecycle is incomplete: there is no update/edit, delete/forget, or list/enumerate operation. For a persistent memory system, the inability to correct or remove outdated facts or SOPs is a notable gap.

Maintenance

ActivityMaintained
ResponsivenessNo issues