Mindpm MCP Server

Persistent project memory for LLMs via MCP. Never re-explain your project again.

Local serverstdio

What is the Mindpm MCP server?

Persistent project memory for LLMs via MCP. Never re-explain your project again. The mindpm mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 5 defined tools rather than through you.

What it actually does

mindpm is an MCP (Model Context Protocol) server that gives LLMs a SQLite-backed brain for your projects. It tracks tasks, decisions, architecture notes, and session context — so every new conversation picks up exactly where you left off.

Its toolset

Everything the assistant can do here goes through one of these:

  • Projects — The Projects tool exposed by this server
  • Tasks — The Tasks tool exposed by this server
  • Decisions — The Decisions tool exposed by this server
  • Sessions — The Sessions tool exposed by this server
  • Query — The Query tool exposed by this server

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at mindpm on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Configuration

You will need 3 environment variables: MINDPM_DB_PATH, MINDPM_PORT, PROJECT_MEMORY_DB_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Mindpm's toolset — Projects, Tasks, Decisions and 2 more — is a fair guide to whether it matches your workflow. It is maintained by umitkavala; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mindpm mcp server does with a few real requests.

Available tools

ToolWhat it does
ProjectsThe Projects tool exposed by this server.
TasksThe Tasks tool exposed by this server.
DecisionsThe Decisions tool exposed by this server.
SessionsThe Sessions tool exposed by this server.
QueryThe Query tool exposed by this server.

How to install the Mindpm MCP server

{
  "mcpServers": {
    "mindpm": {
      "command": "mindpm",
      "env": {
        "MINDPM_DB_PATH": "~/.mindpm/memory.db",
        "MINDPM_PORT": "3131"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
MINDPM_DB_PATHFilesystem location the server is allowed to use.Optional
MINDPM_PORTConfiguration value read at startup.Optional
PROJECT_MEMORY_DB_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use Mindpm to Projects.
  • Use Mindpm to Tasks.
  • Use Mindpm to Decisions.

Frequently asked questions

It connects Mindpm to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (Projects, Tasks, Decisions, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Mindpm directly.