mFlow

The problem

Claude has no memory between sessions — your task list shouldn’t either

MFlow gives every session the same board to read from, so nothing gets lost between one and the next.

Context resets every session

A new Claude Code session doesn’t know what the last one decided, tried, or ruled out. You end up re-explaining the same task from scratch, or Claude re-does work that already happened.

No shared task list

You’re tracking what to hand Claude next in a scratch file, a chat scrollback, or your own head — not somewhere Claude itself can read, update, or check off.

No trail when something breaks

If Claude changes course mid-task, there’s no record of why — for you, or for whichever session picks it up next.

Standalone + MCP

One board,every session reads

MFlow's built-in Kanban board (Standalone) plus an MCP server Claude connects to directly — nothing to sync, nothing to configure.

Assign tasks

Give Claude a task from chat, or create it yourself on the board — either way it lands in the same place.

Live status

Claude moves its own cards — To Do → In Progress → Done — as it actually works, not after the fact.

Comment trail

Every decision, blocker, or handoff gets logged as a comment on the task — readable by you and the next session.

Any client, one board

Claude Code, Claude Desktop, or claude.ai — same MFlow account, same board, connected over MCP.

How it works

Three steps, one board Claude keeps up to date

From connecting MCP to a Claude session actually moving a card — under two minutes.

01

Connect via MCP

Add MFlow as an MCP server in Claude Code, Claude Desktop, or claude.ai. Sign-in runs through your existing MFlow account via an OAuth-style consent screen — no API key, no client secret to copy.

No API key · Works in any MCP client

02

Create a Standalone project

Start a project and a few tasks yourself on the board, or just ask Claude to create them as it works — either way they land in the same Standalone project.

Zero setup · No syncing

03

Watch it work

Claude updates status and leaves comments as it goes. Open the board anytime to see exactly where things stand — or hand a task to a brand-new session and let it read the same trail.

Live status · Full comment history

One task, two sessions

The handoff, as it actually happens

Session #1 ran out of context mid-task. Session #2 opened the same card and kept going — nobody had to re-explain anything.

TASK-142 · Migrate onboarding modal library

You

Assigned: migrate the onboarding flow off the old modal library.

Claude · session #1

Started. Swapped 4 of 9 screens so far — pausing here, ran low on context.

Claude · session #2

Picked this up from the comment above — no re-explaining needed. Finishing the remaining 5 screens now.

Claude · session #2

Done. All 9 screens migrated, old library removed from package.json.

Already on Jira or Trello?

This board isn't a toy — it's the same account as the full platform

Standalone task tracking over MCP is free — that never changes. When you're ready for more, the same account connects Jira and Trello for PSI scoring, risk flags, and an MCP tool that lets Claude reason across your real delivery data, not just Standalone tasks. That part is part of the paid platform.

Jira — full delivery metrics Trello — board metrics

Paid — plan limits apply on Jira project count, see /platform for pricing.

Pricing

Free for tracking Claude, straightforwardly

Standalone task tracking over MCP costs nothing, permanently. Connecting Jira or Trello for full delivery analytics is part of the paid platform.

Standalone + MCP

$0

Free forever

Unlimited Standalone tasks

Full MCP task tools — create, update, comment

Claude Code, Claude Desktop & claude.ai

No credit card

Full platform

Paid

Jira & Trello, unlocked

Jira & Trello sync

PSI score + risk flags

MCP tool for cross-project AI reasoning

Slack, Telegram & Email alerts