AimYear
Track one yearly goal with daily steps, time tracking, and accountability.
Accountability partner that helps you set one yearly goal with a metric and deadline, break it into milestones and daily steps, track time spent on goal work versus other activities, and see your progress and pace. Integrates with your agent's calendar and planning.
Try asking Muse: "Help me set a goal to reach 10 paying customers by December and plan what to work on today to get there."
See the most upvoted connectors
Source: Found in the official MCP Registry (io.github.Yahhi/aimyear-mcp) · First listed October 29, 2026
Last 24 hours
Each bar is one check, every 15 minutes. Green means it answered. Last checked 2 h ago.
Is it safe to connect?
What Muse can see: It does not ask you to sign in, so it cannot see your accounts. It only sees what Muse sends it from your request.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
musedirectory.ai is not part of Meta. More about how Muse handles your information
How to add it to Muse
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
https://mcp.aimyear.com/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Also use it in ChatGPT or Claude
AimYear is a remote MCP server, so any assistant that can add a custom connector by link can use it. Same link, same tools.
Add it to ChatGPT
- 1
Open ChatGPT settings
In ChatGPT, open Settings, then Connectors (called Apps & Connectors on some accounts).
- 2
Turn on developer mode
Under Advanced settings, switch on Developer mode. That is what lets you add a connector by link.
- 3
Create the connector
Choose Create, give it a name, paste the link as the MCP server URL, and save. If it needs a sign-in, ChatGPT asks for it here.
- 4
Use it in a chat
Start a chat, open the tools menu, pick the connector, and ask. ChatGPT asks before it runs a tool the first time.
Custom connectors need a paid ChatGPT plan, and on Team, Enterprise and Edu accounts only an admin can add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in ChatGPT
Add it to Claude
- 1
Open Claude settings
In Claude, open Settings, then Connectors.
- 2
Add a custom connector
Choose Add custom connector, give it a name, and paste the link.
- 3
Connect and use it
If it needs a sign-in, Claude sends you to it. Then turn the connector on in a chat from the tools menu and ask.
Custom connectors are available on paid Claude plans; on Team and Enterprise accounts an admin may need to add them. Our "Working" label means the server answered us; it cannot tell whether your plan lets you add it. All connectors that work in Claude
https://mcp.aimyear.com/mcpWhat people ask Muse to do
Technical details: safety screening, tools, response time and recent checks
Response time at the last check: 130ms. Worked in n/a of checks over 30 days.
Screening · October 29, 2026
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
Tools · 40
get_goalThe one yearly goal: metric, starting value, current value, target, deadline, levers (hard/comfortable) and other projects. Call first in most flows.check_goal_draftCheck 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_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, 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_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. Pass existing ids to keep them.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 edit it. Pass existing ids to keep them.get_pathMilestones with pace (ahead/on_pace/behind) and their steps. current_milestone_id is the one to work on.set_milestonesReplace 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_milestoneChange 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_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 where it blocks it (warns otherwise).edit_stepChange one step: title, status (todo/doing/done), order, lever, estimate.delete_stepDelete one step from the path.next_stepsOpen steps of the current milestone, hard-lever steps first: the candidates for today's main step.get_commitmentsRecurring 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.get_capacityWeekly time budget out of 168 hours: overhead, hours committed per area, focus windows, and what is still unaccounted for. Nothing is assumed.get_planning_contextEverything 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_planThe 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 work, family, workout, etc. with their area. Items that stay kedit_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.get_routinesRoutines: 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_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 them. days are ISO weekdays 1=Mon..7=Sun, default every day.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_nowWhat 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. Several sessions may run at once (two terminals) and share attenadd_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. For a finished session use edit_session.stop_sessionStop 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_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_session first. Returns the break length.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.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 classified again after a change. Use it when a timer was forgotten delete_sessionDelete a session, running or finished, so it no longer counts. Without session_id it deletes this connection's running session.list_sessionsSessions in a date range (default the last 7 days), with ids, optionally filtered by area or project.find_gapsUntimed stretches of 20+ minutes between the first and last session of a day. Ask the user what happened there.summarize_dayFull summary of a day: wall and attention minutes per area, classification and lever, sessions, gaps, overlaps, overrides.summarize_weekA week, Monday to Sunday (to today for the current week): main-step days, goal share, hard share, area balance, overrides, streak, milestone pace.find_leaksWhere 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_settingsTimezone, where reminders go (desktop or mobile), and timer settings.set_settingsChange 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.Link
https://mcp.aimyear.com/mcpQuestions about AimYear in Muse
How do I connect AimYear to Muse?
Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use AimYear to help me. It is a free service with an MCP server at https://mcp.aimyear.com/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
Is AimYear working right now?
At the last check (October 29, 2026, 13:06 UTC) the endpoint was working, answering in 130ms. It is checked every 15 minutes.
Is AimYear safe to connect to Muse?
It was screened on October 29, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
What can AimYear do in Muse?
It exposes 40 tools, including get_goal, check_goal_draft, set_goal, record_progress. For example, you could ask Muse: "Help me set a goal to reach 10 paying customers by December and plan what to work on today to get there."
Follow AimYear
Made this app? Claim it or get a status badge
Is this yours?
This listing was added from public sources (Found in the official MCP Registry (io.github.Yahhi/aimyear-mcp)). If you build AimYear, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/aimyear"><img src="https://musedirectory.ai/badge/aimyear.svg" alt="AimYear on musedirectory.ai" width="236" height="40"></a>