Skip to main content
Glama
buildwithmanag

OwnerRez MCP Server

by buildwithmanag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to OwnerRez MCP Server

No user-submitted related servers found.

    Related Servers

    • OwnerRez MCP Server

      jgonzalez007
      A
      license
      A
      quality
      B
      maintenance
      Connects OwnerRez property management data to MCP clients, enabling natural-language queries about bookings, check-ins, guest messaging, expenses, and webhooks.
      18
      MIT

    • 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

    • Rizerve MCP Server

      panoskiriakopoulos-sys
      F
      license
      A
      quality
      D
      maintenance
      MCP server for the Rizerve direct booking platform. Enables managing properties, bookings, availability, iCal sync, analytics, and webhooks through AI assistants.
      19
      1
      -

    • actual-mcp

      s-stefanov
      A
      license
      B
      quality
      B
      maintenance
      MCP server for integrating Actual Budget with Claude and other LLM assistants.
      17
      535 npm
      247
      TypeScript
      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

    B3.4/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target distinct resources/actions, but the message-related tools (list_messages, list_open_messages, get_message_event, mark_message_handled) could be confused without careful reading. Overall, descriptions clarify the boundaries well.

    Naming Consistency4/5

    The dominant pattern is verb_noun (list_*, get_*, create_*, delete_*, send_*), but 'who_is_staying' and 'find_guest' break the pattern. The inconsistency is minor and doesn't hinder readability.

    Tool Count4/5

    At 18 tools, the set is slightly above the typical range but justified by the domain's breadth (owners, bookings, guests, quotes, payments, messages, webhooks). Each tool serves a clear purpose, though a few could be consolidated.

    Completeness3/5

    The set covers read and monitoring operations thoroughly, plus message handling and webhook management. However, it lacks booking lifecycle operations (create, update, cancel) and property/owner mutations, which are notable gaps for a property management server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources