Skip to main content
Glama
jgonzalez007

OwnerRez MCP Server

by jgonzalez007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to OwnerRez MCP Server

No user-submitted related servers found.

    Related Servers

    • OwnerRez MCP connector

      gcwharton-a11y
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to read and act on your OwnerRez account—bookings, properties, guests, financials, and guest messaging—through a secured remote MCP endpoint.
      MIT

    • OwnerRez MCP Server

      palarkin
      F
      license
      A
      quality
      B
      maintenance
      Enables Claude to interact with your OwnerRez account via natural language, including booking inquiries, income summaries, property stats, and owner statements. Supports optional guest messaging with OAuth setup.
      21
      1
      -

    • Rentvine MCP

      Rentor-CA
      A
      license
      A
      quality
      B
      maintenance
      Provides Claude and any MCP client with live access to property management data, enabling operations on properties, units, leases, tenants, work orders, vendors, accounting, and file attachments through natural language.
      25
      MIT

    • realtycalendar-mcp

      ilyautov
      A
      license
      Not graded
      quality
      F
      maintenance
      Connects AI agents to RealtyCalendar accounts, allowing users to query bookings, availability, and check-ins via natural language, with local-first privacy and read-only access.
      MIT

    • Hostaway MCP

      uncfreak1255-code
      A
      license
      B
      quality
      B
      maintenance
      A read-only hospitality-focused MCP server that enables users to retrieve reservation details, listing briefs, and guest conversation contexts from Hostaway. It simplifies hospitality workflows by providing specialized tools for searching threads and viewing reservation data through natural language interfaces.
      6
      44 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action: webhook subscription lifecycle, booking reads, current-stay snapshot, property/owner/guest lookups, financial lists, and message inbox/thread operations. The only potentially close pair is list_messages vs list_open_messages, but they are clearly separated by conversation thread vs webhook inbox.

    Naming Consistency4/5

    Most tools follow a verb_noun snake_case pattern (list_bookings, get_booking, create_webhook_subscription, delete_webhook_subscription). Minor deviations like who_is_staying and mark_message_handled break the strict noun-object pattern, and find_guest is singular while list_* tools are plural.

    Tool Count4/5

    18 tools is on the high side but each maps to a meaningful OwnerRez domain area (bookings, properties, guests, messages, payments, webhooks). It feels slightly broad rather than bloated, and no obvious redundancy inflates the count.

    Completeness3/5

    The set covers read-side lookup and the webhook-driven message inbox workflow well, including create/delete subscriptions and send/mark-handled. However, it lacks write/update operations for core entities such as bookings, quotes, payments, and guests, and there is no property/guest detail retrieval beyond lists, so full lifecycle tasks would dead-end.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources