Create a new project to track. Use this when starting a new project or when a user mentions a project that doesn't exist yet.

List all tracked projects. Filter by status to see active, paused, completed, or archived projects.

Get a full overview of a project: active tasks, recent decisions, blockers, and last session summary. Great for getting up to speed.

Set 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.

Create 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.

Update any field of a task. Proactively use this when a task status changes, priorities shift, or new information comes in.

List tasks with filters. Defaults to showing non-completed tasks for the most recent active project.

Get full detail for a specific task including sub-tasks and related notes.

Smart query: what should be worked on next? Returns highest priority non-blocked tasks for a project.

Record a decision with reasoning and alternatives considered. Proactively use this when the user makes a technical decision, chooses between options, or settles a debate.

List decisions for a project. Filter by tags to find specific decisions.

Add 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.

Full-text search across notes for a project.

Set 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.

Get context by key or list all context for a project.

Begin 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.

End a work session with a summary of what was accomplished and what to do next. Call this when the user is done working.

Read-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.

Execute a read-only SQL query against the database. Only SELECT statements are allowed. Use this for custom queries not covered by other tools.

High-level summary of a project: total tasks by status, recent activity, open blockers, and upcoming priorities.

List all blocked tasks with what's blocking them.

Full-text search (FTS5, ranked by relevance) across tasks, notes, and decisions for a project.

Returns 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.

DORA-inspired delivery metrics for a project: throughput, lead time, flow efficiency, and performance tier. Use to understand delivery health and trends.