AI Memory
Imports Git metadata incrementally into memory with pattern-based secret redaction, allowing repository facts and provenance to be reviewed and retrieved.
Uses PostgreSQL as the canonical store for memory records, provenance, and durable jobs, with Qdrant serving only as a derived semantic index.
Click 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., "@AI MemoryRemember that my preferred editor is Neovim, and recall it when I ask for setup help."
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.
AI Memory
Self-hosted memory with PostgreSQL canonical records, provenance and durable jobs; Qdrant semantic indexing; CPU inference; REST and MCP interfaces.
The source includes importers for assistant JSON exports, Gemini activity HTML, supported export archives, Git metadata, and shell history. Imports are incremental and apply pattern-based secret redaction. Review imported facts and sensitive material; redaction is not a guarantee.
Client behavior
Connecting MCP does not automatically save conversations. Client instructions can encourage relevant retrieval and confirmed durable-fact saves. Each client's tool availability and approval policy still apply. The service does not passively capture transcripts or export inaccessible native memories.
Usage counters retain 30 days of hourly aggregates, including operation, outcome, result counts, and average/max duration. Query text, memory contents, tokens, and raw client identities are not stored by those counters. Monitoring traffic is separate. Counters are best effort, not lossless audit records.
Related MCP server: memser
Development
Use Python 3.11 or newer and install development dependencies:
python -m venv .venv
. .venv/bin/activate
python -m pip install -e '.[test]'
python -m pytestOAuth gateway tests also require gateway/requirements.txt. CPU model tests and live-service tests have separate dependencies and runtime requirements.
Deployment examples
The Compose files are examples requiring adaptation, not an installer. Start with OPERATIONS.md. Replace example.com and documentation-network addresses, configure private credentials, prepare model files and host paths, and build images before starting. Never use example keys in a live instance. The templates expose no public database/vector ports.
PostgreSQL is canonical; Qdrant is derived. Protect backup archives because they can contain credentials and source evidence. Keep real data, secrets, exports, models, environment files, and backups outside this repository.
This is a fresh sanitized source snapshot. Private deployment history and operator review bundles are intentionally absent. The project is licensed under Apache-2.0. See LICENSE. Dependencies and model weights retain their own licenses.
Private deployment configuration
See PRIVATE-DEPLOYMENT.md for keeping local settings beside public source without tracking them or sending them to Docker builds.
This server cannot be deployed
Maintenance
Related MCP Connectors
- KogniteOAuthdev.kognite
Hosted agent memory: store, search, and recall facts across sessions from any MCP client.
Cross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client.
Cross-session memory for AI agents with a Source Receipt for every memory, over MCP.
- memnodeOAuthdev.memnode
Persistent, inspectable memory for AI agents with lineage, correction, and a hosted MCP endpoint.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceA semantic-memory MCP server that stores text 'memories' with provenance and enables recall by meaning (vector search), keyword (FTS5), or structured filters.35 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides MCP agents with persistent memory operations (store, recall, forget, consolidate, list) backed by Redis, Postgres, and pgvector, including semantic search and background consolidation.Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnables trustworthy AI memory operations including authoritative memory creation, hybrid recall with provenance, evidence tracking, and safe dry-run-first forget and rebuild operations through a stateless MCP endpoint.2-
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to persist, recall, update, forget, and search agent memories over stdio, backed by Postgres with pgvector for vector search. Supports cross-session memory validation with per-operation latency and outcome logging.1-