memoryhub
Click on "Install 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., "@memoryhubremember that I prefer dark mode"
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.
memoryhub
MCP server for persistent memory using Qdrant vector store.
Stores text memories with LLM-generated embeddings and retrieves them via semantic search.
Install
npm install @taraksh011/memoryhubOr run directly:
npx @taraksh011/memoryhubRelated MCP server: mcp-server-qdrant
Quick Start
# Start Qdrant (see docs/install-qdrant.md for help)
docker run -p 6333:6333 qdrant/qdrant
# Set API credentials (or use config file)
export LLM_BASE=https://api.openai.com/v1
export LLM_KEY=sk-...
export LLM_MODEL=gpt-4o-mini
# Start memoryhub in stdio mode (for MCP clients)
memoryhub
# Or auto-start Qdrant + serve in one step
memoryhub bootstrapPrerequisites
Memory Hub needs three things:
Qdrant — vector database (install guide)
LLM API — extracts facts from text (e.g. OpenAI, Anthropic, local Ollama)
Embedding API — converts text to vectors (e.g. OpenAI
text-embedding-3-small, local Ollama)
If your LLM and embedding APIs are the same provider, you can set just the LLM values and reuse them (see config example below).
Configuration
Configuration is checked in this order: config file → environment variable → default.
Config file
Create a memoryhub.json in your project root, or config.json in the memoryhub directory (~/.memoryhub/ by default):
{
"qdrant": {
"url": "http://localhost:6333"
},
"collection": "memories",
"vector_size": 768,
"llm": {
"model": "gpt-4o-mini",
"base_url": "https://api.openai.com/v1",
"api_key": "sk-..."
},
"embedder": {
"model": "text-embedding-3-small",
"base_url": "https://api.openai.com/v1",
"api_key": "sk-..."
}
}If your embedder matches your LLM provider, you can omit embedder — it falls back to the llm settings.
Environment variables
Short names (LLM_BASE, LLM_KEY) are preferred. Long names (LLM_BASE_URL, LLM_API_KEY) are supported for backward compatibility.
Env Var | Short Alias | Default | Description |
| — |
| Base directory for config and data files |
| — |
| Qdrant server URL |
| — |
| Collection name |
| — |
| Vector dimension |
| — | — | LLM model for extraction |
|
| — | LLM API base URL |
|
| — | LLM API key |
| — | — | Embedding model (falls back to LLM_MODEL) |
|
| — | Embedding API base URL (falls back to LLM_BASE) |
|
| — | Embedding API key (falls back to LLM_KEY) |
| — |
| Port for HTTP/SSE mode |
Memory Scopes
Memories can be global or project-scoped:
Omit
project→ memory is global (visible to all searches)Pass
project="my-repo"→ memory is scoped to that projectSearch/list without
project→ returns all memories (global + all projects)Search/list with
project="my-repo"→ returns only that project's memories
Use scopes to keep memories isolated per repo, per feature, or any other boundary.
MCP Tools
Tool | Description | Scope Support |
| Store text (LLM extracts facts, embeds them) | Optional |
| Semantic search with optional limit | Optional |
| List memories with pagination ( | Optional |
| Get a single memory by ID | — |
| Update a memory's text (re-embeds) | — |
| Delete specific memories by IDs | — |
| Delete ALL memories (or filter by project) | Optional |
| Collection statistics | — |
| Show current runtime configuration (API keys masked) | — |
| Update a config value at runtime (not persisted) | — |
| Check connectivity to Qdrant | — |
Config changes via
update_configare in-memory only — lost on restart. Use config file or env vars for permanent changes.
Retry
LLM and embedding API calls retry up to 3 times on transient errors (rate limits, server errors) with exponential backoff.
CLI
Command | Description |
| Start MCP server in stdio mode |
| Start HTTP/SSE server |
| Daemon mode (background) |
| Stop daemon |
| Check daemon status |
| Auto-start Qdrant if needed, then serve |
| Install auto-start service (systemd/launchd/Windows) |
| Remove auto-start service |
| Show help |
| Show version |
Transport Modes
stdio (default): Connect MCP clients via stdin/stdout
HTTP/SSE:
memoryhub servestarts an HTTP server on port 9876
Build
pnpm build # type-check + bundle
pnpm typecheck # type-check only
pnpm dev # run with tsxLicense
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityCmaintenancePersistent semantic memory server for AI assistants via MCP, enabling long-term context retention and semantic search across conversations.Last updated11MIT
- Alicense-qualityCmaintenanceMCP server for Qdrant vector database with local BERT embeddings. Enables semantic search and vector storage operations through natural language.Last updatedMIT
- Flicense-qualityCmaintenanceMCP server providing persistent memory for LLMs via semantic search over captures, structured facts with temporal tracking, and document ingestion. Enables any MCP-compatible client to maintain a searchable knowledge base across sessions.Last updated
- Alicense-qualityCmaintenanceSemantic memory server for AI agent teams. Stores, searches, and retrieves knowledge across sessions using pluggable vector backends with local ONNX embeddings, exposed as an MCP server.Last updatedMIT
Related MCP Connectors
Cloud-hosted MCP server for durable AI memory
Cross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client.
Local-first RAG engine with MCP server for AI agent integration.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/taraksh01/memoryhub'
If you have feedback or need assistance with the MCP directory API, please join our Discord server