AimYear MCP Server

by yahhi Your server? Claim it

answering

AimYear is answering right now. Last checked 7 min ago. It exposes 55 tools. Last commit 20 Oct 2026.

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

Uptime history 20 days of history

20 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

244 ms

Response time

average over 24h

Stars

last commit 20 Oct 2026

What changed 61

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 19 October 2026. No other catalogue keeps this.

6 Nov 3 tools appeared add_move, delete_move, list_moves

6 Nov 2 tool descriptions were rewritten get_settings, set_settings

6 Nov a tool changed the parameters it asks for set_settings

6 Nov a tool changed version

30 Oct a tool changed version

26 Oct 4 tool descriptions were rewritten edit_milestone, get_path, next_steps and 1 more

26 Oct a tool changed version4 times that day

26 Oct 2 tools changed the parameters they ask for edit_milestone, set_milestones

26 Oct a tool appeared set_tracks

22 Oct 8 tools appeared add_post, add_social_account, delete_agent and 5 more

and 37 more, back to 19 October 2026

Nothing serious here today

Today is the operative word: we check AimYear every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add aimyear-mcp --transport http https://mcp.aimyear.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.aimyear.com/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 55

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

edit

edit_milestone

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

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. For a weekly routine, count says how many units this tick did (talked to 2 people today). For a routine, level minimum says only its bad-day minimum was done: it counts for the day, reported apart from full.

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 or a session was labelled wrong.

edit_step

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

goal

check_goal_draft

Check 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 problems[] and next_question: loop until problems is empty, then call set_goal. Prefer count; use done only when no honest number exists.

get_goal

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

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.

plan

delete_plan_item

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

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 keep their done state.

social

add_social_account

Connect WIP (wip.co) or Bluesky so AimYear can post the day's progress there when the user says Post (Pro). WIP: api_key from wip.co settings. Bluesky: handle and an app password (Settings → Privacy and security → App passwords), never the account password. The login is checked, stored encrypted and never shown again. The app's connect screen usually calls this; if the user pastes a key into the chat, use it once and do not repeat it.

delete_social_account

Disconnect a network and delete its saved login. Posts already made stay there.

list_social_accounts

Connected networks (handle, since when), which of them get progress posts, and whether the user has Pro. Never returns any key or password.

commitments

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.

device

add_device

Register a device token so server reminders (stand up, break over) can reach it. The phone app registers itself; use this for testing or a manual token.

delete_device

Remove a device so it stops receiving reminders.

move

add_move

Record 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, stepId, itemId or projectId when known). Past days are fine (date). completes_item: true with item_id ticks that plan item, so a move can finish the main step. Counts toward the weekly target. Use it for work that had no timer; use add_session for timed work.

delete_move

Delete a move recorded by mistake. Pass move_id from list_moves. A plan item it ticked stays ticked.

post

add_post

Post the day's progress, only after the user explicitly said to post. text is the draft as the user edited it (default: the draft from get_post_draft). Goes to the networks chosen in settings, or the ones given. A network where the user already posted that day themselves is skipped. Each day goes to each network once: a retry never posts twice. Today or yesterday only. Pro.

get_post_draft

The day's progress post drafted from the record (aim and progress, main step done or not, minutes on the aim and on hard work, routines, comebacks), at most 300 characters, ending with aimyear.com; and per network whether it is ready, already posted, or skipped because the user already posted there that day. Posts nothing. Pro.

routines

get_routines

Routines: 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 to each matching day's plan, so every device and agent sees the same checks. With no routines yet, returns ready-made starters for the aim's area to offer as they are.

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 day. perWeek makes it a weekly count: each tick adds its count (default 1), and once the week reaches perWeek it leaves the plan until Monday. Link it to the goal with leverId. minimum is the small version for a bad day ("read one thread" for "talk to one person"). Pass existing ids to keep them.

session

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. Apps replaying a queued entry pass op_id, so a retry does not count the time twice.

delete_session

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

settings

get_settings

Timezone, where reminders go (desktop or mobile), timer settings, which networks get progress posts (post_to), tracking (time, moves or quiet) and the weekly target.

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, post_to (networks for progress posts), tracking (time, moves or quiet) and weekly_target (days a week toward the aim).

