MCP SERVERKeep tasks, decisions, notes and session handoffs for a project in a local SQLite file, so the next conversation starts with what changed rather than with an explanation.
LABSCO SUMMARY
Most catch-up tooling diffs on a timestamp, which quietly breaks the moment history is rewritten. Here the git delta is anchored on the exact sha recorded when the previous session ended; if that sha becomes unreachable after a force-push, it falls back to a timestamp and says so in degraded_reasons rather than presenting a wrong answer as a right one. The same honesty shows in the gap label — a gap over fourteen days comes back marked stale with a hint to re-verify rather than trust the stored next steps. Nothing here calls a model or touches the network: it is local git subprocesses and a local database.
Project memory for an assistant, held in a SQLite database on your own machine at ~/.mindpm/memory.db. It tracks tasks, decisions with their rejected alternatives, notes, key-value context and sessions, and serves a Kanban board on http://localhost:3131 alongside the tools.
Node — npm install -g mindpm — and nothing else: no account, no key, no network. The database lives at ~/.mindpm/memory.db unless MINDPM_DB_PATH says otherwise, and every client you configure shares it, so you can switch tools mid-project. MINDPM_PORT moves the Kanban board off 3131. Git activity in the brief needs the repository path registered against the project; without it the brief still reports the task, blocker and decision delta.
One command — npx -y mindpm
USE CASES
Read what changed — commits, branch, task movements, new blockers — before deciding anything.
Ask for the highest-priority unblocked work, and see separately what is stuck and on what.
Record the choice with its reasoning and the options that were rejected, then find it again by tag.
Write the summary and the next steps; that is what the next brief is measured against.
Store the stack, config values and constraints as context rather than repeating them each chat.
Throughput, lead time and flow efficiency computed from what has been recorded, not estimated.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
add_noteAdd a note to a project or task. Proactively use this when the user shares context about architecture, bugs, ideas, research findings, or any important information worth remembering. Always specify the project parameter when you know which project is active.
create_projectCreate a new project to track. Use this when starting a new project or when a user mentions a project that doesn't exist yet.
create_taskCreate a new task in a project. Proactively use this when the user mentions something that needs to be done, a bug to fix, or a feature to build.
end_sessionEnd a work session with a summary of what was accomplished and what to do next. Call this when the user is done working.
get_agent_instructionsReturns the recommended instructions for using mindpm effectively. Call this once if you are unsure how to use mindpm, or share it with the user to paste into other LLM clients.
get_blockersList all blocked tasks with what's blocking them.
get_contextGet context by key or list all context for a project.
get_delivery_metricsDORA-inspired delivery metrics for a project: throughput, lead time, flow efficiency, and performance tier. Use to understand delivery health and trends.
get_next_tasksSmart query: what should be worked on next? Returns highest priority non-blocked tasks for a project.
get_project_statusGet a full overview of a project: active tasks, recent decisions, blockers, and last session summary. Great for getting up to speed.
get_project_summaryHigh-level summary of a project: total tasks by status, recent activity, open blockers, and upcoming priorities.
get_session_briefRead-only: what changed since the last session ended — commits, branch and working-tree state, task status changes, new blockers, decisions, and notes. Unlike start_session, this does not open a session or mark one as started.
get_taskGet full detail for a specific task including sub-tasks and related notes.
list_decisionsList decisions for a project. Filter by tags to find specific decisions.
list_projectsList all tracked projects. Filter by status to see active, paused, completed, or archived projects.
list_tasksList tasks with filters. Defaults to showing non-completed tasks for the most recent active project.
log_decisionRecord a decision with reasoning and alternatives considered. Proactively use this when the user makes a technical decision, chooses between options, or settles a debate.
queryExecute a read-only SQL query against the database. Only SELECT statements are allowed. Use this for custom queries not covered by other tools.
searchFull-text search (FTS5, ranked by relevance) across tasks, notes, and decisions for a project.
search_notesFull-text search across notes for a project.
set_contextSet a key-value context pair for a project (upsert). Proactively use this when the user shares important project context like architecture decisions, config values, conventions, or constraints.
set_project_repo_pathSet or update the local git repository path for a project. Required for the session brief to include git activity (commits, branch, working-tree state) since the last session.
start_sessionBegin a work session for a project. Returns the full project overview including last session's next_steps, active tasks, blockers, and recent decisions. Call this at the start of every conversation. For multi-project conversations, call once per project — after that, pass project explicitly on every tool call. IMPORTANT: Always show the kanban_url to the user as a clickable link so they can open the Kanban board.
update_taskUpdate any field of a task. Proactively use this when a task status changes, priorities shift, or new information comes in.
BEFORE YOU INSTALL
24 tools when we connected.
npx on PATH
MINDPM_DB_PATH in your environment
CONTEXT COST
Rated by the size of the 24 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Add the block to your client, or run the command directly.
{
"mcpServers": {
"mindpm": {
"command": "mindpm",
"env": {
"MINDPM_DB_PATH": "~/.mindpm/memory.db",
"MINDPM_PORT": "3131"
}
}
}
}npx -y mindpmMCP servers
memory-graph
amanasmuei
qualixar
Yuchen20