Lific runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 2 Nov 2026.
Local-first, lightweight issue tracker. Single binary, SQLite-backed, MCP-native.
What the code does
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const next = current.slice(0, start) + insert + current.slice(end);
btn.innerHTML = COPY_SVG;
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Lific
same job, measured the same wayLocal-first persistent memory for AI agents — SQLite + local embeddings, MCP-native, no cloud.
Local-first memory for coding agents — MCP server, single SQLite file, local embeddings
Local Jeero MCP server backed by Mother and SQLite.
Persistent memory + vibe-loop engine for AI agents. Single Go binary, SQLite-backed, stdio MCP.
Local-first memory for AI agents: on-device hybrid retrieval over a single SQLite file.
Local-first memory for AI coding agents. Memory + CodeGraph + Wiki in one SQLite file.
Local-first MCP memory server for coding agents. No API key, no cloud. SQLite + FTS5 + sqlite-vec.
Token-light local memory with SQLite hybrid retrieval for MCP agents.
Lific — questions
Answers built from our own checks of this server.