genesys-memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The HTTP URL of the Genesys MCP server (e.g., http://localhost:8000/mcp) |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| memory_storeA | Store a new memory in the causal memory graph. Use |
| memory_amendA | Record a correction: creates a new memory that supersedes an existing one. The old memory is kept (decayed in recall results), not deleted. |
| memory_recallC | Recall memories using hybrid search (vector + keyword + graph spreading activation). |
| memory_searchA | Filtered vector search by status, category, date, or entity. Pass an EMPTY query to enumerate by recency instead (no vector search, no embedder needed): with since/active_since this answers 'what's new/changed since ' without knowing what to query for. |
| memory_traverseB | Traverse the memory graph from a starting node. Returns reachable nodes AND the edges of the induced subgraph among them (source/target/type/weight/created_by) — a superset of the BFS tree, so paths can be reconstructed. |
| memory_explainC | Explain a memory's score breakdown. |
| pin_memoryC | Pin a memory to core status. |
| unpin_memoryB | Unpin a memory and re-evaluate core eligibility. |
| list_core_memoriesA | List all core memories, optionally filtered by category. |
| delete_memoryA | Permanently delete a memory node and all its edges. |
| memory_statsC | Get graph statistics. |
| set_core_preferencesC | Configure core memory category preferences. |
| promote_to_orgB | Promote a private memory to org visibility. Caller must own the node and belong to the target org. |
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
Each tool targets a distinct operation: store, amend, recall, filtered search, graph traversal, explanation, pinning, unpinning, deletion, stats, preferences, and visibility promotion. memory_recall and memory_search are clearly differentiated as hybrid retrieval versus structured filtering/enumeration.
The memory_* prefix is used consistently for several core operations, but other tools switch to verb_memory forms (pin_memory, delete_memory), noun-like names (memory_stats), or unrelated forms (list_core_memories, set_core_preferences, promote_to_org). The naming is readable but not a uniform verb_noun pattern.
Thirteen tools is well within the ideal range for a memory graph server. Each tool covers a meaningful lifecycle or administrative function without unnecessary redundancy.
The tool set covers the full memory lifecycle: create, read via multiple retrieval modes, amend/supersede, pin/unpin, delete, and administrative operations like stats and preferences. Graph traversal and explanation tools add strong domain coverage with no obvious dead ends.