Office Booking MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CAB_AUTH_TOKEN | Yes | Authorization token for the cab booking API. | |
| CAB_API_BASE_URL | Yes | Base URL for the cab booking API, captured from your company's app. | |
| LUNCH_AUTH_TOKEN | Yes | Authorization token for the lunch booking API. | |
| OFFICE_MCP_DEBUG | No | Set to 'true' to enable debug logging (optional). | |
| LUNCH_API_BASE_URL | Yes | Base URL for the lunch booking API. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_cab_bookingsA | List your current and upcoming office cab bookings. |
| book_cabA | Book an office cab. Args: pickup: Pickup location (address or saved place name). drop: Drop-off location. when: When the cab is needed, ISO 8601 e.g. "2026-06-18T09:30:00". notes: Optional note for the driver/admin. |
| cancel_cabA | Cancel an office cab booking. Args:
booking_id: The id of the trip to cancel (from |
| list_lunch_bookingsA | List your current and upcoming office lunch bookings. |
| book_lunchB | Book office lunch for a date. Args: date: Slot date as DD-MM-YYYY, e.g. "23-06-2026". time: Slot time as HH:MM (defaults to the captured slot time). food_id: Optional item id to order; if empty, books the template's item. food_name: Optional human-readable name for that item. price: Optional unit price for that item (0 = keep template price). veg: Whether the item is vegetarian. quantity: Number of units (default 1). |
| cancel_lunchA | Cancel an office lunch booking. Args:
booking_id: The id of the lunch order to cancel (from |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct resource (cab or lunch) and action (book, cancel, list), with no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (e.g., book_cab, cancel_lunch), making them predictable and easy to understand.
With 6 tools covering two services with three operations each, the count is well-scoped and appropriate for the domain.
The set covers create, cancel, and list for both services, but lacks update/modify functionality, requiring users to cancel and rebook for changes, which is a notable gap.