6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Triage your inbox, plan your week, create projects and complete tasks.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Todoist MCP server connects a Todoist task account to Claude, ChatGPT, Claude Code and any MCP-compatible agent. It triages your inbox, plans a week from your overdue list, creates projects with sections, and completes and reschedules tasks in conversation. Sign-in is OAuth, it works on every Todoist plan, and it asks for one combined read-and-write permission.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
data:read_write, with reading and writing fused into the same grant. A read-only Todoist connection is not something you can approve here, even though data:read exists on the platform and Doist's own CLI uses it.reschedule-tasks and uncomplete-tasks.add-sections, update-sections, add-comments and update-comments. We cannot reconcile these from published sources. Treat the tool list as the ceiling and the help article as the vendor's own expectation, and verify against your account.update-tasks replaces the whole due string, which wipes the repeat pattern on a recurring task. The tool that preserves it, reschedule-tasks, is one of the twenty absent from Anthropic's listing.import-project-template is in the source and not in the directory listing.data:delete and project:delete as scopes separate from data:read_write. The MCP descriptor advertises neither, yet the connector ships a delete tool. We did not authenticate and make no claim about how the server resolves this. Read the consent screen.GET to https://ai.todoist.net/mcp returns HTTP 405 with Allow: POST, and the host root, robots.txt and .well-known/mcp.json all return 404. The names-only tool section is a limit of the server, not of our effort..well-known documents. Everything above about tool behaviour comes from Todoist's documentation, Doist's published source, or Anthropic's directory listing.Every plan, including the free Beginner tier. Todoist's help documentation names no plan requirement for the connector itself. What your plan changes is how much history the connector can read: Todoist documents one week of activity history on Beginner and full history on Pro and Business, so a Beginner account cannot answer questions about last month.
Yes, and a deleted task cannot be restored. Todoist states plainly that once a task is deleted it cannot be restored to your project, and that there is no undo option for a task deletion. The only recovery path Todoist documents is importing a copy from a backup, which is a Pro and Business feature.
The server and the login live on different hosts by design. The connector endpoint is ai.todoist.net, but its OAuth descriptor names https://todoist.com as the authorization server. So the sign-in page you approve is on Todoist's own brand domain, even though the MCP host is not.
Not through this server. Its descriptor advertises one scope, data:read_write, which fuses reading and writing into a single grant. Todoist's platform does publish a separate read-only data:read scope, and its own command-line tool offers a read-only login, but the MCP resource does not request that narrower scope.
Changing the date replaces the whole due string, which destroys the repeat schedule. Todoist's guidance is to say reschedule rather than change the date, because the reschedule path keeps the recurrence intact. If the recurrence is already lost, Todoist says to reopen the task and set the repeat in the date field again.
Recurring tasks never enter your completed list. Todoist explains that completing a recurring task reschedules it to the next occurrence instead of marking it done, and records the event in your activity log. Todoist's fix is to name the activity log in your request, which returns every completion in the period.
Twenty-five. Todoist documents that the MCP server supports up to 25 tasks per call and recommends telling the assistant to add them all together. Todoist warns that creating tasks one at a time can exhaust the assistant's tool-call budget before a long list is finished.
A Claude workspace administrator has not approved it yet. Todoist documents that on Claude Team and Enterprise plans an Owner or Primary Owner must approve a connector request before a member's connection completes. Todoist notes there is nothing to approve on the Todoist side, so the block is entirely on the Claude account.
initialize against https://ai.todoist.net/mcp — HTTP 401 with WWW-Authenticate: Bearer resource_metadata="https://ai.todoist.net/.well-known/oauth-protected-resource/mcp", our own observation, 2026-08-18. This challenge is what establishes the OAuth posture. A plain GET to the same URL returns HTTP 405 with Allow: POST, and GET / returns 404, so no unauthenticated tool catalogue is served. · retrieved 2026-08-18authorization_servers: ["https://todoist.com"] and scopes_supported: ["data:read_write"]. The same document is served at the path-less form. This is the source for the single combined scope and for the authorization server being the brand domain. · retrieved 2026-08-18issuer: https://todoist.com, a registration_endpoint (dynamic client registration), authorization_code and refresh_token grants, and code_challenge_methods_supported: ["S256"] — S256 only, no plain. Advertises thirteen scopes including data:read, data:delete and project:delete. ai.todoist.net serves no authorization-server document of its own (HTTP 404). · retrieved 2026-08-18data:read definition, and for the rate limits of 1,000 partial and 100 full sync requests per user per 15 minutes with a 15-second standard-request timeout. · retrieved 2026-08-18@doist/todoist-mcp server source (package version 12.6.0, main branch, pushed 2026-08-18, retrieved 2026-08-18, MIT licensed). The documentation URL Anthropic publishes, https://github.com/Doist/todoist-ai, redirects here. Source for the 47-tool registry, the 27-versus-47 diff, the eight entity types delete-object accepts, the complete three-hint annotations on all 47 tools, the typed accessor shapes of fetch, fetch-object and search, the OpenAI-specification rationale, the universal-deletion design note, the local-server security warning and the server's own instruction text. · retrieved 2026-08-18td auth login --read-only requesting the data:read scope and blocking write commands, which demonstrates a read-only grant is available at the platform level. · retrieved 2026-08-18robots.txt for todoist.com (HTTP 200, retrieved 2026-08-18). Allows /help/, disallows only app and API paths, and carries no Content-Signal directive, so fetching and synthesis are both unrestricted. The host's sitemap.xml is how the three MCP help articles were located; no sub-URL was guessed. · retrieved 2026-08-18Connect Todoist once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.