> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wat.com/llms.txt
> Use this file to discover all available pages before exploring further.

# WAT Rooms

> Book WAT meeting rooms in seconds, from the web app, the terminal, or your AI coding agent.

WAT Rooms is the booking app for the WAT community's meeting rooms. See live availability, reserve a free time slot, and manage your own bookings.

There is a web app at [app.wat.com](https://app.wat.com), but WAT Rooms is built to be driven by **AI agents**. A small `wat` CLI exposes the same API the web app uses, a skills plugin lets coding agents book rooms conversationally, and an [MCP server](/mcp-server) brings the same tools to claude.ai and Claude Desktop with zero installation.

<Note>
  **Are you an AI agent reading this?** Go straight to the [Agent playbook](/agents): a top-to-bottom recipe that needs zero installation (`npx -y @wat-toolbox/wat … --json`), scripts the login handoff with your human, and ends with a booked room.
</Note>

## Pick your path

<CardGroup cols={2}>
  <Card title="Agent playbook" icon="robot" href="/agents">
    For agents: zero-install recipe from cold start to a confirmed booking.
  </Card>

  <Card title="Quickstart" icon="wand-sparkles" href="/quickstart">
    For humans: set up the CLI and skills once, then book in natural language.
  </Card>

  <Card title="Create an account" icon="user-plus" href="/account">
    Self-enroll with your company email — recognised automatically. Passwordless.
  </Card>

  <Card title="The wat CLI" icon="terminal" href="/cli">
    Install the CLI and the full command reference: rooms, availability, bookings.
  </Card>

  <Card title="Skills plugin" icon="puzzle" href="/plugin">
    The four `wat:` skills your agent uses to book rooms in plain language.
  </Card>

  <Card title="MCP server" icon="plug" href="/mcp-server">
    Zero-install: connect claude.ai or Claude Desktop to one URL and book from chat.
  </Card>

  <Card title="Booking rules" icon="book-open" href="/booking-rules">
    Durations, opening hours, the daily budget, the booking horizon, and privacy.
  </Card>
</CardGroup>

## How it fits together

One account works everywhere. You sign up once in the web app, mint an API key, and the same identity drives the web app, the `wat` CLI, and the skills plugin.

* **Web app:** a calendar with a day view (one column per room) and a week view (one room across Monday to Sunday), point and click to book.
* **`wat` CLI:** book from the terminal, scriptable, machine-readable with `--json`.
* **Skills plugin:** thin wrappers over the CLI so an agent can book for you in natural language.

The CLI and the skills call the **same** public API the web app uses, so every rule (availability, your daily budget, privacy) is enforced identically no matter how you book.