MCP Session Saver
README.md
# đ MCP Session Saver
[English](README.md) | [įŽäŊ䏿](README-zh.md)
An MCP service for saving session records. Session content can be saved to a specified directory and stored as Markdown files organized by **IDE name, date, and session description**.
## ⨠Key Features
- đ **Save Session Records** - Save AI conversations as Markdown files
- đ **Smart Organization** - Automatically categorized by IDE/date/description
- đ **Session Management** - Read, search, and delete sessions
- đ **Multi-IDE Support** - Compatible with Qoder, Cursor, Claude Desktop, Windsurf, Trae, Codebuddy, Lingma, Continue, Aider, and more
## đ Quick Start
### Method 1: Using npx (Recommended)
No installation required. Simply add to your IDE's MCP configuration:
```json
{
"mcpServers": {
"session-saver": {
"command": "npx",
"args": ["-y", "mcp-session-saver"]
}
}
}
```
### Method 2: Global Installation
```bash
npm install -g mcp-session-saver
```
MCP Configuration:
```json
{
"mcpServers": {
"session-saver": {
"command": "mcp-session-saver"
}
}
}
```
### Method 3: Local Installation
```bash
npm install mcp-session-saver
```
## đ Custom Storage Path (Optional)
Add environment variable in MCP configuration:
```json
{
"mcpServers": {
"session-saver": {
"command": "npx",
"args": ["-y", "mcp-session-saver"],
"env": {
"MCP_SESSION_BASE_DIR": "D:\\MyProjects\\sessions"
}
}
}
}
```
## đ¯ How to Use
After configuration, simply say in your IDE:
```
Save current session
List all sessions
Search session content
```
## đ Documentation
- [**Quick Setup Tools**](tools/) - One-click configuration scripts
- [**Detailed Usage Guide**](docs/USAGE.md) - Complete usage instructions
- [**Multi-IDE Setup**](docs/MULTI_IDE_SETUP.md) - Configuration for Cursor, Claude, and other IDEs
- [**Qoder Configuration**](docs/QODER_CONFIG_GUIDE.md) - Qoder-specific guide
- [**Internationalization**](docs/I18N.md) - Multi-language support guide
## đ ī¸ Tech Stack
- JavaScript (ES Module)
- @modelcontextprotocol/sdk
- Node.js >= 16.0.0
## đ License
MIT
## đ Contributing
Issues and Pull Requests are welcome!
TDQS
A4/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: delete, list, read, save, and search. There is no overlap in functionality, and the descriptions provide clear context for when to use each.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using snake_case (e.g., delete_session, list_sessions), making them predictable and easy to differentiate.
Tool Count5/5
With 5 tools, the server is well-scoped for its purpose of managing saved sessions. The number is neither too many nor too few, providing essential operations without unnecessary complexity.
Completeness4/5
The tool set covers the core CRUD operations (save, read, delete) plus listing and searching. A minor gap is the lack of an update/rename tool, but this is not critical for the domain.
Maintenance
ActivityInactive
ResponsivenessNo issues