Dida365 MCP integration for AI agents.
Connect AI agents to Dida365 through 19 structured actions, including get habit, create or update habit checkin, delete project, and complete task. Review au…
- ACTION CONTRACTS
- 19
- AUTHENTICATION
- OAuth 2.0
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Dida365 integration exposes
The Dida365 Agent App exposes 19 provider-backed actions for productivity work. Its current contract lets an authorized agent get a dida365 habit by its habit id, create or update a dida365 habit check-in for a date stamp, and delete a dida365 project by project id. a missing project is treated as already deleted. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Dida365 account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Dida365 capabilities.
Showing 12 of 19 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_habitREADGet a Dida365 habit by its habit ID.
INPUTS: habitId
create_or_update_habit_checkinWRITECreate or update a Dida365 habit check-in for a date stamp.
INPUTS: habitId / stamp / time / opTime / value
delete_projectHIGH IMPACTDelete a Dida365 project by project ID. A missing project is treated as already deleted.
INPUTS: projectId
complete_taskREVIEWMark a Dida365 task as completed by project ID and task ID.
INPUTS: projectId / taskId
create_projectWRITECreate a Dida365 project with optional color, sort order, view mode, and kind.
INPUTS: name / color / sortOrder / viewMode / kind
create_taskWRITECreate a Dida365 task under a project with optional schedule, reminders, recurrence, and checklist items.
INPUTS: projectId / title / content / desc / isAllDay
delete_taskHIGH IMPACTDelete a Dida365 task by project ID and task ID. A missing task is treated as already deleted.
INPUTS: projectId / taskId
filter_tasksREVIEWFilter Dida365 tasks by project, date range, priority, tags, and status.
INPUTS: projectIds / startDate / endDate / priority / tag
get_project_by_idREADGet a Dida365 project by its project ID.
INPUTS: projectId
get_project_with_dataREADGet a Dida365 project together with its undone tasks and columns by project ID.
INPUTS: projectId
get_task_by_project_and_idREADGet a Dida365 task by project ID and task ID.
INPUTS: projectId / taskId
get_user_projectREADList the projects available to the connected Dida365 account.
INPUT CONTRACTS
Know what the action needs before it runs.
get_habit
habitIdOPTIONAL- The Dida365 habit ID.
create_or_update_habit_checkin
habitIdREQUIRED- The Dida365 habit ID.
stampREQUIRED- A date stamp in YYYYMMDD format.
timeOPTIONAL- The Dida365 date-time string in yyyy-MM-dd'T'HH:mm:ssZ format.
opTimeOPTIONAL- The Dida365 date-time string in yyyy-MM-dd'T'HH:mm:ssZ format.
valueOPTIONAL- The check-in value.
delete_project
projectIdOPTIONAL- The Dida365 project ID.
complete_task
projectIdOPTIONAL- The Dida365 project ID.
taskIdOPTIONAL- The Dida365 task ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Habit
Get a Dida365 habit by its habit ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_habitControl Create Or Update Habit Checkin
Create or update a Dida365 habit check-in for a date stamp. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_or_update_habit_checkinVerify with Create Or Update Habit Checkin
Create or update a Dida365 habit check-in for a date stamp. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_or_update_habit_checkinSAFETY BOUNDARY
Operate Dida365 with explicit limits
- Authorize Dida365 with OAuth 2.0 and grant only the provider access required by the selected actions.
- 8 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_project` and `delete_task` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `tasks:write` and `tasks:read`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Dida365 task completed successfully.
CONNECTION MODEL
OAuth 2.0
Dida365 uses OAuth 2.0. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 9
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 2
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Dida365.