OwnerRez MCP by usefulapi

Most tools are cleanly separated by resource + action (bookings, guests, quotes, payments, properties, listings), and descriptions clarify subtle neighbors like list_listings vs list_listing_sites vs list_properties. The only real overlap is ownerrez_request, a generic GET escape hatch that can duplicate any dedicated get/list tool, though it is explicitly framed as a fallback for unwrapped paths.

Every tool uses the same ownerrez_ prefix plus a snake_case verb_noun pattern (create_/get_/list_/update_ + resource), with pluralization handled predictably. The lone outlier, ownerrez_request, is an intentional escape hatch rather than an inconsistency; a caller can reliably guess names.

At 25 tools this sits at the top of the 'heavy' band, driven by the domain's breadth (bookings, guests, quotes, messages, payments, listings, properties, owners, inquiries, field definitions). Each tool maps to a distinct endpoint, but the four-per-resource create/get/list/update repetition inflates the surface more than necessary.

Read coverage is broad and write coverage spans create/get/list/update for the core entities (bookings, guests, quotes, messages), which covers the main workflows. Gaps remain: no delete anywhere, no create/update for properties, owners, or payments, and no single-message fetch; the read-only escape hatch cannot fill the mutation gaps.