Dida365
Let your coding agent read and update Dida365 and TickTick tasks and lists while you run build and ship checklists from the IDE.
Overview
Dida365 is a MCP server for the Build phase that integrates Dida365 and TickTick task management so your agent can manage tasks and lists over OAuth2.
What is this MCP server?
- stdio MCP server dida365-mcp-server (v0.2.2) for Dida365 and TickTick task management.
- OAuth2 integration via DIDA365_CLIENT_ID and DIDA365_CLIENT_SECRET (required secrets).
- Optional DIDA365_REGION for china vs international TickTick/Dida365 endpoints.
- Enables agents to sync IDE work with existing todo and project lists instead of duplicate trackers.
- Fits indie builders who already live in TickTick for sprint-style solo shipping.
- Server version 0.2.2
- npm identifier dida365-mcp-server
- Two required OAuth secrets plus optional DIDA365_REGION
What problem does it solve?
Your shipping checklist lives in TickTick while your agent only sees the repo, so status updates require constant context switching.
Who is it for?
Indie developers already on Dida365 or TickTick who want Claude or Cursor to create, complete, or summarize tasks during active build weeks.
Skip if: Teams standardized on GitHub Issues, Linear, or Jira with no TickTick/Dida365 account.
What do I get? / Deliverables
Your agent can read and change Dida365/TickTick tasks from the IDE so build and PM steps stay aligned with what you actually ship.
- Agent-driven task and list reads/writes in Dida365/TickTick
- Reduced manual copying between IDE prompts and todo apps
- Region-aware API access when DIDA365_REGION is set
Recommended MCP Servers
Journey fit
Task and list integration keeps shipping work organized inside the Build phase where solo builders juggle features, bugs, and docs in one backlog. PM is the canonical subphase because Dida365/TickTick is personal and team task management, not frontend code or infra monitoring.
How it compares
OAuth task-management MCP, not an in-repo PROJECT.md planning skill.
Common Questions / FAQ
Who is io.github.evalor/dida365 for?
Solo builders and small teams using Dida365 or TickTick who want their coding agent to participate in day-to-day task and list management.
When should I use io.github.evalor/dida365?
Use it during Build PM when you track features, fixes, and launch tasks in TickTick and want those updates co-located with agent-assisted development.
How do I add io.github.evalor/dida365 to my agent?
Install dida365-mcp-server from npm, configure stdio MCP in your host, and set DIDA365_CLIENT_ID, DIDA365_CLIENT_SECRET, and optionally DIDA365_REGION for OAuth.