MemMCP
Provides a persistent storage layer with write-ahead logging and Merkle-root signatures for data integrity.
Formats responses in XML using defensive RAG formatting to mitigate prompt injection attacks.
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., "@MemMCPstore the fact that Paris is the capital of France"
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.
MemMCP is a hyper-optimized Memory Server natively implementing the Model Context Protocol (MCP). It bridges the gap between lexical keyword search and semantic vector embeddings, delivering 100% deterministic, deduplicated memory recall for autonomous AI Agent Swarms.
📖 Table of Contents
Related MCP server: agent-memory
🤔 Why MemMCP?
When dozens of autonomous agents operate in parallel, standard vector databases suffer from race conditions, data duplication, and context hallucination. MemMCP solves this by merging SQLite Write-Ahead Logging (WAL) for ACID-compliant state management with FAISS Hybrid Reciprocal Rank Fusion (RRF) for unparalleled semantic retrieval.
✨ Core Features
Feature | Description | Architecture |
Byzantine Fault Tolerance | Strict isolation of execution states using Bloom-Filter Idempotency tracking. Never stores the same memory twice. |
|
Data Integrity | Dual-ledger Distributed Consensus architecture powered by Merkle-Root signatures. |
|
O(N) Vector Batching Bounds | FAISS Semantic search with hybrid RRF logic executing strictly within |
|
Zero-Trust Execution | Hardened against indirect prompt injection with explicit XML RAG bounding. |
|
🚀 Quick Start
MemMCP is designed to be booted instantly by any MCP-compliant LLM or Agent Framework via standard IO streams (stdio).
# 1. Clone the repository
git clone https://github.com/axton/project_2_mcp_memory.git
cd project_2_mcp_memory
# 2. Build the exact dependency graph using uv
make build
# 3. Verify the rigorous mathematical test suite
make test
# 4. Boot the MCP server directly
make run🏗 Architecture
graph TD
A[MCP Client] --> B{Bloom-Filter Idempotency Gate}
B -->|Duplicate Request| C[Drop (Idempotent Return)]
B -->|New Request| D[Vectorization]
D --> E[FAISS Hybrid RRF Search]
E --> F[SQLite WAL Merkle-Root Ledger]
F --> G[XML RAG Formatter]
G --> H[Response]🛠 MCP Tool Reference
MemMCP automatically exposes the following functions to any connected agent:
store_memory: Store a single memory. Generates unique keys and updates FAISS indices.store_memories_batch: Store multiple memories atomically in a single massive transaction, rebuilding the index only once.recall_memories: Retrieve relevant memories using Reciprocal Rank Fusion (blending Semantic FAISS similarity + SQLite FTS5 keyword search).
🤝 Contributing & Security
To contribute, you must abide by our strict mathematical isolation limits. See CONTRIBUTING.md for details. For vulnerabilities, refer to SECURITY.md.
📄 License
MIT License. Copyright (c) 2026 Axton Carroll.
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.
Latest Blog Posts
- 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/axtontc/project_2_mcp_memory'
If you have feedback or need assistance with the MCP directory API, please join our Discord server