
Like-I-Said
STDIOPersistent memory server for AI assistants to remember conversations across sessions
Persistent memory server for AI assistants to remember conversations across sessions
Turn Claude Desktop into your intelligent project manager. Track tasks, remember context, and maintain continuity across sessions.
🔥 Major Release (August 2025): Version 3.0.0 solves duplicate process issues and adds AI features:
- 🆕 Socket-Based Architecture - HTTP/SSE mode prevents duplicate processes (fixes API Error 500!)
- ✅ Fuzzy Search - Typo-tolerant search with Fuse.js (handles "serch" → "search")
- ✅ Universal Work Detector - Automatically captures work patterns and creates memories
- ✅ Enhanced Search - Multi-mode search combining exact, expanded, semantic, and fuzzy results
- ✅ Windows Integration - Improved cross-platform support with Windows-specific scripts
🔒 No More Duplicates: Port binding ensures only ONE instance can run! 📊 Search Intelligence: Now finds 700+ memories with typo-tolerant matching! 🤖 Work Detection: Automatically identifies problem-solving, implementation, and configuration work!
# New HTTP mode (prevents duplicates!) export MCP_TRANSPORT=http node server-markdown.js # Or classic stdio mode npm install @endlessblink/[email protected]
Like-I-Said v3.0 brings AI-powered intelligence to memory and task management:
Before installing Like-I-Said v2, you need to have Node.js installed on your system:
node --version
Note: NPX commands require Node.js to be installed. If you see an error like "npx: command not found", please install Node.js first from https://nodejs.org/
Works for both Claude Desktop and Claude Code - one command does everything:
npx @endlessblink/like-i-said-v2@latest like-i-said-v2 install # Or install to a specific directory: npx @endlessblink/like-i-said-v2@latest like-i-said-v2 install --path /custom/path
This single command automatically:
If you're using Claude Code and Option 1 didn't work:
claude mcp add like-i-said-memory-v2 -- npx -p @endlessblink/like-i-said-v2@latest like-i-said-v2
This registers the MCP server directly with Claude Code's configuration system.
After installation:
add_memory
, create_task
, etc.Example usage:
"Create a task: Build authentication system"
"Remember: We're using JWT tokens with refresh rotation"
"What am I currently working on?"
If automatic configuration fails, you can manually configure your IDE:
Option 1: Quick Setup (No Local Files)
// ~/.cursor/mcp.json { "mcpServers": { "like-i-said-memory-v2": { "command": "npx", "args": ["-y", "-p", "@endlessblink/like-i-said-v2@latest", "like-i-said-v2"] } } }
Option 2: Local Installation
First run: npx -p @endlessblink/like-i-said-v2@latest like-i-said-v2 install
The installer will automatically configure Cursor for you
Restart Cursor and verify all 27 tools are available
Option 1: Quick Setup (No Local Files)
// ~/.codeium/windsurf/mcp_config.json { "mcp": { "servers": { "like-i-said-memory-v2": { "command": "npx", "args": ["-y", "-p", "@endlessblink/like-i-said-v2@latest", "like-i-said-v2"] } } } }
Option 2: Local Installation
First run: npx -p @endlessblink/like-i-said-v2@latest like-i-said-v2 install
The installer will automatically configure Windsurf for you
Restart Windsurf and verify all 27 tools are available
Follow the Continue extension's MCP configuration guide to add the server.
The dashboard provides a visual interface for managing memories and tasks.
Quick Start (Recommended)
# Clone the repository git clone https://github.com/endlessblink/Like-I-Said-memory-mcp-server.git cd Like-I-Said-memory-mcp-server # Windows scripts\run-dashboard.bat # Mac/Linux ./scripts/run-dashboard.sh
Manual Start
# If you already have the repo cloned cd Like-I-Said-memory-mcp-server npm install npm run start:dashboard
⚡ IMPORTANT: The dashboard URL is shown when you start the server!
http://localhost:3001
)create_task
- Create tasks with automatic memory linkingupdate_task
- Update status, add subtasks, link memoriessmart_status_update
- Natural language status changes ("I finished X")list_tasks
- View tasks by status, project, or priorityget_task_context
- See all memories and subtasks for a taskget_task_status_analytics
- Productivity insights and suggestionsadd_memory
- Store any information with rich metadatasearch_memories
- Find information across all projectslist_memories
- Browse memories by project or categorygenerate_dropoff
- Create handoff documents for new sessionsset_memory_path
- Claude can change where memories are storedset_task_path
- Claude can change where tasks are storedget_current_paths
- Check current storage locationsenhance_memory_metadata
- Generate titles and summariesbatch_enhance_memories
- Bulk enhance multiple memoriesvalidate_task_workflow
- Check workflow validityget_automation_suggestions
- Get automation ideasTasks and memories are stored as markdown files with rich metadata:
memories/
├── project-name/
│ ├── 2024-07-15-auth-decision-a7b3c9.md
│ └── 2024-07-15-jwt-implementation-d4e8f2.md
tasks/
├── project-name/
│ ├── TASK-00001-build-authentication.md
│ └── TASK-00002-add-user-dashboard.md
Each task tracks:
"I'm blocked on the payment integration because we need API credentials"
"The frontend is done but needs code review"
"What should I work on next?"
"Show me my progress this week"
"Change my memory storage to D:\AI\Memories"
"Set task directory to C:\Projects\MyApp\tasks"
"Where are my files currently stored?"
"Switch to the mobile-app project"
"Show me all tasks for the API project"
"What's the status across all my projects?"
# Update to latest version npx -p @endlessblink/like-i-said-v2@latest like-i-said-v2 install # For Claude Code users (no local files) claude mcp add like-i-said-memory-v2 -- npx -p @endlessblink/like-i-said-v2@latest like-i-said-v2
Your old memories stay in the original location. Either:
Set environment variable before starting Claude:
set DEBUG_MCP=true # Windows export DEBUG_MCP=true # Mac/Linux
Windows Path Issues:
C:/Users/name/memories
C:\\Users\\name\\memories
Port Conflicts:
Found a bug? Have a feature idea?
MIT © endlessblink
Note: This is an MCP (Model Context Protocol) server for Claude Desktop. It requires Claude Desktop or a compatible MCP client to function.