Manage OwnerRez properties, bookings, guests, quotes and inquiries. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"ownerrez": {
"url": "https://ownerrez.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"ownerrez": {
"type": "http",
"url": "https://ownerrez.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your OwnerRez Personal Access Token and OwnerRez login email.
Create a Personal Access Token in OwnerRez → Settings → API Access. Pair it with the login email that owns it.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your OwnerRez Personal Access Token and OwnerRez login email. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the OwnerRez connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
get_me | read | Get current user Return the authenticated OwnerRez user (verifies your credentials). OwnerRez API: GET /v2/users/me. |
list_properties | read | List properties List rental properties. OwnerRez API: GET /v2/properties. Returns the pageable envelope { items, count, limit, offset, next_page_url }. |
get_property | read | Get a property Fetch a single property by id (includes time_zone). OwnerRez API: GET /v2/properties/{id}. |
list_bookings | read | 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 }. |
get_booking | read | Get a booking Fetch a single booking by id. OwnerRez API: GET /v2/bookings/{id}. Opt into embedded charges/guest/tags. |
list_guests | read | 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 }. |
get_guest | read | Get a guest Fetch a single guest (contact) by id. OwnerRez API: GET /v2/guests/{id}. |
list_quotes | read | 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). |
get_quote | read | Get a quote Fetch a single quote by id. OwnerRez API: GET /v2/quotes/{id}. |
list_listings | read | 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 }. |
get_listing | read | Get a listing Fetch a single channel listing by id. OwnerRez API: GET /v2/listings/{id}. |
list_listing_sites | read | List listing sites List the listing sites (channels, e.g. Airbnb, Vrbo) known to OwnerRez. OwnerRez API: GET /v2/listingsites. |
list_owners | read | List owners List property owners. OwnerRez API: GET /v2/owners. Returns { items, count, limit, offset, next_page_url }. |
list_inquiries | read | List inquiries List guest inquiries (pre-booking leads). OwnerRez API: GET /v2/inquiries. Use `params` for documented filters. |
list_messages | read | List messages List messages from guest-communication threads. OwnerRez API: GET /v2/messages. Use `params` for documented filters (e.g. booking_id). |
list_payments | read | List payments List payments. OwnerRez API: GET /v2/payments. Use `params` for documented filters (e.g. booking_id, since_utc). |
get_payment | read | Get a payment Fetch a single payment by id. OwnerRez API: GET /v2/payments/{id}. |
list_field_definitions | read | List custom-field definitions List custom-field definitions available in the account (the schema for custom fields on properties/bookings/guests). OwnerRez API: GET /v2/fielddefinitions. |
ownerrez_request | read | Raw read 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. |
create_guest | write | Create a 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. |
update_guest | write | Update a 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. |
create_booking | write | Create a 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. |
update_booking | write | Update a 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). |
create_quote | write | Create a 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. |
create_message | write | Create a 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. |
ownerrez_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
ownerrez_request_feature | Request a missing feature Tell usefulapi that the user needs something the OwnerRez tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
ownerrez_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED OwnerRez tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
ownerrez_cancel_subscription | Cancel the Pro subscription Cancel the caller's OwnerRez Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run ownerrez_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Pro | $9/mo · $90/yr | Unlimited |
Pro covers this OwnerRez server only. Subscribe with ownerrez_upgrade (it returns a Stripe Checkout link). Cancel any time with ownerrez_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running ownerrez_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by OwnerRez. The server calls the OwnerRez API with your own OwnerRez access, so it sees only the data that your account can see.
The login page asks for your OwnerRez Personal Access Token and OwnerRez login email. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your OwnerRez Personal Access Token and OwnerRez login email. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the OwnerRez API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in OwnerRez.
Yes, if you approve it. 6 of the 25 OwnerRez tools can create or change data. The other 19 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this OwnerRez server only. Run ownerrez_usage_status to see how many calls you used.
Ask the AI to run ownerrez_upgrade: it returns a Stripe Checkout link. To cancel, run ownerrez_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with ownerrez_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.