# OneHaus Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## OneHaus

Household management: tasks, calendar, contacts, pets, vehicles, appliances, documents and subscriptions.

- Record: https://musedirectory.ai/connector/onehaus
- Category: Productivity
- Developer: Im5tu (https://onehaus.app)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 879ms, checked 2026-09-28T08:31:27Z
- Endpoint: https://mcp.onehaus.app/
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-24T08:16:10Z)
- Source: Found in the official MCP Registry (app.onehaus/haus) https://registry.modelcontextprotocol.io/v0/servers?search=app.onehaus%2Fhaus

OneHaus connects to a household management system for shared tasks, calendar events, contacts, pet and vehicle records, appliance warranties, documents, and subscription tracking. Muse can create and update household records, assign tasks to members, check weather forecasts, and manage shared household data.

Example request: "Add a task to take out the recycling and assign it to my partner for Thursday."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use OneHaus to help me. It is a free service with an MCP server at https://mcp.onehaus.app/. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- create_contact: Add a contact to the address book. Only firstName is required; address, date of birth, notes and the birthday-present flag can follow via 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 the household's appliances with brand, model, serial number, purchase date and warranty expiry. Answers whether something is still under warranty.
- create_calendar_event: Creates a single, one-off calendar event on the household calendar. Timed events need startDateTime; all-day events need startDate (plus endDate for several days). Set reminders with reminderOffsetMinutes. 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. Events shared from a member's device calendar can only be removed by that member or the house owner.
- list_calendar_events: List one-off calendar events with their title, times, location and notes. Bound them with startDateFrom and startDateTo, or omit both for everything. An all-day event's end depends on its sourceEntityType. With no source, endDateTime is its LAST day (inclusive), or null for a sin
- create_document: Store a document (passport, insurance, certificate, warranty, license, other) with its reference number, issuing authority, fee and notes. Returns the new id, which an appliance, vehicle or pet can link to.
- update_document: Update a stored document's type, title, reference number, issuing authority, fee or notes, returning the updated document. Only the fields you send change. renewalCronExpression is the one exception: it is accepted but not yet stored or acted on, so sending it changes nothing.
- 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: Add a pet, optionally with its microchip number and date of birth, and links to an existing contact as vet and document as insurance. Returns the new pet's id.
- update_pet: Update a pet's name, microchip number, date of birth, notes, or its linked vet contact and insurance document. Only the fields you send change.
- delete_pet: Soft-delete a pet; it is hidden from list_pets but not permanently erased.
- list_pets: List the household's pets with microchip number, date of birth, notes and their linked vet contact and insurance document.
- create_subscription: Track a bill such as a streaming service or membership, with an optional fee and cron renewal schedule (no more often than daily). A bill with no renewal schedule is a one-off. Set paymentDate only when the money leaves the account on a different day from the renewal.
- update_subscription: Update a subscription. Only the fields you send change; for renewalCronExpression, startDate, paymentDate and notes an empty string clears the stored value.
- delete_subscription: Soft-delete a subscription so it leaves list_subscriptions; the record is retained. Use it when the user cancels a service.
- list_subscriptions: List tracked subscriptions with their fee, renewal schedule, payment date and status. A subscription with no renewal schedule is a one-off. startDate is the renewal date: the first renewal of a recurring bill, or when a one-off is due; paymentDate, when set, is the first day mone
- 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: Update a vehicle. Only the fields you send change; for text and due-date fields an empty string clears the stored value.
- delete_vehicle: Soft-delete a vehicle so it leaves list_vehicles; the record is retained. Use it when the household sells a car.
- list_vehicles: List the household's vehicles with make, model, year, registration, VIN and MOT, tax and service due dates. Answers questions like when the MOT is due.
- create_task: Creates a new household task. Only title is required; the task starts unassigned and uncompleted. Set reminders with reminderOffsetMinutes. Use assign_task, update_task, or complete_task to change it afterward.
- update_task: Update a task's title, assignee, due date, reminders, notes or urgency. Only the fields you send change.
- delete_task: Soft-delete a task. It leaves list_tasks but the record is retained. Fails if it 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: List tasks, filterable by assignee, due-date range and completion, with cursor pagination. Excludes completed tasks by default and sorts open urgent tasks first (within the returned page), then due date ascending (undated first).
- get_weather_forecast: Return a one-to-five day forecast for the household's location, for planning outdoor tasks or events.
- get_house: Return the current household in full: name, address, invite code, notes, join settings, members, subscription status and resolved feature flags.
- list_house_members: List the household's members with id, userId, first and last name, nickname and role. Use a member's id as assignedToMemberId in create_task and assign_task.
- 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 signed-in user's profile: name, email, AI-consent status and timezone. Also bumps their last-seen activity as a side effect.

Screening checks:
- MCP handshake: pass (Answered in 147ms)
- Domain against threat feeds (Cloudflare security DNS): pass (mcp.onehaus.app, onehaus.app not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (69 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)