MCP Server for ZenTao bug management with CAS SSO login
from $14/mo
Tools
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.
ArgumentsA call is made on an account: it counts against an allowance and the publisher sees it, which is why this one asks who you are first.
—
p95 latency
—
call success
—
uptime 90d
0
calls last 7d
What it does
OneHaus household tools: tasks, calendar, contacts, pets, vehicles, documents and more.
Quickstart
# 1 — install (mcprush login holds a key from your dashboard)
npx mcprush@latest add haus-mcp
# 2 — ask your agent something
> OneHaus household tools: tasks, calendar, contacts, pets, vehicles, documents and more.
Haus is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
MCAll 1 server
mcp.onehaus.app1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine — this server runs on the publisher’s own infrastructure behind our gateway, and what you install is the connection to it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add --transport http haus-mcp https://mcp.onehaus.app/Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it writes
One config entry pointing at the gateway. The server itself runs on the publisher’s own infrastructure, so nothing from this listing executes on your machine.
What you approve
68 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
Takes no parameters.
Example callreturns →
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).
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
List all contacts in the household. Takes no parameters; soft-deleted contacts are excluded.
Takes no parameters.
Example callreturns →
Create an appliance record for the household, tracking purchase date, warranty expiry, and optional references to previously created warranty/insurance documents.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Soft-delete an appliance; it is hidden from list_appliances but not permanently erased.
Takes no parameters.
Example callreturns →
List all appliances in the household
Takes no parameters.
Example callreturns →
Creates a single, one-off calendar event on the household calendar. For a repeating schedule use create_recurring_calendar_event instead.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Soft-deletes a single calendar event by id. Events imported from a calendar subscription cannot be deleted here; unsubscribe from the source calendar instead.
Takes no parameters.
Example callreturns →
List calendar events with optional date-range filters
Takes no parameters.
Example callreturns →
Create a document (passport, insurance, certificate, warranty, license, other)
Takes no parameters.
Example callreturns →
Update a document. Omitted fields unchanged.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
List documents in the household, optionally filtered to a single document type. Soft-deleted documents are excluded.
Takes no parameters.
Example callreturns →
Create a pet. Supports microchip, vet contact, and insurance refs.
Takes no parameters.
Example callreturns →
Update a pet. Omitted fields unchanged.
Takes no parameters.
Example callreturns →
Soft-delete a pet; it is hidden from list_pets but not permanently erased.
Takes no parameters.
Example callreturns →
List all pets in the household
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Soft-delete a subscription
Takes no parameters.
Example callreturns →
List subscriptions with optional status filter
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Soft-delete a vehicle
Takes no parameters.
Example callreturns →
List all vehicles in the household
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Update task title, assignment, dates, or notes.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Reopens a completed task, clearing its completion timestamp and completed-by user. Fails with a conflict if the task is not currently completed.
Takes no parameters.
Example callreturns →
Assign or unassign a task to a household member.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Get weather forecast for the household's location
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
List household members with their userId, name, nickname, and role.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
List all shopping list items in the household
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Buy item (decrements quantity; removes at zero)
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Add Later: defer a House Review recommendation and create a 7-day task
Takes no parameters.
Example callreturns →
Skip: permanently suppress a House Review recommendation
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Update an existing memory's name, description, or content. Type is immutable; to reclassify, forget and store again.
Takes no parameters.
Example callreturns →
Forget (soft-delete) a memory by id. Use when a memory is superseded or no longer relevant.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
List meal plans in the household with an optional date range
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
List all recipes in the household
Takes no parameters.
Example callreturns →
List the global/Discover recipe catalogue (curated recipes available to all households)
Takes no parameters.
Example callreturns →
Add multiple items to the shopping list at once
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Create a recurring calendar event that automatically generates event instances on a schedule.
Takes no parameters.
Example callreturns →
Update a recurring calendar event. Changes to title/description/notes patch existing instances. Changes to frequency/dates/time regenerate future instances.
Takes no parameters.
Example callreturns →
Delete a recurring calendar event and all its future instances.
Takes no parameters.
Example callreturns →
Create a recurring task that automatically generates task instances on a schedule.
Takes no parameters.
Example callreturns →
Update a recurring task. Title/notes changes patch existing instances; frequency/date changes regenerate future instances.
Takes no parameters.
Example callreturns →
Delete a recurring task and all its uncompleted future instances.
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Haus costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is a hosted endpoint: the publisher runs it and we connect to it. The scanner reads packages and source, and neither exists to read here, so there is no grade — not a withheld one, an unmeasured one. What can be checked instead is on Installation: what it asks to reach and what it writes.
Release history
Pinned to 1.4.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
1.4.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Haus in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.