Dida365 MCP server

Read from the package source without running it. The installed server may list more.

• check_auth_status

  Use when the user asks about being authorized (e.g. 'am I authorized', 'auth status', 'check auth'), or when deciding whether protected Dida365 operations can proceed and current state is unclear. Avoid repeated calls if status already known in the current conversation turn. Restricted to Dida365 MCP authorization context only.

• complete_task
• create_projectwrite action

  Create a new project (folder/list) for organizing tasks. WHEN TO USE: - User wants to create a new task list, folder, or project - Organizing tasks into categories or areas REQUIRED: name (project title) OPTIONAL: - color: Hex color code (e.g., '#F18181') - viewMode: 'list' (default), 'kanban', or 'timeline' - kind: 'TASK' (default) for tasks, 'NOTE' for notes - sortOrder: Position in project list

• create_taskwrite action
• delete_projectwrite action

  Permanently delete a project and all its contents. ⚠️ DESTRUCTIVE: This action cannot be undone. All tasks within the project will also be deleted. WHEN TO USE: - User explicitly requests to delete a project - Cleaning up unused/empty projects WHEN NOT TO USE: - Just archiving or hiding a project (not supported) - Moving tasks to another project first → use 'update_task' REQUIRED: projectId

• delete_taskwrite action

  Permanently delete one or more tasks. Supports batch deletion. ⚠️ DESTRUCTIVE: This action cannot be undone! WHEN TO USE: - User explicitly requests to remove/delete a task - Cleaning up unwanted tasks WHEN NOT TO USE: - Complete a task → use 'complete_task' - Archive a task (not supported by API) REQUIRED (per task): - projectId: Project containing the task - taskId: Task to delete INPUT FORMAT:

• get_auth_url

  Use ONLY when a Dida365 MCP tool (task/project operations) fails with an authorization/OAuth error (e.g. missing, expired, or invalid token), or the user explicitly asks to start/redo Dida365 authorization. Not for generic OAuth of other services. Provides a short‑lived URL (≈5 min) to open in a browser; starts a local callback server to capture the authorization code.

• get_project

  Retrieve metadata for a single project by ID. WHEN TO USE: - Check project settings (name, color, viewMode, permissions) - Verify a project exists before operations - Get project metadata without loading tasks WHEN NOT TO USE: - Need tasks within the project → use 'get_project_data' or 'list_tasks' - Need to filter tasks by date/priority → use 'list_tasks' RETURNS: Project metadata only (id, name,

• get_project_data

  Retrieve complete project data including project details, tasks, and kanban columns. WHEN TO USE: - Get all uncompleted tasks within a specific project - Need project metadata AND tasks together - View kanban column structure for kanban-view projects WHEN NOT TO USE: - Only need project metadata → use 'get_project' (faster) - Filter tasks by date/priority/across projects → use 'list_tasks' - Need

• get_task

  Retrieve detailed information about a specific task. WHEN TO USE: - View complete task details (title, description, dates, priority) - Check task status before updating or completing - Verify a task exists WHEN NOT TO USE: - List multiple tasks → use 'list_tasks' - Get all tasks in a project → use 'get_project_data' or 'list_tasks' REQUIRED: projectId, taskId RESPONSE FIELDS: - content: Descriptio

• list_projects

  Retrieve all projects (folders/lists) for the current user. WHEN TO USE: - Get an overview of all projects - Find a project ID before operating on tasks - Check project names, colors, and view modes RETURNS: Project list with id, name, color, viewMode, permissions, kind (TASK/NOTE). 💡 TIP: After getting the project list, use 'list_tasks' with projectId to get tasks, or 'get_project_data' for comp

• list_tasks
• revoke_auth

  Use ONLY when the user explicitly requests to log out, revoke, reset, clear, or remove Dida365 authorization/tokens. Do NOT call for token refresh, generic OAuth logout of other services, or routine task operations. Clears stored tokens; user must re-authorize afterward.

• update_projectwrite action

  Update an existing project's settings. WHEN TO USE: - Rename a project - Change project color, view mode, or type - Reorder projects in the list PARTIAL UPDATE: Only provide fields you want to change. Unspecified fields remain unchanged. REQUIRED: projectId OPTIONAL (at least one required): - name: New project name - color: New hex color (e.g., '#F18181') - viewMode: 'list', 'kanban', or 'timeline

• update_taskwrite action

• Code scan63 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 310 days ago4/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

66/100

higher than 18% of 1,299 Productivity servers

Tools

15

the typical Productivity server has 7

Tools that change things

40%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

4

more than 68% of 854 Productivity servers

Dida365: common questions

Is Dida365 MCP server safe?

With care: it is graded C, so read the findings first (66/100). Read the Dida365 safety report

How do I install Dida365?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Dida365 need an API key?

Yes. The registry entry asks for DIDA365_CLIENT_ID, DIDA365_CLIENT_SECRET.

Is Dida365 maintained?

The last commit was 343 days ago (2025-11-26). The latest release is v0.2.2.

How does Dida365 compare with other Productivity MCP servers?

safety score 66/100 (higher than 18% of 1,299 Productivity servers); tools 15 (the typical Productivity server has 7); tools that change things 40% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.