stop

stop_session

Stop 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. outcome=done completes the linked plan item or path step. Without end_at or op_id it refuses a session that already ended: use edit_session for that. With end_at (apps delivering a stop queued offline) a second stop on the same session is merged, whatever order they arrive in: the earliest end wins, done wins over any other outcome, the first summary stays and a different later one goes to the notes; the answer says applied: ended | shortened | recorded.

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.

summarize

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.

agent

delete_agent

Disconnect one agent: its sign-in for this account is deleted and it can no longer read or change anything until it connects again. Only on the user's explicit request. client_id from list_agents.

agents

list_agents

Agents connected to this AimYear account (Claude, ChatGPT, Claude Code, the AimYear app…): name, client_id, when it connected and when it was last active. current marks the one calling.

capacity

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.

day

set_day_mode

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

devices

list_devices

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

gaps

find_gaps

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

insights

get_insights

Week (the last 7 days) or month (the last 30 days) ending on to (default today): minutes per day on the aim, other work and life; hard vs comfortable share of aim time; an hour × weekday heatmap of aim minutes (6:00–23:00, Mon–Sun) with its hard part and the peak; main-step days; and comebacks (active days after 2+ days away, over 90 days). Wall minutes of finished sessions, as the app shows them.

leaks

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.

levers

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.

milestones

set_milestones

Replace 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. Pass each existing id, or that milestone's steps are deleted. To change one milestone, use edit_milestone.

moves

list_moves

Moves in a date range (default the last 7 days), with ids, whether each was toward the aim and on the hard part.

next_steps

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

note

add_note

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

now

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.

path

get_path

Milestones 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_milestone_id is then the first open one in list order. Without tracks, current_milestone_id is the one to work on.

planning

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.

projects

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.

record

record_progress

Record 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: calling again for the same date corrects it. Says when the target is reached; a countable milestone that reaches its target is done.

sessions

list_sessions

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

split

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.

start

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 attention by weight. Apps replaying a queued start pass op_id, their own session_id and start_at; an agent leaves all three out.

step

delete_step

Delete one step from the path.

steps

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

tracks

set_tracks

Replace 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 reach the aim. milestoneIds puts those milestones into the track, in that order. An empty list makes the path one list again. Use tracks only when the user chooses to work on more than one way; never present one track as the wrong one.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.aimyear.com/mcp	streamable-http	answering	601 ms	7 min ago

Alternatives to AimYear

same job, measured the same way

Basicdeploy MCP

by akacianl

The runtime your agent deploys to — DB, storage, and a public URL in one MCP call.

67 installs/wk local only

Noemic

by noemic

Someone to talk to, for your user: coaches, mentors, accountability partners. First session free.

6 tools answering

Paramability

by paramability

Links your AI assistant app to the Paramability tab open in Chrome. Runs on your computer only.

82 installs/wk local only

Paas Build MCP

by unipaas

Your agent opens a real merchant account (go_live) and takes payments the same day. 3.9% flat.

65 installs/wk local only

Pinafly Guides

by pinafly

Your agent walks you through any tool, one step at a time, on the real screens.

answering

Health Partner

by shrynshjn

Manage your Health Partner account, log food, water, workouts, body using agent

answering

Kin

by kinlab

Connect accounts once. Set what agents may do per account. Enforced when the action runs.

answering

Kitchen Timer

by tnyforge

Plan a meal and run kitchen timers that ring on your phone. No sign-in.

9 tools answering

AimYear — questions

Answers built from our own checks of this server.

What can AimYear do?

It exposes 55 tools, read directly from the server on our last check. Among them: add_device, add_move, add_note, add_post, add_session, add_social_account and 49 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is AimYear mostly used for?

Its tools cluster around edit, goal and plan. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is AimYear working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 244 ms. The bar chart above shows every period we have measured.

How do I connect AimYear?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does AimYear need an API key?

No. AimYear completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 55 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is AimYear?

It answers our handshake in 244 ms on average, which is faster than 59% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is AimYear open source?

We cannot say either way: written in TypeScript, 0 stars on GitHub and 16 open issues, but we could not determine the licence, and without one the code is not open source by default.