app.onehaus/haus
app.onehaus/haus · v1.3.0 · MCP 2026-07-28
OneHaus household tools: tasks, calendar, contacts, pets, vehicles, documents and more.
Reachability
reachable
checked 2026-08-29 05:49 UTC
Registry status active
Tools pinned 68
8013248d6c4a
Tools last changed
2026-07-22
Provenance
Registry namespace app.onehaus
(domain verified by the official registry)
Repository
github.com/im5tu/haus
repo gone
Website
https://onehaus.app
Remote endpoints
https://mcp.onehaus.app (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-07-22 05:46 | tools changed | 0 added, 0 removed, 68 changed |
| 2026-07-14 03:05 | first capture | 68 tools pinned |
Pinned tool definitions (68)
| Tool | Description |
|---|---|
| create_contact | Create a contact in the household's address book. Only firstName is required; all other details (address, date of birth, notes, a flag to prepare a birthday present) are optional and can be filled in later with update_contact. |
| update_contact | Update a contact by id. Only the fields supplied are changed; omitted fields keep their current value (dateOfBirth is the exception: an empty string explicitly clears it). |
| delete_contact | Soft-delete a contact by id; it is marked deleted and no longer appears in list_contacts, but the underlying record is retained rather than permanently erased. |
| list_contacts | List all contacts in the household. Takes no parameters; soft-deleted contacts are excluded. |
| create_appliance | Create an appliance record for the household, tracking purchase date, warranty expiry, and optional references to previously created warranty/insurance documents. |
| update_appliance | Update an appliance's details; omitted fields keep their current value. Rejects the update if the resulting warranty expiry date would fall before the purchase date. |
| delete_appliance | Soft-delete an appliance; it is hidden from list_appliances but not permanently erased. |
| list_appliances | List all appliances in the household |
| create_calendar_event | Creates a single, one-off calendar event on the household calendar. For a repeating schedule use create_recurring_calendar_event instead. |
| update_calendar_event | Updates fields on an existing single calendar event; only the fields supplied are changed, all others keep their current value. Imported (subscription-sourced) events cannot be edited. |
| delete_calendar_event | Soft-deletes a single calendar event by id. Events imported from a calendar subscription cannot be deleted here; unsubscribe from the source calendar instead. |
| list_calendar_events | List calendar events with optional date-range filters |
| create_document | Create a document (passport, insurance, certificate, warranty, license, other) |
| update_document | Update a document. Omitted fields unchanged. |
| delete_document | Soft-delete a document by id and cascade soft-delete its attachments; none of them appear in listings afterward, but the records are retained rather than permanently erased. |
| list_documents | List documents in the household, optionally filtered to a single document type. Soft-deleted documents are excluded. |
| create_pet | Create a pet. Supports microchip, vet contact, and insurance refs. |
| update_pet | Update a pet. Omitted fields unchanged. |
| delete_pet | Soft-delete a pet; it is hidden from list_pets but not permanently erased. |
| list_pets | List all pets in the household |
| create_subscription | Create a subscription for the household to track a recurring cost, such as a streaming service or membership. Accepts an optional cron-based renewal schedule (must not repeat more frequently than once a day) and a fee amount. |
| update_subscription | Partially update an existing subscription; only the fields provided are changed, everything else is left as-is. For renewalCronExpression and notes, sending an empty string clears the stored value rather than leaving it unchanged. |
| delete_subscription | Soft-delete a subscription |
| list_subscriptions | List subscriptions with optional status filter |
| create_vehicle | Create a vehicle record for the household to track its details, registration and VIN, insurance document, and upcoming MOT/tax/service due dates. All fields are optional. |
| update_vehicle | Partially update an existing vehicle's details; only the fields provided are changed, everything else is left as-is. For string and due-date fields, omitting the field leaves the stored value unchanged, while sending an empty string clears it. |
| delete_vehicle | Soft-delete a vehicle |
| list_vehicles | List all vehicles in the household |
| create_task | Creates a new household task. Only title is required; the task starts unassigned and uncompleted. Use assign_task, update_task, or complete_task to change it afterward. |
| update_task | Update task title, assignment, dates, or notes. |
| delete_task | Soft-deletes a task: it stops appearing in list_tasks but the record is retained rather than permanently removed. Fails if the task was already deleted. |
| complete_task | Marks a task as completed and records the completion for the household's momentum stats. Fails with a conflict if the task is already completed. |
| uncomplete_task | Reopens a completed task, clearing its completion timestamp and completed-by user. Fails with a conflict if the task is not currently completed. |
| assign_task | Assign or unassign a task to a household member. |
| list_tasks | Lists tasks in the household with optional filters (assignee, due-date range, completion status) and cursor-based pagination. Excludes completed tasks by default; results are sorted by due date ascending, with tasks that have no due... |
| get_weather_forecast | Get weather forecast for the household's location |
| get_house | Return full details for the household the current session is scoped to: name, address, invite code, notes, join settings, members, subscription status, and resolved feature-flag states. No parameters — the household is resolved... |
| list_house_members | List household members with their userId, name, nickname, and role. |
| list_houses | List the households the current user belongs to (e.g. to tell the user which home you are acting on). The active house is determined server-side from the authenticated session. |
| get_profile | Return the authenticated user's profile: name, email, AI-consent status, and timezone. Also records this call as user activity (bumps last-seen) as a side effect. No parameters — the user is resolved server-side from the authenticated session. |
| list_shopping_list_items | List all shopping list items in the household |
| add_shopping_list_item | Add an item to the household's shopping list. A brand-new item gets a category auto-assigned from its name. If an unbought item with a matching name already exists, its quantity is merged into that item instead of creating a duplicate,... |
| buy_shopping_list_item | Buy item (decrements quantity; removes at zero) |
| get_house_review | Return this week's pending House Review recommendations (data gaps like a missing appliance warranty date or vehicle MOT date), re-validated live so items already filled in, actioned, or superseded by an open task are dropped before... |
| defer_recommendation | Add Later: defer a House Review recommendation and create a 7-day task |
| skip_recommendation | Skip: permanently suppress a House Review recommendation |
| store_memory | Store a long-term memory about the household. Use sparingly for durable preferences, routines, constraints, or insights worth recalling in a future conversation. Recall first to avoid duplicates. |
| update_memory | Update an existing memory's name, description, or content. Type is immutable; to reclassify, forget and store again. |
| forget_memory | Forget (soft-delete) a memory by id. Use when a memory is superseded or no longer relevant. |
| recall_memory | Recall long-term memories stored about the current household. Call this at the start of advisory or open-ended turns. Filter by type when only one author's notes are relevant. |
| create_meal_plan | Plan a meal for a specific date and meal type. Provide recipeId to link an existing recipe (from list_recipes) OR name for a custom meal; when recipeId is given any name is ignored and stored as null. |
| update_meal_plan | Update a meal plan entry. Any field left out keeps its current value. Provide recipeId to link a recipe (clears any custom name) or name to make it a custom meal (clears the recipe link); recipeId takes precedence when both are given. |
| delete_meal_plan | Remove a planned meal from the household's meal plan. This is a soft delete: the entry stops appearing in list_meal_plans and its date/meal-type slot becomes free again. |
| list_meal_plans | List meal plans in the household with an optional date range |
| create_recipe | Create a new recipe in the household's recipe collection, with optional ingredients, source URL, instructions and serving size. Link it to a date with create_meal_plan, or browse it later with list_recipes. |
| update_recipe | Update an existing recipe. Only the fields provided are changed; any field left out keeps its current value. Providing ingredients replaces the entire ingredient list rather than merging with the existing one. |
| delete_recipe | Delete a recipe from the household's collection. This is a soft delete; any meal plan entries still linked to this recipe are automatically converted into custom entries that keep a snapshot of its name, ingredients and instructions, so... |
| list_recipes | List all recipes in the household |
| list_global_recipes | List the global/Discover recipe catalogue (curated recipes available to all households) |
| batch_add_shopping_list_items | Add multiple items to the shopping list at once |
| update_shopping_list_item | Update a shopping list item's name, quantity, and/or category. Only the fields provided are changed; any field left out keeps its current value. |
| remove_shopping_list_item | Remove an item from the household's shopping list without marking it as bought. This soft-deletes the item so it no longer appears in list_shopping_list_items. |
| create_recurring_calendar_event | Create a recurring calendar event that automatically generates event instances on a schedule. |
| update_recurring_calendar_event | Update a recurring calendar event. Changes to title/description/notes patch existing instances. Changes to frequency/dates/time regenerate future instances. |
| delete_recurring_calendar_event | Delete a recurring calendar event and all its future instances. |
| create_recurring_task | Create a recurring task that automatically generates task instances on a schedule. |
| update_recurring_task | Update a recurring task. Title/notes changes patch existing instances; frequency/date changes regenerate future instances. |
| delete_recurring_task | Delete a recurring task and all its uncompleted future instances. |
Get alerted when this changes.
Email the moment app.onehaus/haus drifts, dies, or revives.
Status badge
[](https://toolpin.dev/servers/app.onehaus/haus)
Maintain this server? Add the badge to your README. It links your users to this live status page.