AimYear

Reliability

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "aimyear": {
      "type": "http",
      "url": "https://mcp.aimyear.com/mcp"
    }
  }
}

43 tools

• get_goal

  The one yearly goal: metric, starting value, current value, target, deadline, levers (hard/comfortable) and other projects. Call first in most flows.

• check_goal_draft

  Check a goal that is not saved yet against the rubric (countable metric, value today, target, deadline within 12 months, pace per week). Changes nothing. Returns problems[] and next_question: loop until problems is empty, then call set_goal.

• set_goal

  Save the yearly goal, or replace it with the next one. Rejects with problems[] if the rubric fails. Keeps levers and projects. area is which of the five life areas the goal belongs to.

• record_progress

  Record the current value of the goal metric, e.g. "I now have 4 customers". One value per date: calling again for the same date corrects it. Says when the target is reached.

• set_levers

  Replace the list of levers: the recurring kinds of goal work. At least one must be kind=hard (the work the user avoids). keywords/repos are hints for classifying sessions from their task text. Pass existing ids to keep them.

• set_projects

  Replace the list of other projects (paid work, other products, life routines), so their sessions count as other work or life, not goal work. Pass the whole list: leave one out to remove it, change its name or hints to edit it. Pass existing ids to keep them.

• get_path

  Milestones with pace (ahead/on_pace/behind) and their steps. current_milestone_id is the one to work on.

• set_milestones

  Replace the list of 2–6 ordered milestones under the goal, each with a metric, target and due date before the goal deadline. Pass each existing id, or that milestone's steps are deleted. To change one milestone, use edit_milestone.

• edit_milestone

  Change one milestone: title, metric, target, due date or status. status=retired drops it without finishing; done or retired moves the path to the next milestone. Its steps are kept.

• add_steps

  Add concrete steps to a milestone. A step is an action that fits a few work blocks ("email 10 people from the waitlist"), not "do marketing". Abstract steps are rejected. Put a hard-lever step first; preparation only where it blocks it (warns otherwise).

• edit_step

  Change one step: title, status (todo/doing/done), order, lever, estimate.

• delete_step

  Delete one step from the path.

• next_steps

  Open steps of the current milestone, hard-lever steps first: the candidates for today's main step.

• get_commitments

  Recurring weekly time: commitments (school runs, training, classes), overhead (sleep, meals) and focus windows.

• set_commitments

  Replace the list of recurring weekly commitments. days are ISO weekdays 1=Mon..7=Sun; use timesPerWeek instead when there are no fixed days. Pass existing ids to keep them.

• get_capacity

  Weekly time budget out of 168 hours: overhead, hours committed per area, focus windows, and what is still unaccounted for. Nothing is assumed.

• get_planning_context

  Everything needed to plan a day: goal and pace, next_steps, yesterday's summary and undone items, week balance, days since a hard lever. Defaults to tomorrow. The agent plans; then call set_plan.

• get_plan

  The plan for a day (default today).

• set_plan

  Replace the plan for a day. Exactly one item must have isMainStep=true (the step toward the goal), ideally linked by stepId from next_steps and on a hard lever. Warns when no item is on a hard lever. Other items: paid work, family, workout, etc. with their area. Items that stay…

• edit_plan_item

  Change one plan item: mark it done or not done, rename it, change its estimate, area or links, or make it the main step. done=true also completes its linked path step.

• get_routines

  Routines: small steps that repeat on fixed weekdays, e.g. "talk with one person on Reddit". The server adds them to each matching day's plan, so every device and agent sees the same checks.

• set_routines

  Replace the list of routines: small steps that repeat on fixed weekdays. From today on, each one appears as a plan item on its days; tick it with edit_plan_item, skip it for one day with delete_plan_item. set_plan keeps them. days are ISO weekdays 1=Mon..7=Sun, default every…

• delete_plan_item

  Remove one item from a day's plan. A routine item is skipped for that day only.

• set_day_mode

  Tracking for a day: full (everything recorded, the default) or off (timer and reminders only, nothing stored, no plan required).

• get_now

  What is happening now: running sessions with attention shares, the timer, today's main step, today's minutes, the streak and a one-line nudge.

• start_session

  Start a session of work and, if none is running, the timer. Returns a verdict: ok | stop | plan_first. On "stop" NO session is created: relay the message, ask the user; if they insist, call again with override=true. Several sessions may run at once (two terminals) and share…

• add_note

  Add a one-line note to a running session (this connection's, or session_id). May classify a session that was unclassified.

• split_attention

  Set attention weights of the running sessions at once, e.g. {"abc": 0.7, "def": 0.3}. Applies to the whole session. For a finished session use edit_session.

• stop_session

  Stop a running session (this connection's, or session_id) with a summary and outcome. The timer keeps running for other sessions. outcome=done completes the linked plan item or path step. Refuses a session that already ended: use edit_session for that.

• stop_timer

  Stop the timer ("pause", "stop", "stand up") and every running session with it. There is no paused state: resuming starts a new session. Pass summary and outcome to save them on the sessions it closes, or call stop_session first. Returns the break length.

• add_session

  Add past time that was not timed: minutes (ending now, or at end), or start+end as HH:MM on date. For calls, children, workout, paid work, or work done away from the agent.

• edit_session

  Fix a session, running or finished: start and end (HH:MM on date; an end before the start means it ran past midnight), task, area, project, lever, step, plan item, summary, outcome, attention share, weight. It is classified again after a change. Use it when a timer was forgotten…

• delete_session

  Delete a session, running or finished, so it no longer counts. Without session_id it deletes this connection's running session.

• list_sessions

  Sessions in a date range (default the last 7 days), with ids, optionally filtered by area or project.

• find_gaps

  Untimed stretches of 20+ minutes between the first and last session of a day. Ask the user what happened there.

• summarize_day

  Full summary of a day: wall and attention minutes per area, classification and lever, sessions, gaps, overlaps, overrides.

• summarize_week

  A week, Monday to Sunday (to today for the current week): main-step days, goal share, hard share, area balance, overrides, streak, milestone pace.

• find_leaks

  Where time leaks: comfortable goal work while the main step waited, overrides, unplanned work, gaps, switching, missed main steps, days without a plan. Default the last 7 days.

• get_settings

  Timezone, where reminders go (desktop or mobile), and timer settings.

• set_settings

  Change any of: timezone (IANA name, e.g. Europe/Madrid; it sets where each day starts and ends), workplace for reminders, stand-up interval workMin, breakMin, longBreakEvery, longBreakMin, standup on/off.

Security scan

Recent checks