Use different AI assistants. Keep the same to-do list.

Different AI assistants can work with the same World's Best To-Do List (WBTDL) account through MCP. A task saved by one assistant can be read and updated by another. Each client needs a compatible remote MCP connection and its own sign-in to that account.

This is useful when you plan in one conversation and do the work somewhere else. Your choice of assistant doesn't have to decide where you keep the next action.

What carries over between assistants?

The saved task carries over: its title, category, status, assignee, and High Priority setting. Your conversation doesn't. An assistant that reads “Review checkout error message” won't automatically know which wording you rejected in another chat.

Write task titles that make sense on their own. “Fix the thing we discussed” has a short useful life. “Show a clear error when a card payment fails” gives the next assistant somewhere to start. Keep longer decisions in the project document or repository and supply that context when needed.

A handoff you can try

1. In the first assistant, review your plan and save one approved next action to a named WBTDL category. Ask it to confirm the saved title.
2. In the second assistant, fetch that category and find the task before doing anything else. Don't paste the plan and ask it to create the task again.
3. Provide the files or background it needs. When the work is finished and checked, ask it to update that existing task's status.

For example, you might draft a launch checklist in Claude and later use a coding agent to work on one item. Both can use the same task record, even though their conversations contain different details.

Ask for a fresh read

Read my current WBTDL tasks in the Launch category. Show the open tasks assigned to me. Use the saved statuses, and don't create copies of tasks that are already there.

A conversation can contain an old snapshot. Fetch the list again when you return to work or switch assistants. If two assistants are working at once, give them distinct tasks and avoid having both change the same status. MCP doesn't settle disagreements about whether a piece of work is actually finished.

WBTDL's task reader returns up to 500 active tasks per call and doesn't retrieve archived History. Treat a large-list summary accordingly; it may not include every task. Connecting another assistant doesn't expand that limit.

Connect the assistants you use

Start with the guide for ChatGPT, Claude, or a coding agent. For other clients, check that they support remote MCP with OAuth sign-in. The MCP standard provides a common way to connect tools; each client still determines what it supports.