Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Todoist to Claude Code

Have Claude create, reschedule, and complete tasks in Todoist. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Todoist to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Todoist, you add a Todoist MCP server: a small hosted service that exposes Todoist's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Todoist account. No API keys pasted into config files.

claude mcp add --transport http todoist https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Todoist once connected?

Full read-write Todoist access lets Claude add tasks to the right project, set or shift due dates and priorities, assign tasks to teammates, add labels and comments, and complete items once you approve. The capture and triage that used to mean switching apps happen where your tasks already live.

  • Create a task in a specific project with a due date and priority
  • Reschedule or shift due dates across a set of overdue tasks
  • Assign tasks to teammates and apply labels for triage
  • Add a comment or sub-task to break down a larger item
  • Move tasks between projects or sections as priorities change
  • Complete or reopen tasks after you approve the change

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Todoist access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Todoist API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Todoist changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Todoist connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Todoist connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Todoist account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Todoist's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Todoist?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Todoist account it signs in with. Revoking access is one click in Todoist.

More on the Todoist connector

Todoist connector for claude.aiTeamwork + Claude CodeShortcut + Claude CodeProductboard + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us