Dida365

You can run and use the Dida365 MCP Server to connect TickTick or Dida365 with your MCP-enabled client, enabling task and project management through controlled, AI-assisted interactions. This server handles authentication, data access, and real-time syncing, letting you create, read, update, and complete items through MCP tools with optional read-only protection.

How to use

To start using the Dida365 MCP Server, you need to obtain OAuth credentials for a TickTick or Dida365 account and configure an MCP client to load the server. You can operate in standard mode or opt into read-only mode for safety during demonstrations or autonomous AI usage.

How to install

Prerequisites you must have installed on your system before proceeding:

• Node.js 16+ (with npm)
• TypeScript 5.0+ is used in the server codebase

Choose one of the following installation approaches. Use whichever fits your workflow.

• Ensure you have an OAuth client, then load the MCP server with npx
• Configure your MCP client to load the server from the command shown below

Option B: Local development from source (clone, build, and run)

Proceed with the steps that match your chosen approach.

## Quick start with npx
# Step 1: Get OAuth credentials (see Getting OAuth Credentials section)
# Step 2: Configure your MCP client using the snippet in the Quick Start
# Step 3: Restart your MCP client
# Step 4: Authorize access when prompted by the AI tool
# Step 5: Verify the server loaded in your MCP client tools list

## Local development from source
# Prerequisites handled above
# Step 1: Clone the repository
# Step 2: Install dependencies
npm install
# Step 3: Create environment file with credentials
# DIDA365_CLIENT_ID=your_client_id_here
# DIDA365_CLIENT_SECRET=your_client_secret_here
# DIDA365_REGION=china  # or 'international'
# Step 4: Build
npm run build
# Step 5: Run
npm run dev
# Step 6: Configure your MCP client to point to the built index.js
# Example for a local MCP client: use the following stdio config (example shows path to built file)

Additional configuration and notes

OAuth credentials are essential. You must register your application with the TickTick or Dida365 developer center, obtain a Client ID and Client Secret, and set the Redirect URI to http://localhost:8521/callback. Tokens are region-specific and refresh automatically, so you may reauthorize when changing regions.

MCP client configuration for the standard runtime uses a stdio server defined with an MCP command and environment variables. The typical runtime entry uses npx to load the server image, with credentials supplied as environment variables.

{
  "mcpServers": {
    "dida365": {
      "command": "npx",
      "args": [
        "-y",
        "dida365-mcp-server@latest"
      ],
      "env": {
        "DIDA365_CLIENT_ID": "your_client_id_here",
        "DIDA365_CLIENT_SECRET": "your_client_secret_here",
        "DIDA365_REGION": "china"
      }
    }
  }
}

Security and best practices

Use read-only mode when you want the MCP server to access data without making changes. This helps ensure safe interactions for autonomous agents or demonstrations.

Getting OAuth Credentials

To use this MCP server, obtain OAuth credentials from your TickTick or Dida365 developer portal. Set the Redirect URI to http://localhost:8521/callback exactly.

Store credentials securely and configure them in your MCP client as shown in the configuration examples.

Advanced configuration

Enable read-only mode by adding the --readonly flag to the startup arguments when you load the MCP server via npx or your local build. In read-only mode, the server can read data and revoke tokens but cannot create, update, or delete projects or tasks.

Terminology and resources

A bilingual terminology resource is available to help MCP interactions map Chinese terms to the correct tool parameters, such as translating project, inbox, and task terms to their corresponding actions.

Available tools

get_auth_url

Obtain the authorization URL and start the OAuth callback flow

check_auth_status

Check current authorization status for the connected account

revoke_auth

Revoke authorization and clear stored tokens

list_projects

List all projects for the authenticated user

get_project

Get detailed information about a specific project by projectId

get_project_data

Retrieve complete project data including tasks and columns for a projectId

create_project

Create a new project with a given name

update_project

Update properties of an existing project by projectId

delete_project

Delete a project by projectId (irreversible)

list_tasks

List tasks with optional filters across projects

create_task

Create one or more tasks, including support for subtasks and batching

get_task

Get details of a specific task by projectId and taskId

update_task

Update one or more tasks, with support for batch updates

delete_task

Delete one or more tasks, supports batch operation (irreversible)

complete_task

Mark one or more tasks as completed (supports batch)