Hostaway

io.github.uncfreak1255-codePublished by GitHub account uncfreak1255-codev0.2.0Updated Oct 24, 2026

Read-only MCP server for Hostaway PMS — guest conversations, reservations, and listings

VerifiedSTDIODesktop onlyProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Read-only MCP server for Hostaway property management: guest conversations, reservations, and listings.

What you can do
Exposes six read-only tools over the Hostaway PMS API: list_unread_guest_threads, get_conversation_context, get_reservation_brief, get_listing_brief, search_reservations, and search_conversations. It is hospitality-shaped rather than a raw endpoint proxy, aimed at conversation context, reservation lookup, and listing lookup. It does not send guest messages or change reservations or listings.
When to use it
Use it when an assistant needs to look up Hostaway reservations, listings, or guest conversation context without hand-wiring raw API calls. It suits read-only triage and lookup workflows, not messaging or data changes.
Requirements
Runs locally over stdio, typically via npx hostaway-mcp or a built CLI. Requires Node.js and a Hostaway API token supplied in the HOSTAWAY_API_TOKEN environment variable. An optional HOSTAWAY_BASE_URL variable can override the API base URL. Network access to the Hostaway API is needed.
Before you install
The server requires the HOSTAWAY_API_TOKEN secret, which grants access to Hostaway account data; keep it out of shared config files and version control. It is read-only by design, so it does not send messages or modify reservations or listings, but the data it reads is sent to the assistant and its model provider.

Installation

In SourceWeft

  1. Open Hostaway in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

hostaway-mcp

Read-only, hospitality-shaped MCP server for Hostaway.

This repo owns the operator product only: local/npm stdio, six read-only tools, no Cloudflare Worker, and no Seascape booking surface.

V1 Goal

Make Codex and Claude useful in real Hostaway workflows without hand-wiring raw API calls every time.

V1 is intentionally narrow:

  • read-only only
  • hospitality-native tools, not raw endpoint parity
  • optimized for conversation context, reservation lookup, and listing lookup

Exact V1 Surface

  • list_unread_guest_threads
  • get_conversation_context
  • get_reservation_brief
  • get_listing_brief
  • search_reservations
  • search_conversations

Local Development

bash
npm installnpm testnpm run checknpm run build

Run the stdio server locally:

bash
HOSTAWAY_API_TOKEN=your-token-here node dist/cli.js

Create a local npm package tarball:

bash
npm pack

After publish, run without cloning:

bash
npx hostaway-mcp

MCP Client Wiring

For local MCP clients, provide HOSTAWAY_API_TOKEN through the environment and spawn the published npm package over stdio.

The snippets below are pinned to the current published version:

text
[email protected]

Update that version intentionally when you upgrade.

Claude Desktop (macOS)

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

If you already have top-level keys like preferences, keep them and add mcpServers alongside them:

json
{  "mcpServers": {    "hostaway": {      "command": "npx",      "args": ["-y", "[email protected]"],      "env": {        "HOSTAWAY_API_TOKEN": "your-token-here"      }    }  }}

Restart Claude Desktop after saving the file.

Codex

Edit ~/.codex/config.toml and add:

toml
[mcp_servers.hostaway]command = "npx"args = ["-y", "[email protected]"]
[mcp_servers.hostaway.env]HOSTAWAY_API_TOKEN = "your-token-here"

Verify the server is registered:

bash
codex mcp list

Local Built CLI

If you want to run the repo checkout instead of npm, point the client at the built CLI directly:

json
{  "command": "node",  "args": ["/absolute/path/to/hostaway-mcp/dist/cli.js"],  "env": {    "HOSTAWAY_API_TOKEN": "your-token-here"  }}

Environment Variables

VariableRequiredDefaultDescription
HOSTAWAY_API_TOKENYes—Hostaway API token used to authenticate all requests.
HOSTAWAY_BASE_URLNoHostaway production URLOverride the API base URL (useful for testing).

V1 Non-Goals

  • sending guest messages
  • mutating reservations or listings
  • Cloudflare Worker transport
  • Seascape booking/distribution flows
  • webhook ingestion
  • background sync pipelines
  • dashboards or owner reporting
  • generic REST-to-MCP proxy coverage

Source Design

See docs/designs/v1-readonly-hostaway-mcp.md.

Source: README.md at commit 7708f14

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts