MCP Server for Dida365 (TickTick) Task Management Integration
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
npx -y dida365-mcp-server{
"DIDA365_CLIENT_ID": "YOUR_SECRET_VALUE",
"DIDA365_CLIENT_SECRET": "YOUR_SECRET_VALUE",
"DIDA365_REGION": "YOUR_VALUE_HERE"
}Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-evalor-dida365": {
"command": "npx",
"args": [
"-y",
"dida365-mcp-server"
],
"env": {
"DIDA365_CLIENT_ID": "YOUR_SECRET_VALUE",
"DIDA365_CLIENT_SECRET": "YOUR_SECRET_VALUE",
"DIDA365_REGION": "YOUR_VALUE_HERE"
}
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
dida365 is an MCP server for MCP Server for Dida365 (TickTick) Task Management Integration. It supports STDIO transport.
Use the generated config in Install. This server runs with npx -y dida365-mcp-server; add any required environment variables before starting your client.
Choose the Claude Desktop tab in Install and copy the config for npx -y dida365-mcp-server. Add required environment variables before starting Claude Desktop.
Choose the Claude Code tab in Install and copy the config for npx -y dida365-mcp-server. Add required environment variables before starting Claude Code.
Choose the Codex tab in Install and copy the config for npx -y dida365-mcp-server. Add required environment variables before starting Codex.
Choose the Cursor or VS Code tab in Install and copy the config for npx -y dida365-mcp-server. Add required environment variables before starting Cursor or VS Code.
dida365 uses STDIO transport. Use the package or command config in Install.
dida365 inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
dida365 is marked with Auth required by registry metadata auth. You may need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
dida365-mcp-serverstdio | npm | 0.2.2 | Env: DIDA365_CLIENT_ID required secret Env: DIDA365_CLIENT_SECRET required secret Env: DIDA365_REGION |