hostaway-kit MCP server

Read from the package source without running it. The installed server may list more.

• draft_reply

  Suggested reply grounded in THAT listing's fields, house rules, amenityId values, and calendar prices. Never invent rates (use calendar or say unknown). Never include wifi or door codes. Never POSTs a message — send is always false and there is no send endpoint.

• get_calendar

  Retrieve listing calendar via GET /v1/listings/{id}/calendar?includeResources=1. Each day has status (available/blocked/reserved/pending), isAvailable, and price (null means unknown — do not invent a rate). Nested reservations are denylist-stripped.

• get_listing

  Retrieve one listing via GET /v1/listings/{id}?includeResources=1. House rules, check-in hours (0–23), amenityId values, and photos are included. wifiPassword, door codes, and invoicing contacts are stripped.

• inbox_triage

  Unanswered / SLA view Hostaway's inbox does not compute. A thread is unanswered when the latest message is incoming (or hasUnreadMessages with no later host reply). Default SLA is 2 hours. Does not send replies.

• list_conversations

  List inbox threads via GET /v1/conversations?includeResources=1. Nested Reservation objects are denylist-stripped.

• list_listings

  List Hostaway listings. Defaults to GET /v1/listings?specialStatus[]=active. Optional availabilityDateStart/End + availabilityGuestNumber filter the list the same way Hostaway does. Amenities are amenityId values, not free-text names. Check-in/out hours are 0–23. Denylisted access and invoicing fields are stripped.

• list_messages

  List messages in a thread via GET /v1/conversations/{id}/messages. Read-only. There is no send tool.

• list_reservations

  List reservations via GET /v1/reservations. Read-only. doorCode / doorCodeVendor / doorCodeInstruction are stripped. Create reservation is not implemented.

• report_completeness

  Listing completeness from reads: missing photos, missing house rules, missing amenities (empty listingAmenities). Not a financial report.

• report_inbox

  Unanswered thread counts by listing, computed from conversation reads. Not a Hostaway owner statement.

• report_occupancy

  Occupancy and blocked holes computed from calendar reads. Occupancy = reserved nights / (reserved + available). Blocked holes are consecutive blocked/hardBlock days. Not an owner statement. No financials.

• Code scan21 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 21 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

hostaway-kit: common questions

Is hostaway-kit MCP server safe?

Yes, by our scan: it is graded A (85/100). Read the hostaway-kit safety report

How do I install hostaway-kit?

It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.

Does hostaway-kit need an API key?

Yes. The registry entry asks for HOSTAWAY_CLIENT_SECRET.

Is hostaway-kit maintained?

The last commit was 21 days ago (2026-08-31). The latest release is v1.0.1.

What can I use instead of hostaway-kit?

Servers from other publishers that do the same job: Workspace MCP server, Atomic Mail MCP server and Google Workspace MCP server. Compare all hostaway-kit alternatives.