# io.github.partymola/ticktick-mcp (oci · ghcr.io/partymola/ticktick-mcp) MCP server for TickTick task management: field-preserving updates and completion tracking. - Trust score: 34/100 (low) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - oci · `ghcr.io/partymola/ticktick-mcp`: 34/100 (this document), [markdown](https://verifymcp.io/servers/partymola-ticktick-mcp/ghcr-io-partymola-ticktick-mcp.md), [page](https://verifymcp.io/servers/partymola-ticktick-mcp/ghcr-io-partymola-ticktick-mcp) ## Channel facts - Registry: `oci` - Package: `ghcr.io/partymola/ticktick-mcp` - Version: `v0.6.1` - Transport: `stdio` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Supply Chain Security**: 0/100 - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package. - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - Install-script risk not yet assessed. - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - **Provenance & Transparency**: 32/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - License check failed: no license is declared. - Actively maintained (last published 1 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 63/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 5824 tokens (~416/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 17/100 - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 71/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 0% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Tool Safety**: 75/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ticktick_delete_tasks" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). **Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm. ## Install ### How do I install the io.github.partymola/ticktick-mcp server? io.github.partymola/ticktick-mcp runs locally as a container image, launched with docker run --rm -i -e TICKTICK_CLIENT_ID -e TICKTICK_CLIENT_SECRET -e TICKTICK_USERNAME -e TICKTICK_PASSWORD ghcr.io/partymola/ticktick-mcp:v0.6.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add partymola-ticktick-mcp -- docker run --rm -i -e TICKTICK_CLIENT_ID -e TICKTICK_CLIENT_SECRET -e TICKTICK_USERNAME -e TICKTICK_PASSWORD ghcr.io/partymola/ticktick-mcp:v0.6.1 ``` This image reads TICKTICK_CLIENT_ID, TICKTICK_CLIENT_SECRET, TICKTICK_USERNAME and TICKTICK_PASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### Cursor ```json { "mcpServers": { "partymola-ticktick-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "TICKTICK_CLIENT_ID", "-e", "TICKTICK_CLIENT_SECRET", "-e", "TICKTICK_USERNAME", "-e", "TICKTICK_PASSWORD", "ghcr.io/partymola/ticktick-mcp:v0.6.1" ] } } } ``` This image reads TICKTICK_CLIENT_ID, TICKTICK_CLIENT_SECRET, TICKTICK_USERNAME and TICKTICK_PASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### VS Code ```json { "servers": { "partymola-ticktick-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "TICKTICK_CLIENT_ID", "-e", "TICKTICK_CLIENT_SECRET", "-e", "TICKTICK_USERNAME", "-e", "TICKTICK_PASSWORD", "ghcr.io/partymola/ticktick-mcp:v0.6.1" ] } } } ``` This image reads TICKTICK_CLIENT_ID, TICKTICK_CLIENT_SECRET, TICKTICK_USERNAME and TICKTICK_PASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### Codex ```bash codex mcp add partymola-ticktick-mcp -- docker run --rm -i -e TICKTICK_CLIENT_ID -e TICKTICK_CLIENT_SECRET -e TICKTICK_USERNAME -e TICKTICK_PASSWORD ghcr.io/partymola/ticktick-mcp:v0.6.1 ``` This image reads TICKTICK_CLIENT_ID, TICKTICK_CLIENT_SECRET, TICKTICK_USERNAME and TICKTICK_PASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "partymola-ticktick-mcp": { "type": "local", "command": [ "docker", "run", "--rm", "-i", "-e", "TICKTICK_CLIENT_ID", "-e", "TICKTICK_CLIENT_SECRET", "-e", "TICKTICK_USERNAME", "-e", "TICKTICK_PASSWORD", "ghcr.io/partymola/ticktick-mcp:v0.6.1" ], "enabled": true } } } ``` This image reads TICKTICK_CLIENT_ID, TICKTICK_CLIENT_SECRET, TICKTICK_USERNAME and TICKTICK_PASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### Hermes ```yaml mcp_servers: partymola-ticktick-mcp: command: "docker" args: ["run", "--rm", "-i", "-e", "TICKTICK_CLIENT_ID", "-e", "TICKTICK_CLIENT_SECRET", "-e", "TICKTICK_USERNAME", "-e", "TICKTICK_PASSWORD", "ghcr.io/partymola/ticktick-mcp:v0.6.1"] ``` This image reads TICKTICK_CLIENT_ID, TICKTICK_CLIENT_SECRET, TICKTICK_USERNAME and TICKTICK_PASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### Netclaw ```json { "McpServers": { "partymola-ticktick-mcp": { "Transport": "stdio", "Command": "docker", "Arguments": [ "run", "--rm", "-i", "-e", "TICKTICK_CLIENT_ID", "-e", "TICKTICK_CLIENT_SECRET", "-e", "TICKTICK_USERNAME", "-e", "TICKTICK_PASSWORD", "ghcr.io/partymola/ticktick-mcp:v0.6.1" ] } } } ``` This image reads TICKTICK_CLIENT_ID, TICKTICK_CLIENT_SECRET, TICKTICK_USERNAME and TICKTICK_PASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container. ### Other ```json { "mcpServers": { "partymola-ticktick-mcp": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "TICKTICK_CLIENT_ID", "-e", "TICKTICK_CLIENT_SECRET", "-e", "TICKTICK_USERNAME", "-e", "TICKTICK_PASSWORD", "ghcr.io/partymola/ticktick-mcp:v0.6.1" ] } } } ``` This image reads TICKTICK_CLIENT_ID, TICKTICK_CLIENT_SECRET, TICKTICK_USERNAME and TICKTICK_PASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-04 (score 34, +1) No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-11-03 (score 33, 0) - [security regression] Provenance: fail → unverified - [functional] Package version: v0.6.0 → v0.6.1 ### 2026-11-02 (score 33, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-31 (score 32) First indexed and scored. ## MCP tools (14) ### `ticktick_filter_tasks` (~1201 tokens) Return the tasks matching every supplied filter criterion. Supports any combination of project, priority, tag, status, and a date window applied to either the due date (open tasks) or the completion timestamp (completed tasks). Args: detail (str, optional): ``"compact"`` (default) or ``"full"``. Compact drops the heavy ``content``/``desc``/checklist ``items`` blobs and bulky sync metadata, keeping id, projectId, title, dueDate, startDate, priority, status, isAllDay, timeZone, tags plus a ``contentPreview`` (first ~200 chars of content) so keyword search still works. Full returns the raw task objects unchanged. To edit a task, call ``ticktick_update_task`` with its id and only the fields to change, plus ``projectId`` for a completed task. filter_criteria (dict | str): A criteria object, or a JSON string that decodes to one. No value below reaches the query unchecked, and **any key not on this list is an error** rather than something ignored, so a mistyped key fails loudly. Recognised keys: * ``status``: ``"uncompleted"`` (default) or ``"completed"``. When ``"completed"`` you should supply ``completion_start_date`` and/or ``completion_end_date``; without dates the result is an empty list. * ``project_id`` (str): Limit to tasks in this project. Accepts the project's name as well as its ID (case-insensitive, trimmed). Two projects sharing a name is an error, not a guess, and so is a project the account does not have. * ``priority`` (int): 0=None, 1=Low, 3=Medium, 5=High. Must be a JSON integer; the string ``"3"`` and the float ``3.0`` are errors, as is any other value. * ``tag_label`` (str): Tag name (case-sensitive), non-empty. Surrounding whitespace is trimmed. * ``due_start_date`` / ``due_end_date`` (str): ISO date or… Input parameters: - `detail` (string) - `filter_criteria` (required) Output parameters: - `result` (string) ### `ticktick_get_unprocessed_completions` (~370 tokens) Returns completed tasks for a project that have NOT yet been marked as processed by a domain agent. Could be called at the beginning of each conversation to check for new completions. After reviewing each returned task, call ticktick_mark_completion_processed to record that it has been handled. A task completed through ticktick_complete_task is recorded by that tool, so what this returns is what was completed elsewhere, in the TickTick app or on another client, where a note may be waiting to be read. One exception: no recurring completion is recorded, because it files its completed instance under an id the completing call never sees, so that instance appears here whoever completed it. Args: project_id (str): TickTick project ID or name to check. Required. Accepts the project's name as well as its ID (case-insensitive, trimmed; "Inbox" resolves to the inbox). Two projects sharing a name is an error, not a guess. days (int): How many days back to look for completions. Default 30. Returns: JSON list of unprocessed task objects (may be empty). Each object includes: id, title, projectId, completedTime, content. Error: {"error": "...", "status": "error"} Usage Guide: - Call once per project at the start of each conversation. - For each returned task: read the content field, log meaningful outcomes if appropriate, then call ticktick_mark_completion_processed. - Example: ticktick_get_unprocessed_completions( project_id="your_project_id_here", days=30 ) Input parameters: - `days` (integer) - `project_id` (string, required) Output parameters: - `result` (string) ### `ticktick_mark_completion_processed` (~345 tokens) Records that a domain agent has processed a completed task. Call this after reviewing each task returned by ticktick_get_unprocessed_completions. The task will no longer appear in future calls to that tool. Args: task_id (str): Full TickTick task ID. Required. project_id (str): Project ID or name the task belongs to. Required. Accepts the project's name as well as its ID (case-insensitive, trimmed; "Inbox" resolves to the inbox). Two projects sharing a name is an error, not a guess. title (str, optional): Task title (stored for human-readable audit trail). completed_time (str, optional): ISO completion timestamp from the task object. notes (str, optional): Brief notes on how the completion was handled. Returns: {"status": "ok", "task_id": "..."} on success. {"status": "already_processed", "task_id": "..."} if already recorded. {"error": "...", "status": "error"} on failure. Usage Guide: - Call once per task after finishing your handling of it. - Example: ticktick_mark_completion_processed( task_id="abc123", project_id="your_project_id_here", title="Fix kitchen tap", completed_time="2025-06-01T19:00:00+01:00", notes="Replaced ceramic disc, resolved" ) Input parameters: - `completed_time` - `notes` - `project_id` (string, required) - `task_id` (string, required) - `title` Output parameters: - `result` (string) ### `ticktick_convert_datetime_to_ticktick_format` (~341 tokens) Convert an ISO 8601 datetime string into TickTick's storage format. TickTick uses ``YYYY-MM-DDTHH:MM:SS+0000`` (UTC offset, no colon). Args: datetime_iso_string (str): ISO 8601 datetime, e.g. ``"2026-04-13T20:45:00+01:00"``. Naive strings are accepted and interpreted in ``tz``. tz (str): IANA timezone name used for the UTC conversion, e.g. ``"Europe/London"`` or ``"America/Los_Angeles"``. Returns: On success: ``{"ticktick_format": "2026-04-13T19:45:00+0000"}``. On parse error: ``{"error": "Invalid datetime format...", "status": "error"}``. On any other conversion error: ``{"error": "Conversion failed: ...", "status": "error"}``. Agent Usage Guide: - Call this when you need to set ``startDate`` or ``dueDate`` on a task dict by hand. The ``ticktick_create_task`` and ``ticktick_update_task`` tools accept ISO strings directly and run this conversion internally. Example: ticktick_convert_datetime_to_ticktick_format( datetime_iso_string="2026-04-13T20:45:00+01:00", tz="Europe/London", ) Input parameters: - `datetime_iso_string` (string, required) - `tz` (string, required) Output parameters: - `result` (string) ### `ticktick_create_task` (~665 tokens) Create a new task. Args: title (str): Task title. Required. project_id (str, optional): Project ID or name. Defaults to inbox. Accepts the project's name as well as its ID (case-insensitive, trimmed; "Inbox" resolves to the inbox). Two projects sharing a name is an error, not a guess. content (str, optional): Long-form content (markdown supported). desc (str, optional): Short description / checklist subtitle. all_day (bool, optional): True for all-day tasks. start_date (str, optional): ISO 8601 start datetime, e.g. ``"2026-04-13T09:00:00+01:00"``. due_date (str, optional): ISO 8601 due datetime. expected_day_of_week (str, optional): English weekday name. Required when ``due_date`` is set; mismatch returns an error. time_zone (str, optional): IANA timezone. Defaults to the system timezone for date conversion. reminders (list[str], optional): TickTick trigger strings, e.g. ``["TRIGGER:-PT30M"]``. repeat (str, optional): Recurrence rule (RFC 5545 RRULE). priority (int, optional): 0=None, 1=Low, 3=Medium, 5=High. sort_order (int, optional): Position within project. items (list[dict], optional): Subtask items. Returns: JSON object containing the created task. ``_verification_warnings`` carries everything worth knowing about what landed: a response that did not match what was sent, a due date that is missing and so will fire no reminder at all or all-day and so no timed one, a title character TickTick parses as a marker, and content longer than the compact preview. On failure: ``{"error": "...", "status": "error"}``. Limitations: - ``builder()`` in ``ticktick-py`` sometimes omits dates, reminders, priority and timezone; we re-populate them after the call. Agent Usage Guide: - Always pair ``due_date`` with ``expected_day_of_week``. - Pass a project name directly, or list ids with ticktick_get_all(sear… Input parameters: - `all_day` - `content` - `desc` - `due_date` - `expected_day_of_week` - `items` - `priority` - `project_id` - `reminders` - `repeat` - `sort_order` - `start_date` - `time_zone` - `title` (string, required) Output parameters: - `result` (string) ### `ticktick_update_task` (~563 tokens) Update an existing task without wiping unmodified fields. Send only the fields to change. The tool fetches the current task and overlays ONLY the fields the caller explicitly set (``exclude_unset=True``), sending the other editable fields back with them. Args: task_object (TaskObject): Must include ``id``. All other fields are optional; set only the ones you want to change. When ``dueDate`` is set you must also set ``expectedDayOfWeek``. Returns: JSON object containing the updated task. ``_verification_warnings`` is attached when the response did not match what we sent, when a ``reminders: []`` removal could not be confirmed, and when ``status: 0`` was set but the local completion record could not be cleared. That last one says nothing about whether the update itself landed. On failure: ``{"error": "...", "status": "error"}``. Limitations: - Read-only API fields (``creator``, ``etag``, ``createdTime``, ``modifiedTime``, ``deleted``, ``kind``, ``isFloating``) are stripped from the main update call. - Setting ``status: 0`` also clears any local record of this task's earlier completion, so a later completion is surfaced by ``ticktick_get_unprocessed_completions`` again. A clear that fails is reported in ``_verification_warnings``. - ``reminders: []`` removes whatever reminders the task has at that moment, so do not send it back from an old copy of the task. ``_verification_warnings`` says so if the removal could not be confirmed. ``reminders: null`` leaves them alone. A non-empty list replaces them. Sending ``dueDate`` and ``startDate`` as ``null`` removes the date, and its reminders with it. Agent Usage Guide: - To reschedule a task, send a single update with the new ``dueDate`` + ``expectedDayOfWeek``. Do NOT complete and recreate. Example: ticktick_update_task(task_object={ "id": "60ca9dbc8f08516d9dd56324",… Input parameters: - `task_object` (required) Output parameters: - `result` (string) ### `ticktick_delete_tasks` (~290 tokens) Delete one or more tasks. Args: task_ids (str | list[str]): A single task ID, or a list of IDs. An empty list returns an error. project_id (str, optional): Used to construct a minimal delete payload when ``get_by_id`` cannot find the task locally (typical for completed tasks). Accepts the project's name as well as its ID (case-insensitive, trimmed; "Inbox" resolves to the inbox). Two projects sharing a name is an error, not a guess. Returns: ``{"status": "success", "deleted_count": N, "tasks_deleted_ids": [...]}`` on success. Tasks that could not be matched at all are returned as ``status="not_found"`` with ``missing_ids`` / ``invalid_ids`` arrays. Partial success surfaces ``warnings``. Empty input: ``{"status": "error", "message": "No task IDs..."}``. Agent Usage Guide: - For tasks already completed in TickTick, supply ``project_id`` -- ``get_by_id`` does not see completed tasks. Example: ticktick_delete_tasks( task_ids=["abc123", "def456"], project_id="", ) Input parameters: - `project_id` - `task_ids` (required) Output parameters: - `result` (string) ### `ticktick_get_tasks_from_project` (~468 tokens) Return every open task in a project. Args: project_id (str): The project's ID or name. Accepts the project's name as well as its ID (case-insensitive, trimmed; "Inbox" resolves to the inbox). Two projects sharing a name is an error, not a guess. List them with ``ticktick_get_all(search="projects")``. detail (str, optional): ``"compact"`` (default) or ``"full"``. Compact drops the heavy ``content``/``desc``/checklist ``items`` blobs and bulky sync metadata, keeping id, projectId, title, dueDate, startDate, priority, status, isAllDay, timeZone, tags plus a ``contentPreview`` (first ~200 chars of content) so keyword search still works. Full returns the raw task objects unchanged. Returns: Compact (default): JSON list of compact task objects. If the compact payload would still exceed the size budget, the soonest-due tasks are returned and a final ``_truncation_note`` element reports how many were omitted -- nothing is dropped silently. Full: JSON list of raw task objects (empty list if none). On failure: ``{"error": "...", "status": "error"}``. Limitations: - Completed tasks are NOT included. - Compact output is for browsing only. To edit a task, call ``ticktick_update_task`` with its id and only the fields to change. Get the full content of a single task with ``ticktick_get_by_id``, or pass ``detail="full"``. Freshness: Local state is synced from the server at most once per throttle window (default 15s, ``TICKTICK_MCP_SYNC_TTL_SECONDS``); an edit made elsewhere within that window may not be visible yet. Call ``ticktick_sync`` to force an immediate refresh. Example: ticktick_get_tasks_from_project( project_id="" ) Input parameters: - `detail` (string) - `project_id` (string, required) Output parameters: - `result` (string) ### `ticktick_complete_task` (~432 tokens) Mark a task as completed. Completing a task here also records it as processed, so it does not come back from ``ticktick_get_unprocessed_completions``. That queue is for completions made elsewhere, where a note may be waiting to be read. There is no need to call ``ticktick_mark_completion_processed`` afterwards. Args: task_id (str): The task's full ID. Returns: After a completion call, a JSON object carrying ``outcome``. ``completed``: the task is no longer open. It has usually left the active list, so no task object comes back; one that can still be read is returned at status=2. ``completed_recurring``: the next occurrence, at status=0, with ``next_occurrence_id``. ``uncertain``: a non-recurring task is still open, with ``_verification_warnings`` saying so. ``completion_recorded`` reports whether the local record was written. Present only when a non-recurring task completed; absent wherever nothing was recorded, which is every recurring completion and ``outcome: "uncertain"``. The task is complete either way. Missing task: ``{"status": "not_found", "error": "..."}``. Other failures: ``{"error": "...", "status": "error"}``. Limitations: - Once completed, the ``content`` field becomes immutable. Update content with resolution notes BEFORE calling this tool. - A recurring task's completion is never recorded, whatever the outcome: completing one files the completed instance under an id this tool never sees. That instance reaches the unprocessed queue. Do not mark the series id processed by hand instead; it is not the id the queue is showing. Example: ticktick_complete_task(task_id="60ca9dbc8f08516d9dd56324") Input parameters: - `task_id` (string, required) Output parameters: - `result` (string) ### `ticktick_move_task` (~209 tokens) Move a task into a different project. Args: task_id (str): The task's full ID. new_project_id (str): Destination project's ID or name. Accepts the project's name as well as its ID (case-insensitive, trimmed; "Inbox" resolves to the inbox). Two projects sharing a name is an error, not a guess. Returns: JSON object containing the moved task. If the target project cannot be looked up locally, the move is still attempted. Missing source task (no projectId field): ``{"status": "not_found", ...}``. Other failures: ``{"error": "...", "status": "error"}``. Example: ticktick_move_task( task_id="60ca9dbc8f08516d9dd56324", new_project_id="", ) Input parameters: - `new_project_id` (string, required) - `task_id` (string, required) Output parameters: - `result` (string) ### `ticktick_make_subtask` (~213 tokens) Nest ``child_task_id`` under ``parent_task_id``. Args: parent_task_id (str): The parent task's ID. child_task_id (str): The task to become a subtask. Must differ from ``parent_task_id`` and live in the same project. Returns: On success: ``{"status": "success", "updated_parent_task": ..., "api_response": ...}``. Missing child / parent: ``{"status": "not_found", "error": "..."}``. Cross-project: ``{"error": "...same project...", "child_project": "...", "parent_project": "..."}``. Example: ticktick_make_subtask( parent_task_id="60ca9dbc8f08516d9dd56324", child_task_id="60ca9dbc8f08516d9dd56325", ) Input parameters: - `child_task_id` (string, required) - `parent_task_id` (string, required) Output parameters: - `result` (string) ### `ticktick_get_by_id` (~188 tokens) Look up any object (task, project, tag) by its ID. Args: obj_id (str): The object's full ID. Returns: JSON object of the matching record, or an empty object ``{}`` if nothing has that id. Branch on emptiness. On failure: ``{"error": "...", "status": "error"}``. Freshness: Local state is synced from the server at most once per throttle window (default 15s, ``TICKTICK_MCP_SYNC_TTL_SECONDS``); an edit made elsewhere within that window may not be visible yet. Call ``ticktick_sync`` to force an immediate refresh. Example: ticktick_get_by_id(obj_id="60ca9dbc8f08516d9dd56324") Input parameters: - `obj_id` (string, required) Output parameters: - `result` (string) ### `ticktick_get_all` (~331 tokens) Dump everything of a single kind from the local sync state. Args: search (str): Either ``"tasks"``, ``"projects"`` or ``"tags"`` (case-insensitive). detail (str, optional): ``"compact"`` (default) or ``"full"``. Accepted for parity with the other list tools and validated here. It has no effect on the ``"projects"``/``"tags"`` searches (those return non-task records in full) nor on the currently inert ``"tasks"`` search -- for a compact task list use ``ticktick_filter_tasks`` or ``ticktick_get_tasks_from_project``. Returns: For ``"projects"``: JSON list, inbox prepended as ``{"id": , "name": "Inbox"}``. For ``"tags"``: JSON list of tag objects. For ``"tasks"``: see Limitations. Unknown search type: ``{"error": "Invalid search type...", "status": "error"}``. Limitations: - ``"tasks"`` triggers a fetch of every open task across all projects, but the current implementation returns ``None`` rather than a JSON string. Use ``ticktick_filter_tasks({"status": "uncompleted"})`` for a proper (compact) JSON response. Example: ticktick_get_all(search="projects") Input parameters: - `detail` (string) - `search` (string, required) Output parameters: - `result` (string) ### `ticktick_sync` (~208 tokens) Force an immediate refresh of TickTick state from the server. The active-read tools (``ticktick_get_by_id``, \``ticktick_get_tasks_from_project``, ``ticktick_filter_tasks``) already auto-refresh at most once per throttle window (default 15s, overridable via ``TICKTICK_MCP_SYNC_TTL_SECONDS``). Call this when you need an immediate refresh -- e.g. you just changed something in the TickTick app on another device, or a read looks stale and you want to be certain before acting. Returns: ``{"status": "synced", "task_count": N, "project_count": M}`` on success. ``{"status": "error", "detail": "..."}`` if the refresh failed -- the previous (stale) state is still served by the read tools, so callers can continue with reduced confidence. Example: ticktick_sync() Output parameters: - `result` (string) ## Diagnostics Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/partymola-ticktick-mcp/ghcr-io-partymola-ticktick-mcp#diagnostics ## Score history - 2026-11-05: 34 - 2026-11-04: 34 - 2026-11-03: 33 - 2026-11-02: 33 - 2026-11-01: 32 - 2026-10-31: 32 ## Common questions ### What is the io.github.partymola/ticktick-mcp server? io.github.partymola/ticktick-mcp is listed in the public MCP registry as io.github.partymola/ticktick-mcp. MCP server for TickTick task management: field-preserving updates and completion tracking. This page covers its container image (ghcr.io/partymola/ticktick-mcp). ### Is the io.github.partymola/ticktick-mcp server safe to use? io.github.partymola/ticktick-mcp scores 34 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the io.github.partymola/ticktick-mcp server expose? io.github.partymola/ticktick-mcp exposes 14 tools: ticktick_filter_tasks, ticktick_get_unprocessed_completions, ticktick_mark_completion_processed, ticktick_convert_datetime_to_ticktick_format, ticktick_create_task, and 9 more. Their descriptions and schemas cost roughly 5,824 tokens of context every time the server is loaded. ### Is the io.github.partymola/ticktick-mcp server still maintained? io.github.partymola/ticktick-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - GitHub Container Registry: https://ghcr.io/partymola/ticktick-mcp - Repository: https://github.com/partymola/ticktick-mcp - Changelog RSS feed: https://verifymcp.io/servers/partymola-ticktick-mcp/ghcr-io-partymola-ticktick-mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/partymola-ticktick-mcp/ghcr-io-partymola-ticktick-mcp.json - HTML version of this page: https://verifymcp.io/servers/partymola-ticktick-mcp/ghcr-io-partymola-ticktick-mcp