dawnmere
Dawnmere MCP server
dawnmere-connector · npm · stdio · Updated November 12, 2026
dawnmere-connector is the MCP server that lets AI apps share Dawnmere's one memory. Each app launches it as a local stdio server, and it passes the app's recall, remember, forget and access_status calls to Dawnmere on the same Mac over a local socket. The connector stores nothing, sends nothing over the network, and does not decide what an app may see: Dawnmere does, per app.
Dawnmere itself must be installed and running first. Without it every call answers "Dawnmere isn't running on this computer".
curl -fsSL https://dawnmere.app/install | sh
dawnmere setup connects Claude Code, Codex and Cursor for you. The lines below are for other apps, or for connecting one by hand.
Tools
| Tool | What it does |
recall | Search the memory by meaning and keywords. Read only. |
remember | Save one fact for future conversations. A note an app saves on its own is kept for search, labelled, and reaches other apps' prompts only after you confirm it (dawnmere held). |
forget | Hide one memory at once. It is deleted for good after 24 hours unless you bring it back with dawnmere restore ID. |
access_status | Say what this app is allowed to see. |
Check that Dawnmere answers
npx -y dawnmere-connector --check
Claude Code
claude mcp add --scope user dawnmere -- npx -y dawnmere-connector
Or as a plugin: /plugin marketplace add LF-Labs-Inc/dawnmere, then /plugin install dawnmere@dawnmere.
Claude Desktop
Download dawnmere-connector.mcpb from the latest release and open it.
Cursor, Windsurf and Gemini CLI
In ~/.cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json or ~/.gemini/settings.json:
{
"mcpServers": {
"dawnmere": {
"command": "npx",
"args": ["-y", "dawnmere-connector"],
"env": { "LFLABS_MEMORY_CLIENT": "cursor" }
}
}
}
Set LFLABS_MEMORY_CLIENT to the app it is in: cursor, windsurf or gemini. The name decides what that app may see, so do not copy Cursor's into another app.
VS Code
In the user mcp.json (run "MCP: Open User Configuration" from the Command Palette):
{
"servers": {
"dawnmere": {
"type": "stdio",
"command": "npx",
"args": ["-y", "dawnmere-connector"],
"env": { "LFLABS_MEMORY_CLIENT": "copilot" }
}
}
}
Codex
In ~/.codex/config.toml:
[mcp_servers.dawnmere]
command = "npx"
args = ["-y", "dawnmere-connector"]
env = { LFLABS_MEMORY_CLIENT = "codex" }
Needs Node.js 18 or later (Claude Desktop brings its own for the .mcpb).
Settings
| Variable | Default | Meaning |
LFLABS_MEMORY_CLIENT | none | A name for the app, shown in Dawnmere and used for its permissions |
LFLABS_MEMORY_CLIENT_KEY | none | A key Dawnmere gives an app it trusts with more than its default |
LFLABS_MEMORY_SOCKET | ~/Library/Application Support/LF Labs/memory-connector.sock | Where Dawnmere listens |
LFLABS_MEMORY_TIMEOUT_MS | 20000 | How long to wait for an answer |
Limits
- Mac only, and only with Dawnmere running. There is no hosted server: the memory stays on your Mac, so cloud apps that cannot launch a local server cannot reach it.
- An app's name is a label, not a password: any program running as you can talk to the socket. Access levels keep each AI app to what suits it; they are not a wall against software you already run.
Links
Questions: hello@dawnmere.app. Dawnmere is made by LF Labs.