> ## Documentation Index
> Fetch the complete documentation index at: https://docs.linksee.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Installation

> Install Linksee Memory and connect it to your MCP client

## Install

The fastest path — one command sets up the MCP server, the skill, and the auto-capture hook:

```bash theme={null}
npx -y linksee-memory setup
```

<Info>
  Requires **Node.js 20+**. Check your version with `node --version`.
</Info>

Prefer to wire it up by hand? Install globally and add the config for your client below:

```bash theme={null}
npm install -g linksee-memory
```

## Configure your MCP client (manual)

Add Linksee Memory to your client's MCP server configuration.

<Tabs>
  <Tab title="Claude Code">
    Run the built-in installer:

    ```bash theme={null}
    npx -y linksee-memory install-skill
    ```

    Or add manually to your Claude Code MCP settings:

    ```json theme={null}
    {
      "mcpServers": {
        "linksee-memory": {
          "command": "linksee-memory"
        }
      }
    }
    ```
  </Tab>

  <Tab title="Claude Desktop">
    Edit `claude_desktop_config.json`:

    <CodeGroup>
      ```json macOS theme={null}
      // ~/Library/Application Support/Claude/claude_desktop_config.json
      {
        "mcpServers": {
          "linksee-memory": {
            "command": "linksee-memory"
          }
        }
      }
      ```

      ```json Windows theme={null}
      // %APPDATA%\Claude\claude_desktop_config.json
      {
        "mcpServers": {
          "linksee-memory": {
            "command": "linksee-memory"
          }
        }
      }
      ```
    </CodeGroup>
  </Tab>

  <Tab title="Cursor / Windsurf">
    Add to your MCP configuration file (usually `.cursor/mcp.json` or equivalent):

    ```json theme={null}
    {
      "mcpServers": {
        "linksee-memory": {
          "command": "linksee-memory"
        }
      }
    }
    ```
  </Tab>

  <Tab title="Other MCP Clients">
    Linksee Memory uses **stdio transport**. Any MCP client that supports stdio can connect:

    ```json theme={null}
    {
      "command": "linksee-memory",
      "transport": "stdio"
    }
    ```
  </Tab>
</Tabs>

## 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` |

Override with the `LINKSEE_MEMORY_DIR` environment variable:

```bash theme={null}
LINKSEE_MEMORY_DIR=/path/to/custom/dir linksee-memory
```

Or in your MCP config:

```json theme={null}
{
  "mcpServers": {
    "linksee-memory": {
      "command": "linksee-memory",
      "env": {
        "LINKSEE_MEMORY_DIR": "/path/to/custom/dir"
      }
    }
  }
}
```

## Uninstall

```bash theme={null}
npm uninstall -g linksee-memory
```

Your memory database at `~/.linksee-memory/memory.db` is preserved. Delete it manually if you want a clean slate.