Can Claude manage my to-do list? Yes, here’s how

Short answer: Yes, if your task manager hosts an MCP server. Done Bear runs one at https://mcp.donebear.com/mcp. Add it to Claude Desktop or claude.ai as a custom connector, sign in with OAuth, and Claude can read, create, triage, and complete tasks on your list. Anthropic currently allows custom connectors on Free, Pro, Max, Team, and Enterprise, and Free accounts can connect one.

Pasting your list into a chat works until the conversation ends. Claude gives good advice, forgets all of it, and nothing lands in the app you open tomorrow.

The Model Context Protocol (MCP) is the open standard that lets Claude use your tools, where before it could only tell you what to do with them. Once your task manager hosts an MCP server, Claude works on the list you already keep.

What Claude can do once it’s connected

With Done Bear connected, Claude can triage your inbox: “Go through my Done Bear inbox. For each task, tell me whether it’s Today, Upcoming, Anytime, or Someday, and why, then file it.” You check its reasoning in the chat, and it files what you agree with.

After a call, paste raw meeting notes and say “extract the action items and add them to my Done Bear inbox.” Or have it plan a realistic day: “Pick at most five tasks from Anytime that fit around my meetings today.”

It runs the weekly review too: “Compare my Logbook to what’s still in Anytime. What am I avoiding?” It creates and breaks down projects as well: “Make a project called ‘Kitchen renovation’ and list the first steps.”

All of it acts on your real tasks and syncs to your phone and desktop in real time.

What Claude can’t (and shouldn’t) do

Free accounts get one connector. Anthropic supports custom remote connectors on Free, Pro, Max, Team, and Enterprise plans, and Team and Enterprise owners have to enable organisation-level connectors before members can use them.

It doesn’t act on its own. Claude only reaches your tasks when you enable the connector in a chat.

It can’t fix a structureless list either. If your task manager is one flat pile, there’s nothing meaningful to file into. That’s why the GTD views matter: “move to Someday” is a real instruction, and a flat pile leaves Claude guessing.

And its context isn’t your whole life. Claude sees your Done Bear workspace, not your calendar or email, unless you connect those separately.

Access is scoped and revocable

Authentication follows MCP’s HTTP authorization flow: the first time Claude calls a Done Bear tool, it opens a browser for you to sign in. Claude then acts as you, scoped to your Done Bear workspace, with no access to anything else on your machine. Remove the connector in Claude and the access goes with it.

How to set it up

1. Open Claude Desktop or claude.ai. A Free account can add one custom connector.
2. Go to Settings, then Connectors, and choose Add custom connector.
3. Paste https://mcp.donebear.com/mcp and save.
4. Start a chat, enable the Done Bear connector, and ask “List my Done Bear tasks.” The first request opens a browser to sign in.

The full walkthrough, with screenshots and troubleshooting, is on the task manager for Claude page. From the terminal, Claude Code connects with a single command. ChatGPT, Cursor, and Windsurf all work too, and the MCP hub covers the rest.

Coding-task tools do a different job

The “AI task managers” you’ll come across, like Task Master or Shrimp, are built for a different job: planning sub-tasks inside a coding session. They’re useful while the feature is being built, and they’re done when it ships. “Renew the passport” doesn’t belong there.

A better prompt won’t fix a list that disappears with the chat. Claude needs a connection to a list that outlives the conversation. Done Bear is that list: local-first, GTD-native, and free to start. If you are still choosing the list itself, the task manager comparisons cover Todoist, Things 3, and TickTick.

The free plan covers your first 250 tasks. Connect Claude and let it do the filing.

Sources

• Anthropic: Get started with custom connectors using remote MCP covers current plan availability, the Free-plan limit, and organisation controls.
• Model Context Protocol: Authorization defines the authorization requirements for HTTP-based MCP transports.