smoobu-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SMOOBU_API_KEY | Yes | Your Smoobu API key (Smoobu: Settings > Advanced > API Keys) | |
| SMOOBU_API_SECRET | Yes | Your Smoobu API secret (Smoobu: Settings > Advanced > API Keys) |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_propertiesA | The 14 properties with Smoobu id, name, EOM entity (KALAWALA/NAMAITAMI/RIBHOLDING/DELFINES/PERLA) and fiscal company / bsides account. Casa 4 Modern = PERLA. With include_live=true also reports unmapped live apartments. |
| get_bookingsA | Bookings arriving between arrival_from and arrival_to (both INCLUSIVE), or in |
| get_bookingB | Full detail of one booking by id: normalized row, price elements (Other Fees = 13% IVA, Host Fee = commission, Payout), created_at / modified_at and the raw Smoobu object for audit. |
| changes_sinceA | For an arrival month: new, modified (field-level old -> new, incl. price and dates), cancelled and disappeared bookings compared with the snapshot taken at or before |
| stays_in_monthA | Every booking overlapping the month with nights inside the month and pro-rated revenue, totalled per property, per portal and per entity. Reproduces Smoobu Analytics' convention so the extraction can be verified without reading the screen. |
| smoobu_healthA | Checks each configured account: auth mode, Smoobu user, live apartment count, rate-limit status. Never returns keys. |
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
Most tools have distinct purposes: list_properties, get_booking (by id), changes_since, and smoobu_health are clearly separable. The main soft spot is get_bookings vs stays_in_month, which both target bookings within a month but differ by arrival-window vs overlap/pro-rated revenue convention; descriptions do enough to disambiguate but an agent could still hesitate.
All names use snake_case consistently, and list_properties/get_bookings/get_booking follow a clean verb_noun pattern. changes_since, stays_in_month, and smoobu_health deviate into noun/prepositional phrasing, which is a minor inconsistency but still readable and predictable enough.
Six tools is well-scoped for a booking extraction/audit server; each tool covers a distinct operation (enumerate properties, query bookings, fetch detail, diff changes, monthly analytics, health check). Nothing feels redundant or padded.
For a read-only extraction/reporting surface, coverage is good: properties, ranged and per-booking retrieval, change detection, monthly revenue analytics, and account health are all present with no obvious dead ends. Write/update operations are absent, but that appears intentional for this audit-oriented domain.