claude mcp add --transport http mflow https://mcp.m-flow.io/mcpClaude Desktop or claude.ai? Add MFlow as a custom connector in Settings → Connectors instead.
That's it — Claude Code, Claude Desktop, and claude.ai don't share memory, but now they share a board. Give Claude a task and it updates status and leaves a comment as it works; the next session opens the same board and picks up exactly where the last one left off.
Free forever on Standalone · No API key · No credit card
Standalone + MCP
Works from
MFlow gives every session the same board to read from, so nothing gets lost between one and the next.
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.
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.
If Claude changes course mid-task, there’s no record of why — for you, or for whichever session picks it up next.
MFlow's built-in Kanban board (Standalone) plus an MCP server Claude connects to directly — nothing to sync, nothing to configure.
Give Claude a task from chat, or create it yourself on the board — either way it lands in the same place.
Claude moves its own cards — To Do → In Progress → Done — as it actually works, not after the fact.
Every decision, blocker, or handoff gets logged as a comment on the task — readable by you and the next session.
Claude Code, Claude Desktop, or claude.ai — same MFlow account, same board, connected over MCP.
From connecting MCP to a Claude session actually moving a card — under two minutes.
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.
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.
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.
Session #1 ran out of context mid-task. Session #2 opened the same card and kept going — nobody had to re-explain anything.
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.
See the full platformPaid — plan limits apply on Jira project count, see /platform for pricing.
Standalone task tracking over MCP costs nothing, permanently. Connecting Jira or Trello for full delivery analytics is part of the paid platform.
Free forever
Jira & Trello, unlocked