cabinquote
README.md
# cabinquote
Planning a stay at one particular Swedish holiday home, without submitting anything. cabinquote is a local forwarding client for the hosted Lilla Alva MCP service: it answers `tools/list` on your own machine from the captured tool definitions and forwards every read to the service, returning the answers exactly as they come back.
Everything here is a published read. You can pull up the home's description, amenities, house rules and contact details, check which date ranges are blocked and whether a specific stay is free, and get a price breakdown in EUR for a set of dates and a guest count. A quote is only a calculation — dates and counts go upstream, no name, no email, and nothing is booked or requested by any tool in this package.
## The tools
- **`get_property_info`** — Description, amenities, house rules, booking flow and contact details for Lilla Alva, a holiday home in Varmland, Sweden. Takes no arguments.
- **`check_availability`** — Which date ranges are blocked from today onward. With both `check_in` and `check_out` (YYYY-MM-DD) it also says whether that stay is available. Ranges are all-day and end-exclusive, so a new stay may begin on another booking's check-out day. Both arguments are optional.
- **`get_quote`** — A price breakdown in EUR: date-dependent nightly rates, the mandatory cleaning fee, and optional add-ons (bed linens and towels per person, Hot Tub Service per stay, a one-time dog fee). `check_in`, `check_out` and `number_of_guests` (1–6) are required; `number_of_dogs` (0–3), `bed_linens` and `hot_tub` are optional.
One upstream tool is deliberately not included: the booking-request tool, which would submit a guest's real name and email address to the property owner. It is not registered, not served over MCP, and has no CLI subcommand.
## Install and run
As an MCP server via npm:
```bash
npx -y @reneturcios/cabinquote mcp
```
MCP client configuration:
```json
{
"mcpServers": {
"cabinquote": {
"command": "npx",
"args": ["-y", "@reneturcios/cabinquote", "mcp"]
}
}
}
```
As a container:
```bash
docker run -i ghcr.io/cloudcorprecords/cabinquote
docker run --rm ghcr.io/cloudcorprecords/cabinquote get_property_info '{}'
```
## CLI
One binary serves both the command line and the MCP server. Each tool is a subcommand taking a single JSON string with that tool's arguments:
```bash
cabinquote get_property_info '{}'
cabinquote check_availability '{}'
cabinquote check_availability '{"check_in":"2026-07-03","check_out":"2026-07-10"}'
cabinquote get_quote '{"check_in":"2026-07-03","check_out":"2026-07-10","number_of_guests":4}'
cabinquote get_quote '{"check_in":"2026-07-03","check_out":"2026-07-10","number_of_guests":2,"number_of_dogs":1,"bed_linens":true,"hot_tub":true}'
cabinquote --version
```
Exit codes: `0` when the forwarded call succeeds, `1` when the upstream result is an error, and `2` for usage problems such as an unknown subcommand or a malformed JSON argument.
## Configuration
- `LILLA_ALVA_MCP_URL` — Overrides the upstream endpoint. The default is the pinned hosted endpoint, `https://lilla-alva.com/api/mcp`. (The override variable is a reconstruction added by this rebuild.)
The Lilla Alva registry record declares no headers on its remote, so cabinquote sends no authentication header of any kind — the reads are keyless.
Upstream failures — a JSON-RPC error from the service, a non-2xx response, an unreadable body, or a request that fails outright — are reported to the caller as an error result whose text starts with `cabinquote error:`.
## How forwarding works
The first forwarded call opens a session: an `initialize` request (protocol version `2025-03-26`), followed by a `notifications/initialized` notification, then the `tools/call` itself. If the service answers the initialize request with an `Mcp-Session-Id` header, that value is carried on every later request, and the open session is reused for the rest of the process. Replies are accepted either as plain JSON or as server-sent events. Successful results pass through verbatim, including any `isError` flag and any extra fields the service includes.
## Development
```bash
npm install
npm run build # tsc -> dist/ (dist/cli.js is the bin)
npm test # tsx --test test/*.test.ts — stubbed upstream, no network
npm run dev # run the CLI from source
```
The test suite checks the served tool list against the captured subset, asserts the omitted booking-request tool is absent at registry, MCP and CLI level, exercises the session handshake and its reuse, asserts that no `Authorization` header is sent under any environment, and verifies that arguments go upstream untouched and results come back untouched.
## License
MIT — see `LICENSE`. Copyright (c) 2026 Rene Turcios.
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues