Agents Index

AimYear

Online

Accountability partner in your agent: one yearly aim, one main step a day, a timer your agent runs.

Visit publisherConnectJSON

What it can do: 59 tools

  • get_goal read-onlyThe one yearly goal: kind (count or done), metric, starting value, current value, target, deadline, progress, levers (hard/comfortable) and other projects. Call first in most flows.
  • check_goal_draft read-onlyCheck a goal that is not saved yet against the rubric (a countable metric with value today and target, or a done-or-not result you can check yes or no; deadline within 12 months; pace per week). Changes nothing. Returns
  • set_goalSave 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_progressRecord the current value of the goal metric ("I now have 4 customers"), or of a countable milestone when milestoneId is given ("I have talked to 7 people"). For a done-or-not goal, 1 marks it done. One value per date: ca
  • set_leversReplace 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. wip_hashtag only for a leve
  • set_projectsReplace 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 ed
  • get_path read-onlyMilestones with kind, progress (recorded value or steps done), pace (ahead/on_pace/behind) and their steps. With tracks: tracks[], each with its current_milestone_id (every track has its own current milestone); current_m
  • set_milestonesReplace the list of ordered milestones under the goal (2–6, or up to 6 per track), each countable (metric and target) or measured by its steps, with a due date before the goal deadline; due dates in order within a track.
  • set_tracksReplace the tracks of the path: 0 to 3 different ways to reach the same aim (e.g. two products that could each earn the target), each with its own milestones and current milestone. reach says how this track alone would r
  • edit_milestoneChange one milestone: title, kind (count or steps), metric, target, due date, status or track. status=retired drops it without finishing; done or retired moves its track to the next milestone. Its steps are kept.
  • add_stepsAdd 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 whe
  • edit_stepChange one step: title, status (todo/doing/done), order, lever, estimate.
  • delete_stepDelete one step from the path.
  • next_steps read-onlyOpen steps of the current milestone (of every track, taken in turns, each step with its track), hard-lever steps first: the candidates for today's main step.
  • get_commitments read-onlyRecurring weekly time: commitments (school runs, training, classes), overhead (sleep, meals) and focus windows.
  • set_commitmentsReplace 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. A recurring life event read from the user's cal
  • get_capacity read-onlyWeekly 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 read-onlyEverything 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 read-onlyThe plan for a day (default today).
  • set_planReplace 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 wo
  • edit_plan_itemChange 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. For a weekly routine, count says how many units this
  • get_routines read-onlyRoutines: small steps that repeat on fixed weekdays, e.g. "talk with one person on Reddit", or that count up to a number a week, e.g. "talk to 5 people a week", each with an optional bad-day minimum. The server adds them
  • set_routinesReplace 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
  • delete_plan_itemRemove one item from a day's plan. A routine item is skipped for that day only.
  • set_day_modeTracking for a day: full (everything recorded, the default) or off (timer and reminders only, nothing stored, no plan required).
  • get_now read-onlyWhat 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_sessionStart 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. Seve
  • add_noteAdd a one-line note to a running session (this connection's, or session_id). May classify a session that was unclassified.
  • split_attentionSet attention weights of the running sessions at once, e.g. {"abc": 0.7, "def": 0.3}. Applies to the whole session, or with from_now only from now on (the user switched what they attend to; the time before keeps its spli
  • stop_sessionStop a running session with a summary and outcome. Pass session_id from get_now; without it, only this connection's single running session is stopped, never another one. The timer keeps running for other sessions. outcom
  • stop_timerStop 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_sessi
  • add_sessionAdd 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, or a calendar event that happened (pass its cal
  • edit_sessionFix 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 classif
  • delete_sessionDelete a session, running or finished, so it no longer counts. Pass session_id from get_now or list_sessions; without it, only this connection's single running session is deleted, never another one.
  • add_moveRecord a move: one action toward the aim with no duration, e.g. a small fix the user described to you from the phone, or a message sent. task says what changed, in plain words. Classified like a session (pass leverId, st
  • list_moves read-onlyMoves in a date range (default the last 7 days), with ids, whether each was toward the aim and on the hard part.
  • delete_moveDelete a move recorded by mistake. Pass move_id from list_moves. A plan item it ticked stays ticked.
  • list_sessions read-onlySessions in a date range (default the last 7 days), with ids, optionally filtered by area or project.
  • find_gaps read-onlyUntimed stretches of 20+ minutes between the first and last session of a day. Ask the user what happened there.
  • summarize_day read-onlyFull summary of a day: wall and attention minutes per area, classification and lever, sessions, gaps, overlaps, overrides.

…and 19 more.

Connect it

Claude Code
claude mcp add --transport http aimyear https://mcp.aimyear.com/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://mcp.aimyear.com/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "aimyear": {
      "url": "https://mcp.aimyear.com/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "aimyear": {
      "type": "http",
      "url": "https://mcp.aimyear.com/mcp"
    }
  }
}

Questions

What does AimYear do?

Accountability partner in your agent: one yearly aim, one main step a day, a timer your agent runs. It exposes 59 tools to AI assistants.

What tools does AimYear provide?

59 tools, including get_goal, check_goal_draft, set_goal, record_progress, set_levers, set_projects, get_path, set_milestones, set_tracks, edit_milestone, add_steps, edit_step….

How do I connect AimYear to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://mcp.aimyear.com/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does AimYear require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is AimYear online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes AimYear?

@Yahhi on GitHub. The official MCP Registry verified that the publisher controls this GitHub account before accepting the listing.

Similar in Agents & Orchestration