Dida365 MCP Server

MCP Server for Dida365 (TickTick) Task Management Integration

Local serverstdioTypeScript

What is the Dida365 MCP server?

If you already use Dida365, the dida365 mcp server is the piece that lets your assistant work with it directly. MCP Server for Dida365 (TickTick) Task Management Integration.

What the server does

I am GitHub Copilot, an AI assistant passionate about programming. To avoid idleness and prevent unemployment, I've decided to build this TickTick MCP server myself. Through this tool, I can:

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Category — Tool Name
  • OAuth2 — get_auth_url
  • Project — list_projects
  • Task — list_tasks
  • Prerequisites — The Prerequisites tool exposed by this server
  • Setup — 1. Clone and install powershell git clone https://github.com/evalor/Dida365MCP.git cd Dida365MCP npm install

Credentials and setup notes

Configuration is passed through the environment: DIDA365_CLIENT_ID, DIDA365_CLIENT_SECRET, DIDA365_REGION. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Node.js 16+ - TypeScript 5.0+

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Dida365's toolset — Category, OAuth2, Project and 3 more — is a fair guide to whether it matches your workflow. It is maintained by evalor; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Dida365's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
CategoryTool Name
OAuth2get_auth_url
Projectlist_projects
Tasklist_tasks
PrerequisitesThe Prerequisites tool exposed by this server.
Setup1. **Clone and install** powershell git clone https://github.com/evalor/Dida365MCP.git cd Dida365MCP npm install

How to install the Dida365 MCP server

{
  "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"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js 16+ - TypeScript 5.0+
VariableDescriptionRequired
DIDA365_CLIENT_IDConfiguration value read at startup.Optional
DIDA365_CLIENT_SECRETCredential the server authenticates with.Yes
DIDA365_REGIONConfiguration value read at startup.Optional

Example prompts to try

  • Use Dida365 to Category.
  • Use Dida365 to OAuth2.
  • Use Dida365 to Project.

Frequently asked questions

It connects Dida365 to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (Category, OAuth2, Project, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Dida365 directly.