TickTick
by TickTick
Read, create, complete and delete TickTick tasks, lists, habits and focus records from an AI agent. Anthropic lists 92 tool names, but they are 47 tools listed twice under two naming conventions. OAuth or a bearer token, two scopes.
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.
Connect TickTick via MCP
https://mcp.ticktick.comWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
TickTick Tools & Capabilities (47)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Two scopes, and the boundary is in the wrong place. The RFC 9728 descriptor advertises
tasks:readandtasks:write. Nothing separates the routine write from the irreversible one: the same grant that lets an agent tick off a task lets it calldelete_comment,delete_focusanddelete_project_group. The scope *names* also understate the reach — they say "tasks", while the surface writes habits, folders, sections, tags and focus records too. Advertised scopes are not enforced scopes, and we could not verify enforcement from outside. - Three deletes have no documented undo. TickTick describes
delete_taskas moving a task to the Trash and documents recovering tasks from there. It documents no equivalent fordelete_comment,delete_focusordelete_project_group.delete_project_groupdissolves a folder and ungroups every list inside it, which is a structural change to the sidebar rather than the removal of a record. - Anthropic's tool list is missing the collaboration tools.
assign_task,unassign_taskandproject_memberare documented by TickTick and absent from the directory snapshot dated 2026-08-16. An audit built on the directory alone will not see them. - We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail or
readOnlyHint/destructiveHintvalue is published here. - Free-plan quotas are the metering exposure. TickTick's pricing page caps a free account at 9 lists, 99 tasks per list, 5 habits, 5 countdowns and 19 checklist items per task, against 299 / 999 / 299 / 299 / 199 on Premium.
batch_add_tasksandcreate_projectconsume that quota. No tool spends money, changes a subscription or touches billing. - Per-call ceilings apply. TickTick documents 20 tasks per
complete_tasks_in_projectrequest, a 14-day maximum range onlist_undone_tasks_by_date, one month perget_focuses_by_timequery, and 90 days of backdating onupsert_habit_checkins. - Streamable HTTP only. TickTick states SSE is not supported, so an SSE-only client cannot connect.
- The feature surface is deliberately partial. TickTick states the server covers basic task, list, habit, focus-record and countdown operations and that other advanced features are not supported yet. There is no tool for attachments, reminders, calendar events or notes.
- Shared-list writes may be visible to colleagues. Whether
create_task,complete_task,move_taskordelete_tasknotifies other members depends on per-list notification settings the agent cannot inspect. Treat any write on a shared list as potentially visible. - No rate limits are published for the MCP endpoint. TickTick documents none, and we did not test for any. Treat throughput as unknown rather than unlimited.
Frequently asked questions
Forty-seven, not the 92 Anthropic's directory appears to list. Those 92 names are 45 capabilities published twice, once in snake_case and once in kebab-case, plus search and fetch which appear only once. Counting the listing without normalising the separator doubles the apparent surface of this connector.
No. TickTick's own documentation describes delete_task as moving a task to the Trash, and its help centre describes recovering deleted tasks from there. Three other delete tools exist though — delete_comment, delete_focus and delete_project_group — and TickTick documents no Trash equivalent for any of them.
Yes, through a tool Anthropic's directory does not list. TickTick's MCP documentation names assign_task, unassign_task and project_member, and its collaboration guide states an assigned member receives a notification reminder in the Notification Center. Assignment on a shared list is therefore an outbound action reaching a colleague.
Two, and neither separates a read from a delete. The server's RFC 9728 descriptor advertised tasks:read and tasks:write on 2026-08-22. Granting tasks:write covers creating a task and deleting a comment alike, and the scope names cover only tasks while the tool surface also writes habits, folders, tags and focus records.
No. TickTick's documentation states the MCP server supports only the Streamable HTTP transport and does not support SSE, so a client limited to SSE cannot connect directly. The endpoint is https://mcp.ticktick.com and the same doc lists working configurations for Claude, ChatGPT, Cursor, VS Code and Codex.
No, but the free plan caps what the write tools can create. TickTick's pricing page lists 9 lists, 99 tasks per list, 5 habits and 5 countdowns on the free plan against 299, 999, 299 and 299 on Premium at US$49.99 a year. Batch creation tools reach those ceilings quickly.
No, under normal use. TickTick states that its OAuth authorization supports automatic token refresh, so reauthorization is needed only after a long period of inactivity has expired the token, or if you manually revoke access. A bearer token from Settings then Account then API Token is the documented alternative.
TickTick attributes this to model behaviour rather than the server. Its documentation lists three causes: the model misread the request, it chose the wrong tool, or it passed wrong parameters. The suggested fixes are naming the list, date or priority explicitly, and splitting a complex request so you confirm the target before the action runs.
Sources
- TickTick MCP setup and tool table (retrieved 2026-08-22). The page is client-rendered; the article text is served in the embedded
__NEXT_DATA__payload, which is where the tool table and FAQ were read from. · retrieved 2026-08-22 - TickTick × AI Use Cases, example prompts (retrieved 2026-08-22, read from the same payload) · retrieved 2026-08-22
- TickTick help centre, "How Teams Can Collaborate" — assignment and notification behaviour (retrieved 2026-08-22) · retrieved 2026-08-22
- TickTick help centre machine index,
llms.txt(retrieved 2026-08-22). It indexes 13 articles and does not list the MCP page. · retrieved 2026-08-22 - TickTick pricing and plan limits (retrieved 2026-08-22) · retrieved 2026-08-22
- Live auth posture check: anonymous initialize to
https://mcp.ticktick.comreturned 401 with awww-authenticatechallenge naming the resource metadata document, and RFC 9728 metadata athttps://mcp.ticktick.com/.well-known/oauth-protected-resourcereturnedscopes_supportedoftasks:readandtasks:write(2026-08-22) · retrieved 2026-08-22 - Authorization server metadata — as declared by the resource, served at
https://mcp.ticktick.com/.well-known/oauth-authorization-server(retrieved 2026-08-22) · retrieved 2026-08-22 help.ticktick.com/robots.txtandticktick.com/robots.txt— both permit the paths used here; only/forumis disallowed and noContent-Signalis set (retrieved 2026-08-22) · retrieved 2026-08-22- Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- TickTick support — · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- TickTick
- Tools
- 47
- Domain
- mcp.ticktick.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.