Install
The fastest path — one command sets up the MCP server, the skill, and the auto-capture hook:
npx -y linksee-memory setup
Requires Node.js 20+. Check your version with node --version.
npm install -g linksee-memory
Claude Code
Claude Desktop
Cursor / Windsurf
Other MCP Clients
Run the built-in installer:npx -y linksee-memory install-skill
{
"mcpServers": {
"linksee-memory": {
"command": "linksee-memory"
}
}
}
Edit claude_desktop_config.json:// ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"linksee-memory": {
"command": "linksee-memory"
}
}
}
// %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"linksee-memory": {
"command": "linksee-memory"
}
}
}
Add to your MCP configuration file (usually .cursor/mcp.json or equivalent):{
"mcpServers": {
"linksee-memory": {
"command": "linksee-memory"
}
}
}
Linksee Memory uses stdio transport. Any MCP client that supports stdio can connect:{
"command": "linksee-memory",
"transport": "stdio"
}
Verify the installation
After restarting your agent, try:
“Use linksee to remember that I prefer TypeScript over JavaScript”
The agent should call the remember tool and confirm the memory was stored.
Then in a new session:
“What do I prefer, TypeScript or JavaScript? Check linksee.”
The agent should call recall and find your preference.
Database location
By default, the SQLite database is stored at:
| OS | Path |
|---|
| macOS / Linux | ~/.linksee-memory/memory.db |
| Windows | %USERPROFILE%\.linksee-memory\memory.db |
LINKSEE_MEMORY_DIR environment variable:
LINKSEE_MEMORY_DIR=/path/to/custom/dir linksee-memory
{
"mcpServers": {
"linksee-memory": {
"command": "linksee-memory",
"env": {
"LINKSEE_MEMORY_DIR": "/path/to/custom/dir"
}
}
}
}
Uninstall
npm uninstall -g linksee-memory
~/.linksee-memory/memory.db is preserved. Delete it manually if you want a clean slate.
