Home

MemAI

Long-term memory for agentic coding. An agent writes down what it learns while it works — facts, decisions, pitfalls, where the work stands — and a later session reads it back instead of rediscovering it. Everything lives in one SQLite file on your machine, and the agent reaches it through MCP tools.

The MemAI dashboard, Health view

Where to start

you want to…	read
install it and see it work	Getting started
understand what happens in a session	How a session uses memory
know which kind of memory to write	Memory types
look up a tool, a hook or a setting	Tools, Hooks and the warden, Configuration
fix something that is not working	Troubleshooting

How the pieces fit

flowchart LR
    agent([Agent in Claude Code])
    hooks[memai-hook<br/>session start · guard · stop]
    server[memai-mcp<br/>43 MCP tools]
    store[(Project file<br/>SQLite + FTS5)]
    admin[memai-admin<br/>dashboard]
    you([You])

    hooks -- brief, reminders --> agent
    agent -- MCP calls --> server
    server --> store
    hooks -. read .-> store
    admin --> store
    you -- review, curate --> admin

memai-mcp is the MCP server. Agents call its tools to read and write.
memai-hook runs on Claude Code's hook events. It puts the store in front of a session that did not ask for it, and holds the session's tools until it has read its memory.
memai-admin is a local web dashboard where a person reads, edits and curates the store.
memai-store exports, imports and moves memories as text.