About hostaway
hostaway is a read-only MCP server for Hostaway, aimed at hospitality operators who need guest conversation, reservation, and listing data. Its six tools are shaped around hospitality workflows rather than mirroring raw API endpoints.
Key features
- 01List unread guest threads
- 02Retrieve conversation context
- 03Look up reservation briefs
- 04Look up listing briefs
- 05Search reservations and conversations
Use cases
- 01Review unread guest messages
- 02Gather context for guest conversations
- 03Find reservation or listing details
MCP support
The server exposes six read-only tools to MCP clients over stdio. Clients provide a Hostaway API token through an environment variable.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y hostaway-mcpHOSTAWAY_API_TOKENSecretHostaway API token used to authenticate all requestsLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
6Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| limit | integer | No | |
| messageLimit | integer | No |
Details
From the project READMEhostaway-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_threadsget_conversation_contextget_reservation_briefget_listing_briefsearch_reservationssearch_conversations
Local Development
npm install
npm test
npm run check
npm run build
Run the stdio server locally:
HOSTAWAY_API_TOKEN=your-token-here node dist/cli.js
Create a local npm package tarball:
npm pack
After publish, run without cloning:
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:
[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:
{
"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:
[mcp_servers.hostaway]
command = "npx"
args = ["-y", "[email protected]"]
[mcp_servers.hostaway.env]
HOSTAWAY_API_TOKEN = "your-token-here"
Verify the server is registered:
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:
{
"command": "node",
"args": ["/absolute/path/to/hostaway-mcp/dist/cli.js"],
"env": {
"HOSTAWAY_API_TOKEN": "your-token-here"
}
}
Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
HOSTAWAY_API_TOKEN | Yes | — | Hostaway API token used to authenticate all requests. |
HOSTAWAY_BASE_URL | No | Hostaway production URL | Override 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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.