TickTick MCP integration for AI agents.
Connect AI agents to TickTick through 21 structured actions, including get habit, batch add tasks, delete project, and complete task. Review authentication…
- ACTION CONTRACTS
- 21
- AUTHENTICATION
- OAuth 2.0 + API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the TickTick integration exposes
The TickTick Agent App exposes 21 provider-backed actions for productivity work. Its current contract lets an authorized agent get a ticktick habit by its habit id, batch create multiple ticktick tasks in one request, and delete a ticktick project by project id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0 and API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected TickTick account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real TickTick capabilities.
Showing 12 of 21 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_habitREADGet a TickTick habit by its habit ID.
INPUTS: habitId
batch_add_tasksWRITEBatch create multiple TickTick tasks in one request.
INPUTS: tasks
delete_projectHIGH IMPACTDelete a TickTick project by project ID.
INPUTS: projectId
complete_taskREVIEWMark a TickTick task as completed.
INPUTS: projectId / taskId
create_or_update_habit_checkinWRITECreate or update a TickTick habit check-in for a date stamp.
INPUTS: habitId / stamp / time / opTime / value
create_projectWRITECreate a TickTick project.
INPUTS: projectId / name / color / sortOrder / viewMode
create_taskWRITECreate a TickTick task under a project.
INPUTS: projectId / title / content / desc / isAllDay
create_task2WRITEDeprecated compatibility alias for create_task.
INPUTS: projectId / title / content / desc / isAllDay
delete_taskHIGH IMPACTDelete a TickTick task by project ID and task ID.
INPUTS: projectId / taskId
filter_tasksREVIEWFilter TickTick tasks by project, date range, priority, tags, and status.
INPUTS: projectIds / startDate / endDate / priority / tag
get_project_by_idREADGet a TickTick project by its project ID.
INPUTS: projectId
get_project_with_dataREADGet a TickTick project together with its undone tasks and columns.
INPUTS: projectId
INPUT CONTRACTS
Know what the action needs before it runs.
get_habit
habitIdOPTIONAL- The TickTick habit ID.
batch_add_tasks
tasksOPTIONAL- The TickTick tasks to create.
delete_project
projectIdOPTIONAL- The TickTick project ID.
complete_task
projectIdOPTIONAL- The TickTick project ID.
taskIdOPTIONAL- The TickTick task ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Habit
Get a TickTick habit by its habit ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_habitControl Batch Add Tasks
Batch create multiple TickTick tasks in one request. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
batch_add_tasksVerify with Batch Add Tasks
Batch create multiple TickTick tasks in one request. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
batch_add_tasksSAFETY BOUNDARY
Operate TickTick with explicit limits
- Authorize TickTick with OAuth 2.0 and API key and grant only the provider access required by the selected actions.
- 10 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_project` and `delete_task` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `ticktick.write` and `ticktick.read`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the TickTick task completed successfully.
CONNECTION MODEL
OAuth 2.0 + API key
Paste a TickTick OAuth access token. It is sent with the Authorization Bearer header.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 9
- WRITE SIGNALS
- 8
- HIGH IMPACT
- 2
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by TickTick.