mcp server

haus

OneHaus household tools: tasks, calendar, contacts, pets, vehicles, documents and more.

Description as published by the maintainer. Source

• version 1.3.0
• archived
• document understanding

archived — The linked repository returns 404. It was deleted, renamed or made private. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.

What this server can do

68 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

add_shopping_list_item(name, quantity)

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, keeping the existing item's category unchanged. Required: name.

assign_task(id, assignedToMemberId)

Assign or unassign a task to a household member. Required: id.

batch_add_shopping_list_items(items)

Add multiple items to the shopping list at once Required: items.

buy_shopping_list_item(id, quantityToBuy)

Buy item (decrements quantity; removes at zero) Required: id.

complete_task(id)

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. Required: id.

create_appliance(name, brand, model, notes, purchaseDate, serialNumber, warrantyDocumentId, warrantyExpiryDate, insuranceDocumentId)

Create an appliance record for the household, tracking purchase date, warranty expiry, and optional references to previously created warranty/insurance documents. Required: name.

create_calendar_event(notes, title, isAllDay, location, timezone, description, endDateTime, startDateTime)

Creates a single, one-off calendar event on the household calendar. For a repeating schedule use create_recurring_calendar_event instead. Required: title, startDateTime, isAllDay.

create_contact(email, notes, phone, address, lastName, firstName, dateOfBirth, displayName, prepareBirthdayPresent)

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. Required: firstName.

create_document(fee, notes, title, documentType, documentNumber, issuingAuthority, renewalCronExpression)

Create a document (passport, insurance, certificate, warranty, license, other) Required: documentType.

create_meal_plan(date, name, notes, mealType, recipeId, servings, recipeSource)

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. Required: date, mealType.

create_pet(name, notes, dateOfBirth, vetContactId, microchipNumber, insuranceDocumentId)

Create a pet. Supports microchip, vet contact, and insurance refs. Required: name.

create_recipe(url, name, servings, ingredients, instructions)

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. Required: name.

create_recurring_calendar_event(notes, title, endDate, duration, isAllDay, location, timezone, startDate, startTime, description, cronExpression, maxOccurrences)

Create a recurring calendar event that automatically generates event instances on a schedule. Required: title, cronExpression.

create_recurring_task(notes, title, endDate, startDate, cronExpression, maxOccurrences, preparationDays, assigneeRotation)

Create a recurring task that automatically generates task instances on a schedule. Required: title, cronExpression.

create_subscription(fee, name, notes, status, remindMe, renewalCronExpression)

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. Required: name, status.

create_task(notes, title, dueDate, preparationDate, assignedToMemberId)

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. Required: title.

create_vehicle(vin, make, year, model, notes, colour, motDueDate, taxDueDate, registration, serviceDueDate, insuranceDocumentId)

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.

defer_recommendation(recommendationId)

Add Later: defer a House Review recommendation and create a 7-day task Required: recommendationId.

delete_appliance(id)

Soft-delete an appliance; it is hidden from list_appliances but not permanently erased. Required: id.

delete_calendar_event(id)

Soft-deletes a single calendar event by id. Events imported from a calendar subscription cannot be deleted here; unsubscribe from the source calendar instead. Required: id.

delete_contact(id)

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. Required: id.

delete_document(id)

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. Required: id.

delete_meal_plan(id)

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. Required: id.

delete_pet(id)

Soft-delete a pet; it is hidden from list_pets but not permanently erased. Required: id.

delete_recipe(id)

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 they aren't left with a dangling recipe link. Required: id.

delete_recurring_calendar_event(id)

Delete a recurring calendar event and all its future instances. Required: id.

delete_recurring_task(id)

Delete a recurring task and all its uncompleted future instances. Required: id.

delete_subscription(id)

Soft-delete a subscription Required: id.

delete_task(id)

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. Required: id.

delete_vehicle(id)

Soft-delete a vehicle Required: id.

forget_memory(id)

