Nexus Memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JINA_API_KEY | No | Jina API key for embeddings (1024d) | |
| GOOGLE_API_KEY | No | Google API key for Vertex AI embeddings (768d) | |
| OPENAI_API_KEY | No | OpenAI API key for embeddings (1536d) | |
| VOYAGE_API_KEY | No | Voyage API key for embeddings (1024d) |
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 |
|---|---|
| rememberC | Store a memory for AI agents. Persists information across sessions. |
| recallA | Search memories. Returns relevant context from past sessions. |
| forgetA | Delete a specific memory by ID. |
| updateB | Update an existing memory in-place without losing metadata. |
| fact_historyA | Trace the supersession chain of a memory: the point itself plus all successors (and predecessors via superseded_by), ordered by valid_from. Shows how a fact evolved over time. |
| healthA | Check if Nexus Memory is running and healthy. |
| subscribeA | Register a webhook URL to receive HTTP POST notifications when a memory event of the given type fires. Returns the subscription id (UUID) which you need to unsubscribe. Subscriptions are stored in ~/.nexus-webhooks.json and survive server restarts. |
| unsubscribeA | Remove a webhook subscription by its id (returned from subscribe). |
| list_subscriptionsA | List all currently registered webhook subscriptions (id, event_type, webhook_url, created_at). |
| backupA | Create a full backup of all memories as JSON file. Includes payloads + vectors. Saved to ~/.nexus-memory/backups/. Runs automatically every 24h - use this for manual backup on demand. |
| restoreA | Restore memories from a backup JSON file. By default reuses stored vectors (zero API cost). Set reembed=true to re-embed with current provider (for provider changes). |
| guardrail_checkA | Active Guardrails: Check if an action is safe before executing it. Queries Nexus Memory for protection rules (category='rule' with protection keywords like 'niemals', 'never delete', 'protected'). Returns allow/block/override verdict. Use before destructive operations (rm, drop, kill, overwrite, recreate). |
| guardrail_overrideA | Active Guardrails: Record a guardrail override with full audit trail. Required when guardrail_check returns 'block' but the action is explicitly authorized. The override is stored as a private session memory entry for audit. Requires explicit reasoning (min 10 chars). |
| graph_traverseA | Knowledge Graph: Multi-hop traversal from a starting fact. Answers 'what is connected to X?' across the entity graph. Returns a list of {fact_id, depth, relation, path} dicts. |
| find_entitiesB | Knowledge Graph: Find all entity-typed memories in Qdrant. Returns a list of {id, name, entity_type, content, attributes} dicts. |
| get_subgraphB | Knowledge Graph: Get a subgraph centered on a fact for visualization. Returns {nodes, edges} where nodes have {id, depth} and edges have {source, target, relation}. |
| get_relatedA | Knowledge Graph: Get directly related facts (1-hop, bidirectional). Returns a list of {fact_id, relation, edge_id, direction} dicts. |
| cost_routing_statsA | Cost-Aware Routing: Get statistics about embedding provider routing. Shows available providers, routing decisions per provider, and tier configuration. |
| cost_routing_explainA | Cost-Aware Routing: Explain the routing decision for a memory category. Returns a human-readable explanation of which provider will be used and why. |
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 19 tools
Core memory operations (remember/recall/update/forget) are clearly distinct, and the guardrail, cost-routing, and webhook clusters are well separated. The knowledge-graph tools (find_entities, get_related, graph_traverse, get_subgraph) overlap somewhat since all query related facts, though hop-depth and output shape differentiate them.
Three conventions coexist: bare verbs (remember, recall, forget, restore, backup, health), verb_noun (find_entities, get_related, graph_traverse, list_subscriptions), and noun_verb (guardrail_check, cost_routing_stats, fact_history). All are snake_case so it stays readable, but the mixed verb styles reduce predictability.
19 tools spans several distinct subsystems—memory CRUD, knowledge graph, guardrails, cost routing, and webhooks—so each earns its place. It runs slightly heavy and could consolidate the KG and cost-routing pairs, but it's reasonable for the breadth of scope.
Strong lifecycle coverage: full memory CRUD (remember/recall/update/forget), backup+restore, fact history/supersession, and complete webhook subscribe/unsubscribe/list. Minor gaps like batch operations or listing all memories remain, but core workflows are well covered.