Haus MCP Server

app.onehaus/haus

answering

Haus is answering right now. Last checked moments ago. It exposes 68 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 41 hours of history

41 hours agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

192 ms

Response time

average over 24h

open, no key

Access

streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add haus --transport http https://mcp.onehaus.app

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "haus": {
      "url": "https://mcp.onehaus.app"
    }
  }
}

~/.codex/config.toml

[mcp_servers.haus]
url = "https://mcp.onehaus.app"

.cursor/mcp.json

{
  "mcpServers": {
    "haus": {
      "url": "https://mcp.onehaus.app"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "haus": {
      "url": "https://mcp.onehaus.app"
    }
  }
}

Available tools 68

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

recurring

create_recurring_calendar_event

Create a recurring calendar event that automatically generates event instances on a schedule.

create_recurring_task

Create a recurring task that automatically generates task instances on a schedule.

delete_recurring_calendar_event

Delete a recurring calendar event and all its future instances.

delete_recurring_task

Delete a recurring task and all its uncompleted future instances.

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.

update_recurring_task

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

calendar

create_calendar_event

Creates a single, one-off calendar event on the household calendar. For a repeating schedule use create_recurring_calendar_event instead.

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

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.

meal

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.

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

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.

shopping

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

list_shopping_list_items

List all shopping list items in the household

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.

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.

appliance

create_appliance

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

delete_appliance

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

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.

contact

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.

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.

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).

document

create_document

Create a document (passport, insurance, certificate, warranty, license, other)

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.

update_document

Update a document. Omitted fields unchanged.

house

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.

list_house_members

List household members with their userId, name, nickname, and role.

pet

create_pet

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

delete_pet

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

update_pet

Update a pet. Omitted fields unchanged.

recipe

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.

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

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.

subscription

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.

delete_subscription

Soft-delete a subscription

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.

task

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.

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.

update_task

Update task title, assignment, dates, or notes.

vehicle

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.

delete_vehicle

Soft-delete a vehicle

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.

appliances

list_appliances

List all appliances in the household

assign

assign_task

Assign or unassign a task to a household member.

batch

batch_add_shopping_list_items

Add multiple items to the shopping list at once

buy

buy_shopping_list_item

Buy item (decrements quantity; removes at zero)

complete

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.

contacts

list_contacts

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

defer

defer_recommendation

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

documents

list_documents

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

forget

forget_memory

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

global

list_global_recipes

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

houses

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.

memory

update_memory

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

pets

list_pets

List all pets in the household

profile

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.

recall

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.

recipes

list_recipes

List all recipes in the household

skip

skip_recommendation

Skip: permanently suppress a House Review recommendation

store

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.

subscriptions

list_subscriptions

List subscriptions with optional status filter

tasks

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

uncomplete

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.

vehicles

list_vehicles

List all vehicles in the household

weather

get_weather_forecast

Get weather forecast for the household's location

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.onehaus.app	streamable-http	answering	160 ms	0 min ago

Haus — questions

Answers built from our own checks of this server.

What can Haus do?

It exposes 68 tools, read directly from the server on our last check. Among them: add_shopping_list_item, assign_task, batch_add_shopping_list_items, buy_shopping_list_item, complete_task, create_appliance and 62 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Haus mostly used for?

Its tools cluster around recurring, meal and shopping. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Haus working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 192 ms. The bar chart above shows every period we have measured.

Is Haus still maintained?

The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.

How do I connect Haus?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Haus need an API key?

No. Haus completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 68 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Haus?

It answers our handshake in 192 ms on average, which is faster than 64% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.