Forget (soft-delete) a memory by id. Use when a memory is superseded or no longer relevant. Required: id.

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 server-side from the authenticated session.

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 they're returned. Pro-gated: fails if the household isn't on a Pro plan.

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.

get_weather_forecast(forecastDays)

Get weather forecast for the household's location

list_appliances

List all appliances in the household

list_calendar_events(startDateTo, startDateFrom)

List calendar events with optional date-range filters

list_contacts

List all contacts in the household. Takes no parameters; soft-deleted contacts are excluded.

list_documents(documentType)

List documents in the household, optionally filtered to a single document type. Soft-deleted documents are excluded.

list_global_recipes

List the global/Discover recipe catalogue (curated recipes available to all households)

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.

list_meal_plans(to, from)

List meal plans in the household with an optional date range

list_pets

List all pets in the household

list_recipes

List all recipes in the household

list_shopping_list_items

List all shopping list items in the household

list_subscriptions(status)

List subscriptions with optional status filter

list_tasks(limit, cursor, dueDateOnOrAfter, includeCompleted, dueDateOnOrBefore, assignedToMemberId)

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 date listed first.

list_vehicles

List all vehicles in the household

recall_memory(type, limit, cursor)

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.

remove_shopping_list_item(id)

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. Required: id.

skip_recommendation(recommendationId)

Skip: permanently suppress a House Review recommendation Required: recommendationId.

store_memory(name, type, content, description)

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. Required: type, name, description, content.

uncomplete_task(id)

Reopens a completed task, clearing its completion timestamp and completed-by user. Fails with a conflict if the task is not currently completed. Required: id.

update_appliance(id, name, brand, model, notes, purchaseDate, serialNumber, warrantyDocumentId, warrantyExpiryDate, insuranceDocumentId)

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. Required: id.

update_calendar_event(id, notes, title, isAllDay, location, timezone, description, endDateTime, startDateTime)

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. Required: id.

update_contact(id, email, notes, phone, address, lastName, firstName, dateOfBirth, displayName, prepareBirthdayPresent)

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). Required: id.

update_document(id, fee, notes, title, documentType, documentNumber, issuingAuthority, renewalCronExpression)

Update a document. Omitted fields unchanged. Required: id.

update_meal_plan(id, date, name, notes, mealType, recipeId, servings, recipeSource)

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. Required: id.

update_memory(id, name, content, description)

Update an existing memory's name, description, or content. Type is immutable; to reclassify, forget and store again. Required: id.

update_pet(id, name, notes, dateOfBirth, vetContactId, microchipNumber, insuranceDocumentId)

Update a pet. Omitted fields unchanged. Required: id.

update_recipe(id, url, name, servings, ingredients, instructions)

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. Required: id.

update_recurring_calendar_event(id, notes, title, endDate, duration, isAllDay, location, timezone, startDate, startTime, description, cronExpression, maxOccurrences)

Update a recurring calendar event. Changes to title/description/notes patch existing instances. Changes to frequency/dates/time regenerate future instances. Required: id.

update_recurring_task(id, notes, title, endDate, startDate, cronExpression, maxOccurrences, preparationDays, assigneeRotation)

Update a recurring task. Title/notes changes patch existing instances; frequency/date changes regenerate future instances. Required: id.

update_shopping_list_item(id, name, category, quantity)

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. Required: id.

update_subscription(id, fee, name, notes, status, remindMe, renewalCronExpression)

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. Required: id.

update_task(id, notes, title, dueDate, preparationDate, assignedToMemberId)

Update task title, assignment, dates, or notes. Required: id.

update_vehicle(id, vin, make, year, model, notes, colour, motDueDate, taxDueDate, registration, serviceDueDate, insuranceDocumentId)

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. Required: id.

Last successful function declaration observed on 2026-08-13. Source: https://mcp.onehaus.app. We list what the server declared; we do not call any of these functions.

Endpoint status observed on 2026-08-13. Source: https://mcp.onehaus.app.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Where to get it

• Repository — https://github.com/Im5tu/haus
• Website — https://onehaus.app
• Remote endpoint (streamable-http) — https://mcp.onehaus.app