MCP.so
登录

Memlord已验证已精选

@MyrikLD

关于 Memlord

Memlord is a remote MCP server available at https://app.memlord.com.

连接信息

https://app.memlord.com/mcp

接入方式

claude mcp add memlord --transport http https://app.memlord.com/mcp

工具

未检测到工具

点击上方按钮,直接连接服务器端点实时获取工具列表。

概览

Self-hosted MCP memory server with hybrid BM25 + semantic search, backed by PostgreSQL +
pgvector

Self-hosted MCP memory server for personal use and teams

License Python Version MCP Ruff MCP score

QuickstartHow It WorksMCP ToolsConfigurationRequirementsLicense


✨ Features

  • 🔍 Hybrid search — BM25 (full-text) + vector KNN (pgvector) fused via Reciprocal Rank Fusion
  • 📂 Multi-user — each user sees only their own memories; workspaces for shared team knowledge
  • 🛠️ 11 MCP tools — store, retrieve, recall, list, search by tag, get, update, delete, move, list workspaces, dream report
  • 💤 Dreaming — a guided consolidation pass (dream MCP prompt + dream_report tool): finds near-duplicate and conflicting memories, merges them into insights non-destructively, driven by the client LLM
  • 🌐 Web UI — browse, search, edit and delete memories in the browser; export/import JSON
  • 🔒 OAuth 2.1 — full in-process authorization server, always enabled
  • 🐘 PostgreSQL — pgvector for embeddings, tsvector for full-text search
  • 📊 Progressive disclosure — search returns compact snippets by default; call get_memory(name) only for what you need, reducing token usage
  • 🔁 Deduplication — automatically detects near-identical memories before saving, preventing noise accumulation

🆚 How Memlord compares

MemlordOpenMemorymcp-memory-servicebasic-memory
SearchBM25 + vector + RRFVector only (Qdrant)BM25 + vector + RRFBM25 + vector
EmbeddingsLocal ONNX, zero configOpenAI default; Ollama optionalLocal ONNX, zero configLocal FastEmbed
StoragePostgreSQL + pgvectorPostgreSQL + QdrantSQLite-vec / Cloudflare VectorizeSQLite + Markdown files
Multi-user❌ single-user in practice⚠️ agent-ID scoping, no isolation
Workspaces✅ shared + personal, invite links⚠️ "Apps" namespace⚠️ tags + conversation_id✅ per-project flag
Authentication✅ OAuth 2.1❌ none (self-hosted)✅ OAuth 2.0 + PKCE
Web UI✅ browse, edit, export✅ Next.js dashboard✅ rich UI, graph viz, quality scores❌ local; cloud only
MCP tools11515+~20
Self-hosted✅ single process✅ Docker (3 containers)
Memory inputManual (explicit store)Auto-extracted by LLMManualManual (Markdown notes)
Memory typesfact / preference / instruction / feedback / decision / insightauto-extracted factsobservations + wiki links
Time-aware search✅ natural language dates⚠️ REST only, not in MCP tools✅ recent_activity
Token efficiency✅ progressive disclosure✅ build_context traversal
Import / Export✅ JSON✅ ZIP (JSON + JSONL)✅ Markdown (human-readable)
LicenseAGPL-3.0 / CommercialApache 2.0Apache 2.0AGPL-3.0

Where competitors have a real edge:

  • OpenMemory — auto-extracts memories from raw conversation text; no need to decide what to store manually; good import/export
  • mcp-memory-service — richer web UI (graph visualization, quality scoring, 8 tabs); more permissive license (Apache 2.0); multiple transport options (stdio, SSE, HTTP)
  • basic-memory — memories are human-readable Markdown files you can edit, version-control, and read without any server; wiki-style entity links form a local knowledge graph; ~20 MCP tools

When to pick Memlord:

  • You want zero-config local embeddings — ONNX model ships with the server, no Ollama or external API needed
  • You run a multi-user team server with proper OAuth 2.1 auth and invite-based workspaces
  • You want a production-grade database (PostgreSQL) that scales beyond a single machine's SQLite
  • You manage memories explicitly — store exactly what matters, typed and tagged, not everything the LLM decides to extract
  • You want a self-hosted Web UI with full CRUD and JSON export, without a cloud subscription

🚀 Quickstart

🐳 Docker

cp .env.example .env
docker compose up

HTTP server (multi-user, Web UI, OAuth)

# Install dependencies
uv sync --dev

# Download ONNX model (~23 MB)
uv run python scripts/download_model.py

# Run migrations
alembic upgrade head

# Start the server
memlord

Open http://localhost:8000 for the Web UI. The MCP endpoint is at /mcp.


⚙️ Configuration

All settings use the MEMLORD_ prefix. See .env.example for the full list.

VariableDefaultDescription
MEMLORD_DB_URLpostgresql+asyncpg://postgres:postgres@localhost/memlordPostgreSQL connection URL
MEMLORD_PORT8000Server port
MEMLORD_BASE_URLhttp://localhost:8000Public URL for OAuth (HTTP mode)
MEMLORD_OAUTH_JWT_SECRETmemlord-dev-secret-please-changeJWT signing secret (HTTP mode)

Set MEMLORD_BASE_URL to your public URL and change MEMLORD_OAUTH_JWT_SECRET before deploying.


🛠️ MCP Tools

ToolDescription
store_memorySave a memory (idempotent by content); raises on near-duplicates; optional expires_at
retrieve_memoryHybrid semantic + full-text search; returns snippets by default
recall_memorySearch by natural-language time expression; returns snippets by default
list_memoriesPaginated list with type/tag filters
search_by_tagAND/OR tag search
get_memoryFetch a single memory by name with full content (expired included)
update_memoryUpdate content, type, tags, metadata, or expiry by name (and optionally rename)
delete_memoryDelete by name
move_memoryMove a memory to a different workspace
list_workspacesList workspaces you are a member of (including personal)
dream_reportRead-only consolidation candidates: similar memory pairs, expired and expiring-soon memories

The dream MCP prompt walks the client LLM through a full consolidation pass over the dream_report output: classify similar pairs (duplicate / complementary / conflict), merge into insight memories, retire superseded ones via expires_at — never destructively.

Workspace management (create, invite, join, leave) is handled via the Web UI.


💻 System Requirements

  • Python 3.12
  • PostgreSQL ≥ 15 with pgvector extension
  • uv — Python package manager

👨‍💻 Development

pyright src/           # type check
ruff format .          # format
pytest                 # run tests
alembic-autogen-check  # verify migrations are up to date

📄 License

Memlord is dual-licensed:

常见问题

Memlord 远程 MCP 服务器是什么?

Memlord 的远程 MCP 服务器是一个托管的 Model Context Protocol 端点,地址是 https://app.memlord.com/mcp,AI 助手无需在本地安装或运行任何东西即可连接。

怎么连接 Memlord 的 MCP 服务器?

把端点 https://app.memlord.com/mcp 添加到任意支持 MCP 的客户端,比如 Claude Code、Cursor 或 VS Code。本页的接入代码块可以一步配置好每个客户端。

Memlord 的 MCP 服务器需要认证吗?

需要。Memlord 使用 OAuth——第一次连接时,你的 MCP 客户端会打开浏览器窗口登录并授权,之后会复用这个凭证。

Memlord 的 MCP 服务器用的是哪种传输方式?

Memlord 暴露的是 Streamable HTTP 端点,这是远程 MCP 服务器普遍使用、主流客户端都支持的传输方式。

评论