UnRemind.me

Context-aware reminders that surface when your situation matches, not at a fixed time.

CommunityOnlineAPI key requiredGlobalFreeRead-only

What it can do

List Context Tags: Lists every context tag UnRemind understands, grouped (time, energy, type, device, connectivity, movement, people, payment, paymentAmount). Tags describe what a task REQUIRES to be
List Unreminders: Lists the signed-in user's own Unreminders (tasks), soonest due first. Does not include ones assigned to other people unless this user is the owner.
Create Unreminder: Submits a new Unreminder to the user for approval. It does NOT appear in their list immediately: like anything arriving from outside the account, it lands in their "Submitted to you

What data it sees

Do you need an account

An API key from the service settings is required

Context-aware reminders that surface when your situation matches, not at a fixed time. UnRemind.me stores reminders with context tags — location, device, connectivity, people present, energy, available time — and surfaces them when your current context matches. Tasks can be delegated to AI agents with scoped access rights and a full audit log.

Server tool list (16)

Raw names from tools/list. Only developers need these.

list_context_tags	Lists every context tag UnRemind understands, grouped (time, energy, type, device, connectivity, movement, people, payment, paymentAmount). Tags describe what a task REQUIRES to be doable (e.g. 'Computer' means the task needs a computer) -- never what the user currently has. Call this before create_unreminder/update_unreminder if unsure a tag string is valid.
list_unreminders	Lists the signed-in user's own Unreminders (tasks), soonest due first. Does not include ones assigned to other people unless this user is the owner.
create_unreminder	Submits a new Unreminder to the user for approval. It does NOT appear in their list immediately: like anything arriving from outside the account, it lands in their "Submitted to you" queue and becomes real only once they accept it. Say so when reporting back -- do not tell the user their reminder is set. Requires the create permission on this connection.
update_unreminder	Updates fields on one of the signed-in user's own Unreminders. Only the fields provided are changed.
complete_unreminder	Marks one of the signed-in user's own Unreminders as completed.
list_my_tasks	Lists Unreminders the user has ASSIGNED TO YOU as an agent to carry out -- your work queue, not the user's own list. Call this whenever the `inbox.pending_tasks` count on any response is above zero, and at the start of a working session. Returns each task's id, title, due date, context tags and current work status. Fetch the full brief for one with get_task before starting it.
get_task	Full brief for one task assigned to you: the complete notes, due date, context tags, place, the owner's standing instructions for you, and the comment history so far. Call this before starting work -- list_my_tasks is a summary and deliberately omits the detail you need to actually execute.
update_task_status	Reports progress on a task assigned to you, with a comment the user will see in the task history. Use 'in_progress' when you start, 'blocked' if something outside your control stops you, and 'done' when the work is genuinely finished. Do not report 'done' for work you could not verify. To ask the user a question, use ask_owner instead -- it notifies them, this does not.
comment_on_task	Adds a comment to a task assigned to you without changing its status. Use for progress notes, findings, or context worth recording. Visible to the user in the task's history.
ask_owner	Hands a task back to the user with a question, when you cannot proceed without a decision or information only they have. This sets the task to 'needs_input' and notifies them in the app, so it reaches them without them having to come and check on you. Prefer this over guessing an answer or reporting the task done with caveats. This is the ONLY way an agent can assign work to a person -- agents cannot assign tasks to other agents.
orient	START HERE at the beginning of a working session, and after any long gap. Returns who this user is and how they want to be worked with (their standing preferences), what you were last doing and where to resume, anything still open on your side, and a snapshot of what needs attention. One call replaces guessing. Cheap — do not skip it to save a round trip.
save_progress	Records what you just did and what should happen next, so a future session (yours or another agent's) can resume instead of starting cold. Call this before you finish a session, and after any meaningful step. Keep it short and factual — it is shown back to you on every orient, and it costs the user tokens every time. These are YOUR notes, not a source of truth: the user edits their tasks in the app between sessions, so always re-read the live task before acting on a recollection.
check_conflicts	Checks whether a proposed time collides with the user's real Google Calendar meetings or with other Unreminders already due around then, and offers free slots nearby. Call this BEFORE proposing or setting any due date — the user's whole reason for this app is not being ambushed by their own schedule. Events the user marked Free, and Unreminders this app itself exported to their calendar, are correctly ignored.
review_workload	The state of the user's commitments: what is overdue, what is due soon, and what has no due date at all. Use this to answer 'how am I doing', to open a check-in, or before proposing new work — adding to a pile of twelve overdue items is rarely the helpful move. Report honestly; do not soften an overdue count.
suggest_next_task	Suggests what to work on right now, given how much time the user has. Ranks by what is overdue or imminent, then by what fits the time available. This is a starting point for a conversation, not a verdict — say why you are suggesting it and let the user redirect. If they are in a specific context (at a computer, on the move, low energy), pass their tags so the suggestion respects what the task actually needs.
get_guide	Fetches detailed guidance for one kind of work — scheduling, delegating, capturing tasks well, setup, or the context-tag vocabulary. Read the relevant guide BEFORE a task you have not done before in this session. Each covers the syntax, worked good and bad examples, and exactly when to stop and ask the user rather than decide.