mcp-hyperspace-memory
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-hyperspace-memoryremember that I prefer concise answers with code examples"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-hyperspace-memory
Zero-Code cognitive memory for AI agents — powered by HyperspaceDB SaaS.
8 tools. One config block. No code required.
What is this?
mcp-hyperspace-memory is a Model Context Protocol (MCP) server that gives your AI agent a production-grade, persistent memory backed by HyperspaceDB's hyperbolic vector engine.
It is intentionally scoped to memory operations only — no DDL, no collection management, no admin tools. If you need full vector DB access, use mcp-hyperspacedb alongside it.
Related MCP server: AGI MCP Server
Quick Start
Claude Desktop / Cursor IDE / Windsurf / OpenWebUI
Add to your MCP config (claude_desktop_config.json or .cursor/mcp.json):
{
"mcpServers": {
"memory": {
"command": "npx",
"args": ["-y", "mcp-hyperspace-memory"],
"env": {
"HYPERSPACE_API_KEY": "<YOUR_API_KEY>",
"MEMORY_COLLECTION": "agent_memory"
}
}
}
}That's it. Restart your agent and it will discover 8 memory tools automatically.
Get your API key at yar.ink/dashboard.
Environment Variables
Variable | Default | Required | Description |
| — | ✅ | Database API key ( |
| — | — | Client-side Zero-Knowledge encryption key (activates orthogonal/Lorentz projection + AES-256-GCM payload encryption) |
| — | — | Cloud API key for |
|
| — | Collection name to store memories in |
|
| — | Set to |
🔑 Authentication Architecture: How Keys Work
Scenario 1: Managed Cloud SaaS (the.yar.ink)
{
"HYPERSPACE_API_KEY": "sk_YOUR_YAR_API_KEY",
"MEMORY_COLLECTION": "agent_memory"
}A single sk_ key authenticates both your HyperspaceDB SaaS database storage and the v5_Embedding_801 vectorizer.
Scenario 2: Local DB (Default Security) + Cloud v5 Embeddings
{
"HYPERSPACE_HOST": "localhost:50051",
"HYPERSPACE_API_KEY": "sk_YOUR_YAR_API_KEY",
"MEMORY_COLLECTION": "agent_memory"
}Because the host is localhost and the key starts with sk_, the client connects to your local DB with default credentials (I_LOVE_HYPERSPACEDB), while forwarding sk_... to https://the.yar.ink/v1/embeddings for high-dimensional vectorization. Data stays 100% on your local disk!
Scenario 3: Local DB (Custom Password) + Cloud v5 Embeddings (Two Separate Keys)
If you configured a custom password in your local .env (HYPERSPACE_API_KEY=my_local_secret), provide two distinct keys:
{
"HYPERSPACE_HOST": "localhost:50051",
"HYPERSPACE_API_KEY": "my_local_secret",
"YAR_API_KEY": "sk_YOUR_YAR_API_KEY",
"MEMORY_COLLECTION": "agent_memory"
}HYPERSPACE_API_KEY: Authenticates to the local gRPC server (localhost:50051).YAR_API_KEY: Authenticates to the cloud embedding API (https://the.yar.ink/v1/embeddings).
Available Tools
Tool | Description |
| Store a memory, fact, or procedure with |
| Semantic search with importance boost, recency half-life decay, and candidate oversampling, filterable by |
| Delete a specific memory by ID |
| Atomically replace an existing memory (delete + store new version with refreshed embeddings) |
| Enumerate unique active |
| Navigate Lorentz hyperbolic concept tree (broader vs narrower concepts) |
| Synthesize clusters of memories into a single abstract Fréchet Mean hyperbolic concept vector with optional persistence and source archiving |
| Mathematical anti-hallucination verification using 129D MRL hybrid (Lorentz + Cosine) space with adaptive trust threshold |
| Explicitly connect two memory/concept entities with a directed, labeled, weighted edge in the native CSR vector-graph |
| Delete an explicit directed edge with zero-lag invalidation |
| Declaratively induce knowledge graph edges across memory entries from existing metadata attributes ( |
| Enterprise Query Planner & Intent Disambiguator: detects ambiguous user queries, generates multiple-choice clarifying questions, or splits compound questions into parallel sub-queries |
| Diagnostic status report showing vector count, collection health, and active indexing schema |
🧪 Testing & Verification
Run the test suite against your cluster or local instance:
# 1. Comprehensive verification (all 9 tools + session isolation)
npm test
# 2. Brutal high-concurrency stress test (30 parallel memories, NIAH recall, Fréchet consolidation)
npm run test:stressArchitecture
Agent (Claude / Cursor)
↓ MCP stdio
mcp-hyperspace-memory (this package)
↓ gRPC / hyperspace-sdk-ts
HyperspaceDB SaaS (the.yar.ink)
└─ MEMORY_COLLECTION (e.g. "agent_memory")
├─ Lorentz head (33D, f32, hyperbolic hierarchy)
└─ Euclidean head (768D, 1-bit ADC, 61.4× compressed)Key design decisions
MEMORY_COLLECTIONin env: The agent never needs to pass the collection name per-call. One env var scopes all memory to the right namespace.Deterministic IDs: Memory IDs are
hash(text + session_id)— inserting the same memory twice is idempotent.SaaS default:
HYPERSPACE_HOSTdefaults tothe.yar.ink. Self-hosted instances work by setting the env var.No admin tools: No
create_collection,delete_collection, orrebuild_index. Memory users never need these.
Comparison with mcp-hyperspacedb
Feature |
|
|
Target user | AI agent end-user | Developer / DevOps |
Collection management | ❌ | ✅ |
Cache control | ❌ | ✅ |
Cognitive memory tools | ✅ (8 tools) | ❌ |
Works local + SaaS | SaaS-only | ✅ both |
Config complexity | 1 API key | host + API key |
Self-Hosting
{
"env": {
"HYPERSPACE_HOST": "localhost:50051",
"HYPERSPACE_API_KEY": "I_LOVE_HYPERSPACEDB",
"MEMORY_COLLECTION": "my_memory"
}
}License
MIT — © YARlabs
Docs: yar.ink/memory
This server cannot be deployed
Maintenance
Related MCP Connectors
Persistent memory for AI agents. EU-hosted, privacy-first, hybrid recall, contradiction detection.
Persistent memory and knowledge graphs for AI agents. Hybrid search, context checkpoints, and more.
Persistent memory for AI agents. Semantic search, memory graph, W3C DID identity.
Persistent memory and knowledge management for AI agents with semantic search and 50+ tools.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceProvides AI agents with persistent, searchable memory that survives across conversations using semantic search, temporal versioning, and smart organization. Enables long-term context retention and cross-session continuity for AI assistants.14-
- FlicenseBqualityDmaintenanceEnables persistent memory for AI systems by providing tools for episodic, semantic, and procedural data storage through a vector-and-graph-enhanced database. It allows models to maintain long-term continuity using similarity search, thematic clustering, and identity tracking.241-

Memsolus MCP Serverofficial
AlicenseAqualityDmaintenanceProvides persistent long-term memory for AI agents through semantic search and automated knowledge graph extraction. It enables agents to store, recall, and reason over facts, preferences, and relationships across multiple conversations and sessions.143 npmMIT- AlicenseAqualityDmaintenanceEnables AI agents with persistent semantic memory, including semantic recall, knowledge graphs, and instant domain expertise via pre-built Intelligence Packs.1029 npmMIT