Dida MCP

What Martinqi826/dida-mcp MCP server does

Martinqi826/dida-mcp MCP server gives an MCP client access to Dida365 task-management data and actions. It targets the China service at dida365.com and supports project lists, project details, tasks, priorities, due dates, and keyword searches. The repository describes 13 tools covering project management, task management, and advanced task queries.

Project operations include listing projects, retrieving a project with its tasks, creating projects, and deleting projects. Task operations include retrieving unfinished tasks, creating and updating tasks, marking tasks complete, and deleting tasks. Query tools return tasks due today, overdue tasks, or matching a selected priority, while search_tasks looks for keyword matches.

How it works

The server communicates with MCP clients over JSON-RPC on standard input and output. After installation, the dida-mcp run command starts the local stdio server. Clients such as Claude Desktop can launch that command from their MCP configuration and pass the Dida365 OAuth settings as environment variables.

Authorization is handled separately with dida-mcp auth. The command opens a browser for Dida365 login and consent, using the configured redirect address http://localhost:18090/callback. After authorization, the access token is saved at ~/.dida-mcp/token.json. The dida-mcp test command checks the API connection, while status and logout inspect or clear local authentication state.

Setup and configuration

Martinqi826/dida-mcp MCP server requires a Dida365 developer application. Create one through the Dida365 developer management page, then record its Client ID and Client Secret. The OAuth redirect URL must match the local callback address used by the project.

The documented local setup clones the repository and installs it with pip install -e .. Copy .env.example to .env, then provide DIDA_CLIENT_ID, DIDA_CLIENT_SECRET, and DIDA_REDIRECT_URI. Run dida-mcp auth once before starting the MCP process. To verify the setup, run dida-mcp test; to launch the server for a client, run dida-mcp run.

Claude Desktop and CodeBuddy can use a configuration entry whose command is dida-mcp and whose argument is run. OpenClaw is supported through the separately documented mcporter bridge rather than through native MCP injection. The README also states that any MCP-compatible client can use the server, but only listed client compatibility is reflected in this directory entry.

Tools and capabilities

The available tool groups are:

• Project management: get_projects, get_project_detail, create_project, and delete_project.
• Task management: get_all_tasks, create_task, update_task, complete_task, and delete_task.
• Task queries: get_tasks_due_today, get_overdue_tasks, get_tasks_by_priority, and search_tasks.

Task priorities use the values 0 for none, 1 for low, 3 for medium, and 5 for high. Dates use ISO 8601 formatting, with the README showing an example that includes a +0800 timezone offset.

Limitations and notes

The implementation is configured for Dida365’s China API. Users of the international TickTick service must modify the API address themselves, according to the repository notes. Deleting projects and tasks cannot be undone. Protect both the Client Secret and the token file, and do not commit .env to version control.

OAuth credentials are required, and the initial authorization must be completed before normal tool use. The repository is released under the MIT license. The local stdio design means the MCP client and server run on the same machine unless an external bridge is added.