Memory Context Manager_v2
@Big0290
Memory Context Manager_v2 について
🧠 Deep Project Analysis: Memory Context Manager v2
基本情報
設定
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"memory-context-manager-v2": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"memory-context-manager-v2:latest",
"python",
"main.py"
],
"env": {
"MCP_LOG_LEVEL": "INFO",
"OLLAMA_BASE_URL": "http://host.docker.internal:11434"
}
}
}
}ツール
ツールは検出されませんでした
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
概要
What is Memory Context Manager_v2?
Memory Context Manager_v2 is an MCP server featuring a Continuous Self-Evolution System that enables autonomous learning, performance improvement, and intelligent adaptation. It includes an Evolution Engine for background optimization and is monitored via a dedicated web UI built with RedwoodJS and Chakra UI.
How to use Memory Context Manager_v2?
To use Memory Context Manager_v2, run its MCP server instance and then access its web UI by cloning the UI repository, installing dependencies with yarn install, starting the development server with yarn rw dev, and navigating to http://localhost:8910. The UI provides real-time monitoring, evolution tracking, and system control.
Key features of Memory Context Manager_v2
- Continuous Self-Evolution System for autonomous improvement
- Real-time system health monitoring with progress bars
- Evolution Engine with scheduled tasks and learning sources
- Dashboard with quick actions and activity feed
- RESTful API endpoints for backend communication
Use cases of Memory Context Manager_v2
- Monitoring autonomous AI system health and performance
- Tracking continuous self-improvement and learning progress
- Managing scheduled evolution tasks and documentation ingestion
FAQ from Memory Context Manager_v2
How do I run the Memory Context Manager_v2 UI?
Clone the repository, run yarn install, then yarn rw dev, and open http://localhost:8910 in your browser.
What are the prerequisites for using Memory Context Manager_v2?
Node.js 18+, Yarn package manager, and a running instance of the Memory Context Manager v2 MCP server.
Where does system data live?
The README does not specify data storage details; it only describes real-time monitoring and RESTful communication with the MCP server.
What transport or communication does the UI use with the server?
The UI communicates with the MCP server via RESTful API endpoints, as stated in the architecture section.
Does Memory Context Manager_v2 require authentication?
The README does not mention authentication; it only describes a dashboard interface without user management features.
「メモリとナレッジ」の他のコンテンツ
Context7 MCP - Up-to-date Docs For Any Cursor Prompt
upstashContext7 Platform -- Up-to-date code documentation for LLMs and AI code editors
Obsidian MCP Server
cyanheadsRead, write, search, and surgically edit Obsidian vault notes, tags, and frontmatter via MCP. STDIO or Streamable HTTP.
Semantic Scholar MCP Server
YUZongminA FastMCP server implementation for the Semantic Scholar API, providing comprehensive access to academic paper data, author information, and citation networks.
minutes
silversteinEvery meeting, every idea, every voice note — searchable by your AI. Open-source, privacy-first conversation memory layer.
Solomd
zhitongblogA markdown editor — and the bridge to your LLM. Local-first, MIT, ~15 MB. Bundled MCP server lets Claude Code / Codex / Cursor drive your vault directly. 14 AI providers BYOK.
コメント