TickTick

Read, create, complete and delete TickTick tasks, lists, habits and focus records.

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

What the TickTick connector does

The TickTick MCP server connects a TickTick account — a cross-platform task manager with habits, a Pomodoro timer and countdowns — to Claude, ChatGPT and any MCP client. It provides 47 tools that search, create, complete, move and delete tasks, lists, folders, tags, habits and focus records. Sign-in is OAuth, or a bearer token where a client cannot do OAuth.

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.

TickTick tools (47)

  • get_user_preference
  • get-user-preference
  • search_task
  • search-task
  • get_task_by_id
  • get-task-by-id
  • list_undone_tasks_by_time_query
  • list-undone-tasks-by-time-query
  • list_undone_tasks_by_date
  • list-undone-tasks-by-date
  • list_completed_tasks_by_date
  • list-completed-tasks-by-date
  • filter_tasks
  • filter-tasks
  • list_projects
  • list-projects
  • create_project
  • create-project
  • update_project
  • update-project
  • get_project_by_id
  • get-project-by-id
  • get_project_with_undone_tasks
  • get-project-with-undone-tasks
  • get_task_in_project
  • get-task-in-project
  • list_columns
  • list-sections
  • create_column
  • create-section
  • update_column
  • update-section
  • list_project_groups
  • list-folders
  • create_project_group
  • create-folder
  • update_project_group
  • update-folder
  • delete_project_group
  • delete-folder
  • create_task
  • create-task
  • batch_add_tasks
  • batch-add-tasks
  • complete_task
  • complete-task
  • complete_tasks_in_project
  • complete-tasks-in-project
  • update_task
  • update-task
  • move_task
  • move-task
  • batch_update_tasks
  • batch-update-tasks
  • delete_task
  • delete-task
  • get_comment
  • get-comment
  • add_comment
  • add-comment
  • delete_comment
  • delete-comment
  • list_tags
  • list-tags
  • create_tag
  • create-tag
  • list_habits
  • list-habits
  • list_habit_sections
  • list-habit-sections
  • create_habit
  • create-habit
  • update_habit
  • update-habit
  • get_habit
  • get-habit
  • get_habit_checkins
  • get-habit-check-ins
  • upsert_habit_checkins
  • log-habit-check-ins
  • get_focuses_by_time
  • get-focuses-by-time
  • get_focus
  • get-focus
  • create_focus
  • create-focus
  • delete_focus
  • delete-focus
  • list_countdowns
  • list-countdowns
  • search
  • fetch

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:read and tasks:write. Nothing separates the routine write from the irreversible one: the same grant that lets an agent tick off a task lets it call delete_comment, delete_focus and delete_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_task as moving a task to the Trash and documents recovering tasks from there. It documents no equivalent for delete_comment, delete_focus or delete_project_group. delete_project_group dissolves 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_task and project_member are 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/destructiveHint value 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_tasks and create_project consume that quota. No tool spends money, changes a subscription or touches billing.
  • Per-call ceilings apply. TickTick documents 20 tasks per complete_tasks_in_project request, a 14-day maximum range on list_undone_tasks_by_date, one month per get_focuses_by_time query, and 90 days of backdating on upsert_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_task or delete_task notifies 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

How many tools does the TickTick MCP server actually have?

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.

Can the TickTick connector delete a task permanently?

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.

Can the TickTick connector notify or assign work to another person?

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.

What OAuth permissions does the TickTick MCP server request?

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.

Does TickTick MCP work with a client that only supports SSE?

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.

Do I need a TickTick Premium subscription to use the MCP server?

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.

Do I have to sign in again each time I restart my AI client?

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.

Why did the TickTick connector do the wrong thing with my task?

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

Use it in an agent

Put TickTick to work.

Connect TickTick once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.