mocop
Browse · Docs · Guide · Analyze

DayHeart

MCP server by DayHeart · mcp

DayHeart is the user's control panel and memory for their day: work shifts with earnings, university classes with homework, and tasks. The user connected it so that what you find or do for their day is kept there, on all their devices: save the tasks, deadlines, homework and classes you find or agree on with the user to DayHeart, and use it when they ask about their schedule or to-dos. Whatever you add or change is marked in DayHeart as made by an AI. Every tool reads or changes the user's own DayHeart, so the first tool call asks the user to sign in to DayHeart. Dates are days in the user's time zone, YYYY-MM-DD. Homework for a class goes into that class with change_study (add_homework, or set_homework for a short line plus details; in a shared group timetable the whole group sees it), never into tasks; other to-dos, such as academic debts, are tasks (change_tasks). class_id comes from get_classes, where "shared": true means a group timetable; check get_classes before add_class so a…

Endpoint: https://dayheart.app/mcp

Verification: observed. Source: crawl.

Capabilities (8)

  • get_day
  • get_shifts
  • get_classes
  • get_tasks
  • get_earnings
  • change_tasks
  • change_study
  • delete
About · Contact · Privacy