Habidu
Server Details
Habidu is an AI daily coach. This remote MCP server lets Claude or any MCP client read and change your daily plan: tasks, inbox, routines, streak and journal, or ask the Habidu coach. Sign in with OAuth using your Habidu account. Setup guide: https://www.habidu.com/connect-claude/?src=glama
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 15 tools
Every tool targets a distinct resource+action pair, and the descriptions actively cross-reference the nearest alternatives (create_task vs create_inbox_item vs create_routine; delete_task vs delete_routine vs delete_inbox_item), including the edge cases like repeating tasks appearing in get_tasks. The only potential overlaps — one-off repeating tasks vs routines, or a routine showing in both get_routines and get_tasks — are explicitly explained rather than left ambiguous.
All 15 tools follow a single snake_case verb_noun convention (create_/get_/update_/delete_ plus ask_coach and save_journal). The resource nouns (task, routine, inbox_item, journal) are reused identically across verbs, so the CRUD matrix is predictable at a glance.
15 tools sit at the top of the well-scoped range, and each one maps to a real operation in a small productivity domain (tasks, routines, inbox, journal, streak, coach). Nothing looks redundant or filler-like; the CRUD sets per resource account for most of the count.
Tasks, routines, and journal have full read/create/update/delete coverage, and the coach and streak tools round out the domain. Minor gaps remain: there is no update_inbox_item (only create-with-merge and delete), get_tasks is limited to a single day with no range/search query, and journal entries cannot be deleted — all workaroundable but real limitations.
Publisher details
- Operator
- Habidu (RynovaLabs)
- Operator website
- https://www.habidu.com/?src=glama
- Vendor relationship
- First-party
- Documentation
- https://www.habidu.com/connect-claude/?src=glama
- Privacy policy
- Not provided
- Trust center
- Not available
- Restrictions
- Requires a Habidu account (sign in with OAuth). Free trial, then a Habidu subscription.
Available Tools
15 toolsask_coachAsk the Habidu coachADestructiveInspect
Send a message to the user's Habidu AI coach and get its reply. Use it for advice, reflection, an overwhelming day, or a plan the user wants talked through; the coach knows their history and routines. For any direct change (add, move or delete a task, an inbox item or a routine) use the task / inbox / routine tools instead. Returns {ok:true, reply, suggestedReplies?, writes, tasksChanged}: the coach may still change the schedule when the user asks it to, and writes lists what it changed. The exchange also appears in the app's coach chat and counts toward the coach's daily limit. ok:false reasons: coach_limit, ai_consent_required, empty_message.
Inputs: message (required).
create_inbox_itemCreate an inbox itemAInspect
Capture ONE to-do with NO date or time into the user's Habidu Inbox: an idea, an errand, a call, or something they are waiting on. Use create_task instead when the user gives a day or a time. Returns {id, title, ...}. If the same item is already in the Inbox it is updated in place and the result carries merged:true - tell the user it was updated, not added. ok:false means nothing was saved. Not preview-gated.
Inputs: title (required), category, priority, waiting_on, +1 more.
create_routineCreate a routineAInspect
Create a NEW repeating routine for the user: a named block at a set time with ordered steps, e.g. "Gym routine" at 18:00 with Warm up 10 min and Lift 40 min. Use it for something done regularly as a sequence of steps; use create_task for a one-off or a simple repeating task, and update_routine to change an existing routine, including the built-in morning and evening routines, which always exist. It runs every day from today unless daysOfWeek is given. Returns {ok:true, id, title, hour, minute, durationMin, steps, daysOfWeek}. Refused with ok:false and nothing saved: reserved_title or title_taken (call get_routines first), invalid_args. Preview rule: if this is the second task or routine change within about 90 seconds, nothing is saved and the result is needs_preview with the pending and saved changes - show them to the user and call again with confirm:true only after they agree.
Inputs: hour (required), title (required), steps, minute, +4 more.
create_taskCreate a taskAInspect
Add ONE task to a day of the user's Habidu schedule: title, date, start time, duration, optional repeat, steps (subTasks) and a "Bring / prep" checklist. Use it when the user gives a day or a time; for an undated to-do use create_inbox_item, for a step-by-step habit use create_routine, and to change an existing task use update_task. Returns the stored task with its id; it then shows in the app and gets reminders. A past date, an overlap or an identical block comes back ok:false with a hint and is NOT saved - tell the user why, never say it was added. Preview rule: if this is the second task or routine change within about 90 seconds, nothing is saved and the result is needs_preview with the pending and saved changes - show them to the user and call again with confirm:true only after they agree.
Inputs: title (required), min, date, hour, +25 more.
delete_inbox_itemDelete an inbox itemADestructiveIdempotentInspect
Remove ONE item from the user's Habidu Inbox by id (from get_inbox, preferred) or by exact title (case-insensitive) - when it is done, unwanted, or was just scheduled with create_task. For a scheduled task use delete_task. Returns {ok:true, removed:true, id}; ok:false with not_found means nothing was removed. A removed item cannot be restored. Not preview-gated.
Inputs: id, title.
delete_routineDelete a routineADestructiveIdempotentInspect
Permanently delete ONE of the user's own routines by id (from get_routines), with its history. The built-in morning and evening routines cannot be deleted (ok:false managed_routine): switch them off with update_routine enabled:false, which is also the better choice when the user may want a routine back. To skip a routine for one day use delete_task with its id and that date. Returns {ok:true, id, deleted:true, title}; ok:false (not_found, not_a_routine, managed_routine) deleted nothing. Preview rule: if this is the second task or routine change within about 90 seconds, nothing is saved and the result is needs_preview with the pending and saved changes - show them to the user and call again with confirm:true only after they agree.
Inputs: id (required), confirm.
delete_taskDelete a taskADestructiveIdempotentInspect
Delete ONE task by id (from get_tasks). On a repeating task, scope "occurrence" (the default) removes only one day (date, default today) and keeps the series; "series" deletes the whole repeating task. Use delete_inbox_item for Inbox items and delete_routine for routines. Returns {id, deleted:true}, or {deleted:false, scope:"occurrence", excludedDate} for one day; not_found means nothing changed. A deleted task cannot be restored. Preview rule: if this is the second task or routine change within about 90 seconds, nothing is saved and the result is needs_preview with the pending and saved changes - show them to the user and call again with confirm:true only after they agree.
Inputs: id (required), date, scope, confirm.
get_inboxGet inboxARead-onlyIdempotentInspect
Read the user's Habidu Inbox: captured items with no day or time yet, each with id, title, context tag (calls/commute/errands/deep), priority, waiting-for and someday flags. Active items come first, someday items last. Use it before delete_inbox_item (for the id) or to help the user decide what to schedule; scheduled work is in get_tasks. An empty inbox returns count 0. Read-only, takes no parameters.
Inputs: no named parameters.
get_journalGet journal entriesARead-onlyIdempotentInspect
Read the user's Habidu journal: one entry per day with their morning and/or evening answers (keyed by prompt, e.g. intention, gratitude, win, lesson), newest first. With no parameters it returns the 7 most recent entries; send date for one day, or from/to for a range of at most 31 days. Use it for reflection, weekly reviews or to recall what the user wrote; write entries with save_journal. Days with nothing written are left out; no entries returns count 0 with a note. Read-only.
Inputs: to, date, from, limit.
get_routinesGet routinesARead-onlyIdempotentInspect
Read ALL of the user's Habidu routines - the built-in morning and evening routines (routineKey morning/evening) and their own - sorted by start time, each with id, title, time, duration, repeat days, per-weekday times, ordered steps and enabled (false = switched off or archived). Use it before update_routine or delete_routine for the ids and current steps. Today's single occurrences are also in get_tasks. No routines returns count 0. Read-only, takes no parameters.
Inputs: no named parameters.
get_streakGet streakARead-onlyIdempotentInspect
Read the user's Habidu streak as the app shows it: the current run of consecutive days with at least one completed task, plus the longest streak, stars and banked streak freezes, and the last completed date. Use it to celebrate progress or answer "how is my streak"; it does not list tasks (get_tasks). A new user returns streak 0. Read-only, takes no parameters.
Inputs: no named parameters.
get_tasksGet tasks for a dayARead-onlyIdempotentInspect
Read the user's Habidu schedule for ONE day: timed tasks, all-day tasks, repeating tasks and routines that occur that day, sorted by start time, each with its id, title, time, duration, done state and steps (subTasks). Use it before update_task or delete_task to get the ids, and to answer "what is on my day". Unscheduled captures are in get_inbox, not here; the full routine list is get_routines. An empty day returns count 0. Read-only.
Inputs: date.
save_journalSave journal entryADestructiveIdempotentInspect
Save the user's journal entry for a day: the evening reflection (win, mistakes, lessons, improve), the morning intention, or answers to their own journal prompts as {id, answer}. Use get_journal to read entries back. Saving a section (morning or evening) again for the same date replaces that section and keeps the other; a morning intention also updates the app's "ONE thing" card. Nothing is added to the schedule. Returns {ok:true, date, type}; ok:false (e.g. empty_answers) saved nothing. Not preview-gated.
Inputs: type (required), win, date, answers, +4 more.
update_routineUpdate a routineADestructiveIdempotentInspect
Change ONE routine by id (from get_routines): rename it, move its start time, set per-weekday times or days, change its length or steps, or switch it on or off. Only the fields you send change. steps REPLACES the whole list (send every step in order); addSteps and removeSteps edit it. When steps change, the length follows them unless durationMin is sent. Use update_task for tasks that are not routines, and delete_task with a date to skip a routine for one day. Editing the built-in morning or evening routine also switches it on. Returns {ok:true, id, title, hour, minute, durationMin, steps, daysOfWeek, enabled?}; ok:false (not_found, not_a_routine, title_taken, reserved_title, invalid_args) changed nothing. Preview rule: if this is the second task or routine change within about 90 seconds, nothing is saved and the result is needs_preview with the pending and saved changes - show them to the user and call again with confirm:true only after they agree.
Inputs: id (required), hour, steps, title, +8 more.
update_taskUpdate a taskADestructiveIdempotentInspect
Change ONE existing task by id (from get_tasks): time, date, title, duration, done, repeat, steps, checklist, priority, alert type and more. Only the fields you send change. Use it to move, rename or tick off a task; use delete_task to remove it and update_routine for a routine. On a repeating task, hour/min/date move EVERY day; occurrence_date moves one day and done_date ticks one day. subTasks and checklist REPLACE the whole list (send every item). Returns {id, updated, ...}; ok:false or an error such as not_found means nothing was saved. Preview rule: if this is the second task or routine change within about 90 seconds, nothing is saved and the result is needs_preview with the pending and saved changes - show them to the user and call again with confirm:true only after they agree.
Inputs: id (required), min, date, done, +31 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceRemote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.MIT
- AlicenseCqualityCmaintenanceCompetitor Monitor AI - MCP server providing AI-powered tools and automation by MEOK AI Labs112 npm46 PyPIMIT
- AlicenseAqualityDmaintenanceEnables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.1611 npm1MIT

industrylens-mcpofficial
AlicenseNot gradedqualityCmaintenanceBrowse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.