Dida365 (TickTick) Service Endpoint for AI Orchestration

This package functions as an MCP endpoint, providing a structured interface for artificial intelligence agents to interface with the Dida365 (TickTick) ecosystem. Authorization via the user's credentials is required before operations can commence.

Core Capabilities

• Secure user credential exchange with Dida365.
• Fetching all defined organizational containers (projects/lists).
• Accessing items stored within the designated collection inbox.
• Programmatic generation of novel tasks, supporting comprehensive parameter specification.
• In-place modification of existing items within the inbox context.
• Removal of specified items from the inbox.
• Initiating the creation of new project containers.

Prerequisites for Local Deployment

To run this component locally, ensure you have the following prerequisites met:

• A functioning Node.js runtime (version 14 or newer is required).
• A package manager: npm or yarn.
• An active Dida365 (TickTick) user account.

Recommended Execution Method (Local Cloning)

We strongly advise cloning this repository and executing the service within your local environment:

Setup Instructions

1. Duplicate the repository contents to your local machine.
2. Install necessary dependencies:

bash npm install

Operational Guide

Securing the Authorization Token

1. Navigate to the Dida365 Developer Portal: https://developer.dida365.com/manage and instantiate a "New App".
2. Edit the newly created application settings. Configure the OAuth redirection endpoint to point specifically to http://106.75.247.14:3999/oauth/callback.
3. Record your Client ID and Client Secret.
4. Initiate the authorization sequence using this URI structure: https://dida365.com/oauth/authorize?scope=tasks%3Aread%20tasks%3Awrite&client_id={client_id}&state=state&redirect_uri=http%3A%2F%2F106.75.247.14%3A3999%2Foauth%2Fcallback&response_type=code

Remember to substitute {client_id} with your actual client identifier.

The server interface will subsequently present a form requiring input of your Client ID and Client Secret to finalize token acquisition.

Integration Configuration for Client Applications

For Cursor Users

1. Access Cursor's configuration panel: Settings > MCP.
2. Select the option to "Add new global MCP server".
3. Incorporate the following JSON configuration snippet into your mcp.json file:

"dida365": { "command": "cmd", "args": [ "/c", "npx", "-y", "@smithery/cli@latest", "run", "@iamjzx/dida", "--config", "{\"token\":\"your token\"}" ] }

1. Persist the changes and activate the MCP feature.

For Claude Desktop Users

1. Open Claude Desktop settings and navigate to the Developer section.
2. Activate Developer Mode.
3. Open the configuration file by selecting "Edit Config" (claude_desktop_config.json).
4. Augment the "mcpServers" array with this configuration:

"dida365": { "command": "cmd", "args": [ "/c", "npx", "-y", "@smithery/cli@latest", "run", "@iamjzx/dida", "--config", "{\"token\":\"your token\"}" ] }

1. Save the configuration file and restart the Claude Desktop application.

Operational Logging

Diagnostic output regarding the service's runtime behavior can be examined within the src/server.log file.

Current Functional Limitations

Due to constraints originating from the exposed API surface, the following granular management operations are currently unavailable:

1. Querying tasks belonging to a specific project context.
2. Modifying tasks residing within a designated project.
3. Executing deletion commands on tasks tied to a particular project.
4. Instantiating new tasks directly within a specified project container.