mcpbeat Sign in

OwnerRez MCP by usefulapi MCP Server

answering

OwnerRez MCP by usefulapi is answering right now. Last checked 2 min ago. It exposes 25 tools. Last commit 10 Oct 2026.

Manage OwnerRez properties, bookings, guests, quotes and inquiries.

Uptime history 13 days of history
13 days agonow
100.0%
Uptime 24h
92 of 92 checks
25
Tools
read from the server
91 ms
Response time
average over 24h
0
Stars
last commit 10 Oct 2026

What changed 8

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 September 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day
7 Oct a tool changed version
1 Oct a tool changed version
30 Sep a tool changed version2 times that day
and 4 more, back to 30 September 2026

Nothing serious here today

Today is the operative word: we check OwnerRez MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add ownerrez --transport http https://ownerrez.usefulapi.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ownerrez": {
      "url": "https://ownerrez.usefulapi.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ownerrez]
url = "https://ownerrez.usefulapi.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ownerrez": {
      "url": "https://ownerrez.usefulapi.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ownerrez": {
      "url": "https://ownerrez.usefulapi.io/mcp"
    }
  }
}

Available tools 25

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

booking
create_booking
MUTATES OwnerRez data: creates a new booking (reservation). OwnerRez API: POST /v2/bookings (JSON). A booking ties a guest to a property for a date range; the exact charge/quote shape is account-specific, so pass extra documented fields via `fields`. Returns the created booking.
get_booking
Fetch a single booking by id. OwnerRez API: GET /v2/bookings/{id}. Opt into embedded charges/guest/tags.
update_booking
MUTATES OwnerRez data: updates an existing booking. OwnerRez API: PATCH /v2/bookings/{id} (JSON — only included fields change). Use the `fields` passthrough for any documented field (dates, guest counts, notes, status).
guest
create_guest
MUTATES OwnerRez data: creates a new guest (contact). OwnerRez API: POST /v2/guests (JSON). Emails/phones/addresses are arrays of objects — pass them via the `fields` passthrough (e.g. email_addresses:[{address:"[email protected]"}]). Returns the created guest.
get_guest
Fetch a single guest (contact) by id. OwnerRez API: GET /v2/guests/{id}.
update_guest
MUTATES OwnerRez data: updates an existing guest. OwnerRez API: PATCH /v2/guests/{id} (JSON — only included fields change). Use the `fields` passthrough for arrays (email_addresses/phones/addresses) and any other documented field.
listing
get_listing
Fetch a single channel listing by id. OwnerRez API: GET /v2/listings/{id}.
list_listing_sites
List the listing sites (channels, e.g. Airbnb, Vrbo) known to OwnerRez. OwnerRez API: GET /v2/listingsites.
quote
create_quote
MUTATES OwnerRez data: creates a quote for a property + date range (the pre-booking pricing document). OwnerRez API: POST /v2/quotes (JSON). The full quote/charge shape is account-specific — pass extra documented fields via `fields`. Returns the created quote.
get_quote
Fetch a single quote by id. OwnerRez API: GET /v2/quotes/{id}.
bookings
list_bookings
List bookings (reservations). OwnerRez API: GET /v2/bookings. Filter by property, date range, changed-since, and status; opt into embedded charges/guest/tags. Returns { items, count, limit, offset, next_page_url }.
field
list_field_definitions
List custom-field definitions available in the account (the schema for custom fields on properties/bookings/guests). OwnerRez API: GET /v2/fielddefinitions.
get
get_me
Return the authenticated OwnerRez user (verifies your credentials). OwnerRez API: GET /v2/users/me.
guests
list_guests
List guests (contacts). OwnerRez API: GET /v2/guests. NOTE: OwnerRez REQUIRES either `q` (search) or `created_since_utc` on this endpoint. Returns { items, count, limit, offset, next_page_url }.
inquiries
list_inquiries
List guest inquiries (pre-booking leads). OwnerRez API: GET /v2/inquiries. Use `params` for documented filters.
listings
list_listings
List channel listings (a property's presence on a listing site such as Airbnb/Vrbo). OwnerRez API: GET /v2/listings. Returns { items, count, limit, offset, next_page_url }.
message
create_message
MUTATES OwnerRez data: posts a message into a guest-communication thread. OwnerRez API: POST /v2/messages (JSON). The exact thread/booking linkage is account-specific — pass extra documented fields (e.g. thread_id, booking_id) via `fields`. Returns the created message.
messages
list_messages
List messages from guest-communication threads. OwnerRez API: GET /v2/messages. Use `params` for documented filters (e.g. booking_id).
ownerrez
ownerrez_request
Power-user escape hatch: GET any OwnerRez API path not wrapped by a dedicated tool. READ-ONLY — only GET is allowed. Pass the FULL API path after the host, starting with a slash, INCLUDING any query string, e.g. "/v2/propertysearch?query=beach" or "/v2/bookings/123". Returns the parsed JSON.
owners
list_owners
List property owners. OwnerRez API: GET /v2/owners. Returns { items, count, limit, offset, next_page_url }.
payment
get_payment
Fetch a single payment by id. OwnerRez API: GET /v2/payments/{id}.
payments
list_payments
List payments. OwnerRez API: GET /v2/payments. Use `params` for documented filters (e.g. booking_id, since_utc).
properties
list_properties
List rental properties. OwnerRez API: GET /v2/properties. Returns the pageable envelope { items, count, limit, offset, next_page_url }.
property
get_property
Fetch a single property by id (includes time_zone). OwnerRez API: GET /v2/properties/{id}.
quotes
list_quotes
List quotes. OwnerRez API: GET /v2/quotes. Returns { items, count, limit, offset, next_page_url }. Use the `params` passthrough for documented filters (e.g. property_id, guest_id).

Endpoints

URLTransportStateLatencyChecked
https://ownerrez.usefulapi.io/mcp streamable-http answering 68 ms 2 min ago

Alternatives to OwnerRez MCP by usefulapi

same job, measured the same way
Hostfully MCP by usefulapi
by usefulapi

Check properties, calendars, leads, quotes, guests and messages in Hostfully, and send replies.

20 tools answering
Invoice Ninja MCP by usefulapi
by usefulapi

Manage Invoice Ninja clients, invoices, quotes, expenses, tasks and projects.

24 tools answering
Beds24 MCP by usefulapi
by usefulapi

Check bookings, quote stays, read guest messages and reviews, and update calendars in Beds24.

18 tools answering
Buildium MCP by usefulapi
by usefulapi

Read Buildium properties, units, leases, tenants, balances and bills; manage work orders.

23 tools answering
Checkfront MCP by usefulapi
by usefulapi

Check Checkfront availability and rates, and manage booking sessions, bookings, customers and notes.

20 tools answering
Persona MCP by usefulapi
by usefulapi

Read Persona inquiries, accounts, verifications and reports.

14 tools answering
Bookeo MCP by usefulapi
by usefulapi

Check Bookeo availability and manage bookings, holds and customers; read payments.

21 tools answering
All Quiet MCP by usefulapi
by usefulapi

Manage incidents and on-call: list/create/update incidents, who is on call, on-call overrides.

11 tools answering

OwnerRez MCP by usefulapi — questions

Answers built from our own checks of this server.

What can OwnerRez MCP by usefulapi do?
It exposes 25 tools, read directly from the server on our last check. Among them: create_booking, create_guest, create_message, create_quote, get_booking, get_guest and 19 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is OwnerRez MCP by usefulapi mostly used for?
Its tools cluster around guest, booking and listing. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is OwnerRez MCP by usefulapi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 91 ms. The bar chart above shows every period we have measured.
How do I connect OwnerRez MCP by usefulapi?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does OwnerRez MCP by usefulapi need an API key?
No. OwnerRez MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 25 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is OwnerRez MCP by usefulapi?
It answers our handshake in 91 ms on average, which is faster than 87% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is OwnerRez MCP by usefulapi open source?
Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.