Overview
What is MCP Server Memo?
MCP Server Memo is a lightweight MCP (Model Context Protocol) server that provides persistent local filesystem storage for rich session summaries and memos used by LLMs like Claude. It supports session history version tracking and offers tools for storing, retrieving, and listing summaries.
How to use MCP Server Memo?
Clone the repository from GitHub, run npm install and npm build. Configure the storage directory via the MCP_SUMMARY_DIR environment variable (defaults to ./summaries/). Start the server with npm start or npm run dev for auto-reload. Clients connect using the MCP SDK and call tools like upsertSummary, getSummaryTool, listSummariesTool, appendSummary, getSessionHistory, and updateMetadata.
Key features of MCP Server Memo
- Preserves all historical versions of each session summary.
- Sessions are time-ordered for easy tracking of conversation development.
- Stores data on the local filesystem without requiring an external database.
- Complies with the Model Context Protocol to provide MCP tool interfaces.
- Optimized for file I/O and concurrent operations.
- Minimal dependencies for easy maintenance and extension.
Use cases of MCP Server Memo
- LLMs like Claude can store and retrieve detailed session records.
- Developers can append new content to existing conversation summaries.
- Users can retrieve the full version history of a specific session.
- Applications can list and filter summaries by tags, sorting, and pagination.
- Metadata (title, tags) can be updated independently of summary content.
FAQ from MCP Server Memo
How do I configure the storage directory for summaries?
Set the MCP_SUMMARY_DIR environment variable to your desired path. If not set, the server defaults to ./summaries/.
Does MCP Server Memo require an external database?
No. It uses the local filesystem for persistent storage, with no external database needed.
How does version tracking work?
Each call to upsertSummary or appendSummary creates a new file with a fresh timestamp, preserving all previous versions. You can retrieve the full history with getSessionHistory.
What are the runtime requirements?
Node.js version 18.0.0 or higher is required. The server is built with TypeScript and uses the MCP SDK (version 1.9.0).
Is the data stored locally or sent to a remote server?
Data is stored entirely on the local filesystem in the configured MCP_SUMMARY_DIR directory. No remote server is involved.
