mocop
Browse · Docs · Guide · Analyze

DoLoop

MCP server by DoLoop · mcp

DoLoop organises recurring work as tasks and loops. - A task is a unit of work. "armed" means it is due now; checking it marks it done (ticker +1), skipping it (abort_task) means "not this time": abortions +1, and its loop moves on at the next arming pass. Both only act on an armed task. The app calls this action Skip; the API keeps the name abort. - task_type "schedule": due on the days given by ONE schedule system: dow (bitmask Monday=1 ... Saturday=32, Sunday=64; 127 = every day), a cron expression, or every_days (strictly every N days from start_date, e.g. every_days=3 for every third day across month ends). Optionally bounded by start_date/end_date. "loop": a member of a loop's queue. "subtask": armed every "every" runs of its parent_task_id. - A loop is an ordered queue of tasks; it arms one task at a time (current_task_id) and moves to the next when the user runs the arming pass (arm_all). Arming is the user's decision: run arm_all only when the user asks for it, never on your…

Endpoint: https://api.getdoloop.com/mcp

Verification: observed. Source: crawl.

Capabilities (16)

  • abort_task
  • arm_all
  • check_task
  • create_loop
  • create_task
  • delete_loop
  • delete_task
  • dequeue_task
  • enqueue_task
  • get_loop
  • get_task
  • list_loops
  • list_tasks
  • todays_tasks
  • update_loop
  • update_task
About · Contact · Privacy