dida365 s

This MCP server provides a TypeScript-based interface to TickTick / Dida365 through a standardized MCP surface. It exposes operations for managing tasks and projects, including create, read, update, delete and completion of tasks, as well as fetching and updating projects. The server authenticates with a Bearer token supplied via the DIDA365_TOKEN environment variable and communicates with the official Dida365 API to perform actions on your projects and tasks. You can invoke the available tools to programmatically manipulate your Dida365 data from an AI assistant or other MCP clients.

Available tools include task management functions such as create_task, get_task_by_projectId_and_taskId, get_tasks_by_projectId, update_task, delete_task, complete_task, and project management functions like get_projects, get_project_by_projectId, create_project, update_project_by_projectID. Each tool takes parameters described in the README (e.g., projectId, taskId, title, dueDate, priority, etc.). Use these tools to automate workflows like creating time-bound tasks, organizing tasks into projects with colors and view modes, and bulk reading of project/task collections. The API layer validates inputs and returns structured responses with error details when something goes wrong, making it suitable for integration into chat assistants and automation pipelines.

To use the server, start it with the configured command and provide your Dida365 API token via the DIDA365_TOKEN environment variable. Then call the MCP methods from your client or AI agent, passing the required parameters as described in the tool documentation. Ensure your token has the necessary permissions for the requested operations.

Prerequisites:

• Node.js (v12+ recommended) and npm
• Access token for Dida365 API and a Dida365 account

1. Install the MCP server package

npm i dida365-mcp-servers

2. Configure environment variables

• Copy or create an env file and set your token:

cp .env.example .env

Edit .env and set:

DIDA365_TOKEN=Bearer your_token_here

3. Build and run (development)

npm run dev

4. Build for production (optional)

npm run build
npm start

5. Configuration (example in JSON config) Create a config fragment (e.g. config.json) including the MCP server entry:

{
  "dida365": {
    "command": "node",
    "args": [
      "dist/index.js"
    ],
    "env": {
      "DIDA365_TOKEN": "Bearer your_token_here"
    }
  }
}

6. Run with your custom config depending on your deployment setup (Docker, PM2, etc.).

Environment variable tips:

• DIDA365_TOKEN should be a Bearer token obtained from the Dida365 Open API portal.
• Keep tokens secret and rotate periodically.

Common issues:

• Invalid token or insufficient permissions: re-check token scopes on the Dida365 developer portal.
• Network errors: ensure outbound access to https://api.dida365.com is allowed.

Configuration tips:

• If running behind a container or orchestrator, ensure the dist/index.js path matches your build output and that environment variables are properly propagated.
• When building, verify TypeScript compilation outputs to dist/ and that the entry file path is correct.

NPM package name:

• dida365-mcp-servers (npm i dida365-mcp-servers)