Provides tools for interacting with the Dida365 (TickTick) API, enabling task management capabilities including creating, updating, and deleting tasks, as well as creating and managing projects/lists after user authorization.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Dida365 (TickTick) MCP Server add a task to buy groceries tomorrow at 5pm"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
This is a Model Context Protocol (MCP) server that provides tools for interacting with the Dida365 (TickTick) API. It allows AI assistants to manage tasks and projects in Dida365 after user authorization.
User authentication with Dida365
Get all projects (lists)
Get tasks from collection box
Create new tasks with various parameters
Update existing tasks in collection box
Delete tasks in collection box
Create new projects
Related MCP server: TickTick MCP
Node.js (v14 or higher)
npm or yarn
Dida365 (TickTick) account
Clone this repository
Install dependencies:
npm installOpen https://developer.dida365.com/manage and click "New App" to create your Dida365 (TickTick) app.
Click "Edit" app and configure the OAuth redirect URL "http://106.75.247.14:3999/oauth/callback"
Get your Client ID and Client Secret
Don't forget to replace {client_id} with you client_id
The server will return a form
Fill in your client_id and client_secret, then sumit to get your token.
Open Cursor and go to Settings > MCP
Click on "Add new global MCP server"
Add the follwing configuration to mcp.json:
"dida365": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"@smithery/cli@latest",
"run",
"@iamjzx/dida",
"--config",
"{\"token\":\"your token\"}"
]
}Save the file and enable the mcp.
Open Claude Desktop and go to Settings > Developer
Enable Developer Mode
Click on "Edit Config" to open your claude_desktop_config.json
Add the following configuration to the "mcpServers" section:
"dida365": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"@smithery/cli@latest",
"run",
"@iamjzx/dida",
"--config",
"{\"token\":\"your token\"}"
]
}Save the file and restart Claude Desktop
You can view the service runtime logs in the src/server.log file.
Due to the lack of api, we can't do the following:
Get tasks from a specific project
Update existing tasks in a specific project
Delete tasks in a specific project
Create new tasks in a specific project
ApiClient tool description
Inputs: message.
DataProcessor tool description
Inputs: message.
An example tool that processes messages
Inputs: message.
FileHandler tool description
Inputs: message.
MyTool tool description
Inputs: message.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 5 tools
The tool names are highly generic and vague, making it impossible to distinguish their purposes. Tools like 'api-client', 'data-processor', 'file-handler', and 'my-tool' could easily overlap in functionality, and 'example_tool' adds confusion without clear differentiation. This lack of specificity will likely cause agents to misselect tools due to ambiguous boundaries.
The naming conventions are inconsistent, mixing kebab-case (e.g., 'api-client'), snake_case (e.g., 'example_tool'), and camelCase (e.g., 'MyTool' in 'my-tool'). There is no predictable pattern in verb usage or structure, leading to a chaotic and unreadable set that lacks coherence.
With 5 tools, the count is reasonable for a server, but it feels borderline due to the vague and overlapping purposes. For a TickTick integration, this number might be thin if it aims to cover core task management features, but it's not extreme enough to score lower.
Given the server's name suggests a TickTick (Dida365) integration, the tool set is severely incomplete. There are no tools for core task management operations like creating, listing, updating, or deleting tasks, notes, or reminders. The generic tool names provide no coverage for the domain, leaving obvious gaps that will cause agent failures.
Manage tasks, Focus Zone, notes, projects, and task history from compatible AI assistants.
Task management for people and AI agents, with scoped OAuth access to issues, projects, and docs.
Task management for people and AI agents, with scoped OAuth access to issues, projects, and docs.
Create and manage MeisterTask projects, tasks, and notes from your AI assistant.
