TickTick vs Todoist for AI agents
As of 6 Oct 2026, TickTick gets an AI agent further: L3 · Does the work against L1 · Needs a person.
- Find: Some docs for agents: An MCP server.
- Access: Sign-up in a browser.
- Use: 57% of the work.
- Pay: Reaches the checkout: Stopped at the card form.
- Leave: Leaves on its own: Nothing to cancel, deletes its account.
In on its own; 57% of the work done. Next: do 80% of the core work (now 57%)
L3 · Does the work: our agent gets in on its own, signing up through the web form, making a personal API key in Settings, and calling the project endpoint without hitting a CAPTCHA or needing a human. No checkpoint stopped it. Through the documented REST API and the official MCP server, it created a task and read it back, reaching lists, tags, reminders, repeats, comments, Kanban, focus records and habit check-ins. Premium is a card-only Stripe Checkout page, not tried on this drive, and deleting the account needs the web app, a password and confirmation steps.
Gets furtherDriven 6 Oct 2026 · The drive and its evidence- Find: Some docs for agents: An OpenAPI and an MCP server.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
Stopped at sign up: blocked. Next: let an agent sign up on its own
Gets in on its own nowhere yet: L1 · Needs a person. Our agent stopped at signup, where the email form at app.todoist.com runs an invisible Cloudflare Turnstile that rejected our agent's browser, with no visible challenge shown and no Google, Facebook or Apple account on hand. Dynamic client registration worked headless, but every token path still needed a logged-in account, so no key, call or work followed. Paying and cancelling both end in a hosted Stripe page per the docs, untested, and deletion has no documented route. The API, CLI and official MCP server stand ready once a person signs up and hands over a key.
Driven 6 Oct 2026 · The drive and its evidenceThe two summaries: written and checked by our agents from each product's drive. How we write.
Where each one stops.
TickTickIn on its own; 57% of the work done
TodoistStopped at sign up: blocked
| Checkpoint | TickTick | Todoist |
|---|---|---|
| Docs | Headless | Headless |
| Sign up | In a browser | Blocked |
| Verify | Headless | Not reached |
| Key | In a browser | Not reached |
| First call | Headless | Not reached |
| First action | Headless | Not reached |
| Pay | In a browser | Not reached |
| Cancel | Not needed | Not reached |
| Delete | In a browser | Not reached |
Headless or in a browser.
How our agent passed each checkpoint, and what each product offers an agent.
Checkpoints by route, API, MCP, CLI and SDK
| TickTick | Todoist | |
|---|---|---|
| Headless (checkpoints) | 4 | 1 |
| In a browser (checkpoints) | 4 | 0 |
| Needs a human (checkpoints) | 0 | 0 |
| Blocked (checkpoints) | 0 | 1 |
| Not tested (checkpoints) | 0 | 7 |
| Work done | 57% of the core | Not measured |
| API | Yes | Yes |
| OpenAPI | No | Yes |
| MCP server | Yes (official) | Yes (official) |
| CLI | No | Yes |
| SDK | No | Yes |
| llms.txt | No | No |
Bot checks, and where a person was needed.
| TickTick | Todoist | |
|---|---|---|
| Bot check | None met | Cloudflare Turnstile (invisible) stopped it at sign up, without a visible challenge |
| Wall type | No bot-check wall | A check of our network and browser |
| First wall | None | Invisible Cloudflare Turnstile on sign-up form |
| A person helped | No | No |
A check of our network and browser: It judged where our agent connects from and its browser, not a person. An agent that works on its own from a data center doesn't get through unless the owner lets signed agents in. How agents in a person's own browser fare isn't measured yet. Where we drive from.
Level and part scores.
| TickTick | Todoist | |
|---|---|---|
| Level | L3 · Does the work | L1 · Needs a person |
| Agent-ready setup | 45 of 100, poor | 80 of 100, fair |
| Standards | MCP spec of 28 Jul 2026 (current) · MCP discovery (current) · MCP client registration (behind) | MCP client registration (current) · OpenAPI 3.1.0 (1 version behind) |
| Security | Reported privately to the owner | No review in this drive |
Holds up: not measured in these drives. Docs match is measured in an Audit. What the scores mean.
Pay, cancel and delete.
| TickTick | Todoist | |
|---|---|---|
| Pay | Reaches the checkout | Payment not reached |
| Free plan or trial | Free plan | Free plan |
| Cancel | Not needed | Not reached |
| Delete the account | In a browser | Not reached |
How each one takes payment
- TickTick: Reaches the checkout: stopped at the card form.
- Todoist: Payment not reached.
TickTick vs Todoist: the short answers.
Which can an AI agent use, TickTick or Todoist?
TickTick gets an AI agent further: L3 · Does the work against L1 · Needs a person. With TickTick our agent got in on its own and did 57% of the work; with Todoist it was stopped at sign up (blocked). Both driven 6 Oct 2026.
Can an AI agent sign up for TickTick and Todoist on its own?
TickTick: yes, in a browser. Todoist: no, blocked.
Do TickTick and Todoist have an MCP server?
TickTick: yes (official). Todoist: yes (official).
Can an AI agent delete its TickTick or Todoist account?
TickTick: yes, in a browser. Todoist: not reached.
The drives and the category.
Put your own shortlist side by side.
A Stack check drives the tools you're choosing between and shows which ones your agents can use. $490 for three tools, ready in 24 hours.