Mnemex gives AI assistants human-like memory that fades over time, mirroring the Ebbinghaus forgetting curve for natural
Add new capabilities to Claude beyond text generation
Example: Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example: Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example: Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Time estimate: 15-60 minutes depending on server complexity
Prerequisites
Createve.AI Nexus
Createve.AI Nexus unifies REST API and MCP, integrating APIs for AI workflow automation with tools like Calendly API and
Qdrant Docs Rag
Qdrant Docs Rag offers real-time documentation context using vector-based search and retrieval with Qdrant for efficient
PageIndex
PageIndex: a reasoning-based RAG system for fast, accurate analysis of long PDFs — extract insights, cite sources, and n
Perplexity MCP
Official Perplexity API MCP server implementation. Perform AI-powered web searches with real-time information, citations
Ollama
Integrate Ollama's local LLM models for secure, on-premise AI and data control with MCP-compatible apps. Deploy custom m
Strong directory entry: Mnemex surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Strong directory entry: Mnemex surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Mnemex is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Strong directory entry: Mnemex surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Mnemex has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Mnemex is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
I recommend Mnemex for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We wired Mnemex into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Mnemex has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
According to our notes, Mnemex benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
showing 1-10 of 73
Share your MCP server with the developer community
Select a client to integrate this server.
Claude Desktop configuration
{
"mcpServers": {
"mnemex": {
"command": "mnemex",
"args": []
}
}
}Gives AI assistants human-like memory that naturally fades over time unless reinforced through use, following the Ebbinghaus forgetting curve. Store and retrieve memories that become weaker or stronger based on usage patterns.
Mnemex is a community-built MCP server published by mnemexai that provides AI assistants with tools and capabilities via the Model Context Protocol. Mnemex gives AI assistants human-like memory that fades over time, mirroring the Ebbinghaus forgetting curve for natural It is categorized under ai ml.
You can install Mnemex in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
A Model Context Protocol (MCP) server providing human-like memory dynamics for AI assistants. Memories naturally fade over time unless reinforced through use, mimicking the Ebbinghaus forgetting curve.
[!NOTE] About the Name & Version
This project was originally developed as mnemex (published to PyPI up to v0.6.0). In November 2025, it was transferred to Prefrontal Systems and renamed to CortexGraph to better reflect its role within a broader cognitive architecture for AI systems.
Version numbering starts at 0.1.0 for the cortexgraph package to signal a fresh start under the new name, while acknowledging the mature, well-tested codebase (791 tests, 98%+ coverage) inherited from mnemex. The mnemex package remains frozen at v0.6.0 on PyPI.
This versioning approach:
- Signals "new package" to PyPI users discovering cortexgraph
- Gives room to evolve the brand, API, and organizational integration before 1.0
- Maintains continuity: users can migrate from
pip install mnemex→pip install cortexgraph- Reflects that while the code is mature, the cortexgraph identity is just beginning
[!IMPORTANT] 🔬 RESEARCH ARTIFACT - NOT FOR PRODUCTION
This software is a Proof of Concept (PoC) and reference implementation for research purposes. It exists to validate theoretical frameworks in cognitive architecture and AI safety (specifically the STOPPER Protocol and CortexGraph).
It is NOT a commercial product. It is not maintained for general production use, may contain breaking changes, and offers no guarantees of stability or support. Use it to study the concepts, but build your own production implementations.
📖 New to this project? Start with the ELI5 Guide for a simple explanation of what this does and how to use it.
CortexGraph gives AI assistants like Claude a human-like memory system.
When you chat with Claude, it forgets everything between conversations. You tell it "I prefer TypeScript" or "I'm allergic to peanuts," and three days later, you have to repeat yourself. This is frustrating and wastes time.
CortexGraph makes AI assistants remember things naturally, just like human memory:
No flashcards. No explicit review. Just natural conversation.
Most memory systems are dumb:
CortexGraph is smart:
This repository contains research, design, and a complete implementation of a short-term memory system that combines:
CortexGraph follows a modular architecture:
cortexgraph.core: Foundational algorithms (decay, similarity, clustering, consolidation, search validation)cortexgraph.agents: Multi-agent consolidation pipeline and storage utilitiescortexgraph.storage: JSONL and SQLite storage backends with batch operationscortexgraph.tools: MCP tool implementationsAll data stored locally on your machine - no cloud services, no tracking, no data sharing.
Short-term memory:
~/.config/cortexgraph/jsonl/)~/.config/cortexgraph/cortexgraph.db)Long-term memory: Markdown files optimized for Obsidian
Export: Built-in utility to export memories to Markdown for portability.
You own your data. You can read it, edit it, delete it, or version control it - all without any special tools.
The temporal decay scoring function:
$$ \Large ext{score}(t) = (n_{ ext{use}})^\beta \cdot e^{-\lambda \cdot \Delta t} \cdot s $$
Where:
Thresholds:
Decay Models:
See detailed parameter reference, model selection, and worked examples in docs/scoring_algorithm.md.
Decision thresholds:
Unlike traditional caching (TTL, LRU), Mnemex scores memories continuously by combining recency (exponential decay), frequency (sub-linear use count), and importance (adjustable strength). See Core Algorithm for the mathematical formula. This creates memory dynamics that closely mimic human cognition.
Patterns for making AI assistants use memory naturally, now enhanced with automatic entity extraction and importance scoring:
Auto-Enrichment (NEW in v0.6.0)
When you save memories, CortexGraph automatically:
# Before v0.6.0 - manual entity specification
save_memory(content="Use JWT for auth", entities=["JWT", "auth"])
# v0.6.0+ - automatic extraction
save_memory(content="Use JWT for auth")
# Entities auto-extracted: ["jwt", "auth"]
# Strength auto-calculated based on content
Auto-Save
User: "Remember: I prefer TypeScript over JavaScript"
→ Detected save phrase: "Remember"
→ Automatically saved with:
- Entities
---
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.