MCPSERV.CLUB
jacepark12

TickTick MCP Server

MCP Server

Integrate TickTick with Claude via Model Context Protocol

Stale(60)
151stars
2views
Updated 12 days ago

About

A Python-based MCP server that connects to the TickTick API, allowing users to view, create, update, complete, and delete tasks and projects directly from Claude or other MCP clients.

Capabilities

Resources
Access data sources
Tools
Execute functions
Prompts
Pre-built templates
Sampling
AI model interactions

TickTick MCP Server – Bringing Your Task Management into the AI Realm

The TickTick MCP server solves a common pain point for developers building conversational agents: accessing and manipulating personal task data without exposing credentials or writing custom API wrappers. By exposing TickTick’s full feature set through the Model Context Protocol, an AI assistant such as Claude can read projects, create tasks, update priorities, and mark items complete—all through natural language interactions. This eliminates the need for separate authentication flows or manual data exports, letting developers focus on building richer conversational experiences.

At its core, the server translates MCP requests into TickTick API calls. When a user asks Claude to “add a meeting with Sarah next Tuesday,” the assistant forwards that intent as an MCP request. The server authenticates via OAuth2, automatically refreshing tokens, and then issues a POST to TickTick’s task endpoint. Because the server mirrors TickTick’s native capabilities—viewing projects, creating and updating tasks, deleting items, and marking completion—it offers a seamless bridge that feels native to the user. Developers can expose these actions as tool calls in their MCP client, enabling instant feedback and stateful interactions.

Key capabilities include:

  • Full CRUD on tasks and projects: Create, read, update, or delete any item in TickTick using simple language commands.
  • Rich task metadata handling: Titles, descriptions, due dates, priorities, and tags can all be set or modified.
  • Automatic token management: The server handles OAuth2 flow and refreshes tokens silently, so the AI never encounters expired credentials.
  • Dual‑platform support: In addition to standard TickTick, the server can be configured for Dida365 (the Chinese version), making it useful across regions.
  • Plug‑and‑play MCP integration: With a single configuration entry, Claude for Desktop or any other MCP client can start using the server as a tool.

Real‑world scenarios that benefit from this integration are abundant. Project managers can ask their assistant to schedule follow‑ups, while students might have the AI auto‑populate study tasks. Developers can build productivity bots that automatically sync meeting notes into TickTick, or create custom workflows where AI prompts users to break down large goals into actionable steps. Because the server exposes a consistent MCP interface, adding new features or switching to another task platform is as simple as updating the configuration.

In summary, TickTick MCP Server turns a traditional task management API into an interactive, AI‑ready service. It removes authentication friction, provides complete task control through natural language, and integrates effortlessly with any MCP‑compliant client—empowering developers to craft intelligent assistants that help users stay organized without leaving the chat.