Productivity

aimyear.com

Manages a yearly goal by saving objectives, checking drafts against criteria, recording metric progress, and setting recurring levers.

1 endpoint43 known toolsFirst detected October 18, 2026Last detected October 18, 2026

ENDPOINT 1

https://mcp.aimyear.com/mcp

No auth detected

MCP server metadata

Name: aimyear
Version: 0.4.2

Capabilities

tools.listChangedprompts.listChanged

Server instructions

AimYear keeps one person's big aim for the year, the path of stages toward it, today's plan, a timer and an honest record of where the time went. Every tool acts as the signed-in person. Names: get_ reads one thing, list_ reads several, find_ looks for problems, set_ replaces a whole list, add_ / edit_ / delete_ change one entry. A session is one piece of work; the timer runs while sessions run. Typical flow: get_goal (or check_goal_draft → set_goal), get_path, get_planning_context → set_plan with one main step (routines from set_routines are added to each day's plan by the server), start_session before work (honor its verdict: ok, plan_first or stop), stop_session with a real summary, summarize_day / summarize_week / find_leaks for reviews. To fix a record, use edit_session or delete_session. Hard first: the first step of each stage and each day's main step should be on a hard lever (the work the user puts off: outreach, applications, selling, publishing). Preparation (CV, profile, research, polishing) comes only when it blocks the hard step, and only as much as it blocks; do the hard step with what exists now and improve after the replies. set_plan, add_steps and set_levers warn when this is broken: fix it before moving on. Every result has a "speak" field: say it to the user in your own words. Start or stop the timer only when the user asks; adding past time with add_session is always fine.

Known tools 43

get_goal

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

Inferred read-only

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).

Inferred read-only

set_goal

Save the yearly goal, or replace it with the next one.

Inferred read-only

record_progress

Record the current value of the goal metric, e.

Inferred read-only

set_levers

Replace the list of levers: the recurring kinds of goal work.

Inferred read-only

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.

Inferred read-only

get_path

Milestones with pace (ahead/on_pace/behind) and their steps.

Inferred read-only

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.

Inferred read-only

edit_milestone

Change one milestone: title, metric, target, due date or status.

Inferred read-only

add_steps

Add concrete steps to a milestone.

Inferred read-only

edit_step

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

Inferred read-only

delete_step

Delete one step from the path.

Potential side effects

next_steps

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

Inferred read-only

get_commitments

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

Inferred read-only

set_commitments

Replace the list of recurring weekly commitments.

Inferred read-only

get_capacity

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

Inferred read-only

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.

Inferred read-only

get_plan

The plan for a day (default today).

Inferred read-only

set_plan

Replace the plan for a day.

Inferred read-only

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.

Inferred read-only

get_routines

Routines: small steps that repeat on fixed weekdays, e.

Inferred read-only

set_routines

Replace the list of routines: small steps that repeat on fixed weekdays.

Inferred read-only

delete_plan_item

Remove one item from a day's plan.

Potential side effects

set_day_mode

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

Inferred read-only

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.

Inferred read-only

start_session

Start a session of work and, if none is running, the timer.

Inferred read-only

add_note

Add a one-line note to a running session (this connection's, or session_id).

Inferred read-only

split_attention

Set attention weights of the running sessions at once, e.

Inferred read-only

stop_session

Stop a running session (this connection's, or session_id) with a summary and outcome.

Inferred read-only

stop_timer

Stop the timer ("pause", "stop", "stand up") and every running session with it.

Inferred read-only

add_session

Add past time that was not timed: minutes (ending now, or at end), or start+end as HH:MM on date.

Inferred read-only

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.

Inferred read-only

delete_session

Delete a session, running or finished, so it no longer counts.

Potential side effects

list_sessions

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

Inferred read-only

find_gaps

Untimed stretches of 20+ minutes between the first and last session of a day.

Inferred read-only

summarize_day

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

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

get_settings

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

Inferred read-only

set_settings

Change any of: timezone (IANA name, e.

Inferred read-only

add_device

Inferred read-only

list_devices

Which devices can receive reminders, and when each was last seen.

Inferred read-only

delete_device

Remove a device so it stops receiving reminders.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.aimyear]
url = "https://mcp.aimyear.com/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: aimyear
Remote MCP URL: https://mcp.aimyear.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "aimyear",
  "transport": "streamable-http",
  "url": "https://mcp.aimyear.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.