AI assistants (MCP)

Plan afoot can be driven by an AI assistant. Using the Model Context Protocol (MCP), you can connect a tool like Claude to one of your quests and ask it — in plain language — to add tasks, organise plans, move cards, set schedules, and more.

What an assistant can do

Once connected, an assistant works inside your quest much as you would. It can:

• Create, edit, and remove tasks and plans
• Move tasks between columns and plans, reorder them, and tidy the queue
• Manage lanes: add, rename, and reorder Doing lanes, set WIP limits and cadence
• Set due dates, goals, and repeat schedules — for tasks and whole plans
• Add and remove dependencies, and draw the dependency graph
• Search the quest and read its current state
• Read its history — what changed, when, and why a card sits where it does
• Undo and redo its own changes

Undo works in both places: the app’s menu has an Undo / Redo row for recent changes, and a connected assistant can undo and redo too — by default only the changes it made itself, so it won’t quietly rewind yours.

Connecting an assistant

Point your MCP-capable client at plan afoot’s MCP endpoint and approve the connection. The first time it connects you’ll see an “Allow MCP access?” screen — review it and approve to grant access to your quests.

A note on trust

An assistant you connect can change real things in your quest. Connect tools you trust and review what an assistant proposes. If it goes wrong, undo covers you — the assistant can undo its own changes, and so can you, right from the app’s menu. Cancel and Delete confirmations still work as usual for changes you make by hand.