You cannot connect LiveRez to Claude with an API integration or an MCP server. LiveRez describes an open API, but access runs through its partner Integration Marketplace, there is no public developer documentation or self-serve API key, and no LiveRez MCP server exists as of July 2026. More importantly, Inhabit announced on September 23, 2025 that LiveRez is being consolidated into Streamline, with support extending through July 2026. The route that works, and the one worth doing this month regardless of Claude, is exporting your reservation, owner statement, financial, and housekeeping reports out of LiveRez and analyzing the files with Claude. That workflow needs nothing from LiveRez except the reports it already produces.
The integration reality, in one table
Before you spend an evening hunting for a developer portal that does not exist, here is where every path stands.
Why the clock matters: the LiveRez sunset
LiveRez spent years as one of the most-installed platforms among established vacation rental managers. In the VRMA member data RapidEye analyzed for its state-by-state landscape series, LiveRez was the third most-named PMS, chosen by 87 of the 923 companies that named one (9.4%), behind only Streamline and the legacy HomeAway Software products. That installed base is exactly who is affected by what happens next.
LiveRez is acquired
Greater Sum Ventures acquires LiveRez, with Vista Point Advisors advising the sale. LiveRez becomes part of the portfolio that operates as Inhabit, alongside Streamline, VRM, and later LMPM.
Inhabit announces consolidation into Streamline
Inhabit announces it is uniting LiveRez, LMPM, and VRM under the Streamline platform, promising "dedicated migration specialists, personalized onboarding plans, and comprehensive training resources" for migrating customers.
Transition window closes
Per the announcement, LiveRez "will remain supported during the transition period, which extends through July 2026," with client migrations in phases. Legacy platforms receive essential maintenance but no new features. If you still have LiveRez access, your export window is now.
The export manifest: what to pull while you still can
This is the part of the guide that matters even if you never open Claude. Migrations carry forward-looking operational data well; deep reporting history is what tends to thin out. Before your LiveRez access ends, export each of these to files you control:
Reservation history
Every booking you can reach: dates, property, guest, channel, rate, fees, cancellations. This is the backbone for any future-year comparison.
Owner statements
Statements for every owner, every period you might ever need to defend. Owners ask questions years later; your answers live in these files.
Trust accounting and financials
Trust ledgers, revenue reports, fee breakdowns, tax summaries. Regulators and CPAs do not accept "it was in the old system."
Guest database
Contact details, stay history, notes. Your repeat-guest list is one of the few assets that transfers cleanly to any future stack.
Housekeeping and work orders
Cleans, inspections, maintenance tickets, vendor assignments. The history that shows which units eat your ops budget.
Property setup
Rates, fees, policies, amenities, descriptions per unit. You will re-enter this somewhere; exporting it now makes that a paste, not a memory test.
LiveRez's knowledge base lives behind its Partner Hub login, so we cannot link you to specific report screens. The rule of thumb: anything LiveRez will render as a report, run it at the widest date range it allows and save the file. CSV or Excel where offered, PDF where not. Claude reads all three.
The workflow: LiveRez exports into Claude
Build a LiveRez archive folder
Create one folder, for example LiveRez Archive 2026, with subfolders per category from the manifest above. Name files so a stranger could parse them: owner-statements-2025-smith.pdf, reservations-2019-2026.csv. Claude handles messy files fine, but consistent names make your prompts shorter and the answers more reliable.
Load the files into a Claude Project
In Claude (claude.ai on a paid plan, or Claude Desktop), create a Project called LiveRez Archive and add your exported files to its knowledge. A Project keeps the files attached to every conversation, so you are not re-uploading owner statements each time a question comes up. For one-off questions, attaching files to a single chat works too.
If your full reservation export is too large to attach, split it by year. Smaller, well-labeled files also get you more precise answers.
Ask operational questions in plain English
Claude reads the spreadsheets and PDFs directly and can compute across them. Start wide, then drill:
Run a migration audit against Streamline
This is the highest-value use of the whole exercise right now. After Inhabit migrates your account, export the same reports from Streamline and have Claude reconcile the two systems:
Checking a few thousand rows by hand is the kind of task that never actually happens. Claude does it in one pass, and catching a mis-migrated fee schedule in August beats explaining it to an owner in December. The same reconciliation habit applies beyond finances: operators who photo-document turnovers run automated checks on that stream too, which is the problem RapidEye's inspection API exists for.
What a LiveRez manager would actually ask Claude
Examples calibrated to the operator LiveRez served: an established, multi-owner professional manager.
- "Draft a plain-English summary of this owner statement I can paste into an email, including why net payout dropped from last month."Owners
- "From seven years of reservations, which two weeks should we block for deep maintenance at each property based on historically lowest occupancy?"Ops
- "Rank our units by work orders per booked night using the housekeeping export. Which three units are costing us the most per stay?"Housekeeping
- "Build a repeat-guest list: every guest with 3 or more stays, their last stay date, and total lifetime revenue."Guests
- "Compare our cancellation rate by booking channel across 2023 to 2025 and tell me if any channel is getting worse."Revenue
- "Using the trust ledger export, list every owner whose escrow balance changed by more than 20 percent last quarter and the transactions that drove it."Accounting
FAQ
Does LiveRez have a public API?
Not a self-serve one. LiveRez's own FAQ states "LiveRez has an open API, we have the ability to connect with most tools you need to run your operations," but in practice access runs through its Integration Marketplace: vendors request a call, get approved as partners, and build against it. There is no public developer portal, no published endpoint reference, and no screen in the product where a property manager can generate an API key. The sunset makes this moot anyway. Coverage of the consolidation notes legacy platforms are receiving "essential maintenance for API functionality and regulatory compliance" only, so new integration builds against LiveRez are not realistic in the time it has left.
Is there a LiveRez MCP server?
No. As of July 2026 we could find no official or community LiveRez MCP server in MCP registries or on GitHub, and given the platform is being sunset, one is very unlikely to appear. Compare that with PMS platforms investing in AI access: Hospitable and Guesty both ship official MCP servers. For LiveRez, exports are the bridge.
Is LiveRez shutting down?
As a standalone platform, yes. On September 23, 2025, Inhabit announced it is consolidating LiveRez, LMPM, and VRM into Streamline, saying the platforms "will remain supported during the transition period, which extends through July 2026." Migrations are phased, with Inhabit providing dedicated migration specialists and onboarding plans. No new features are being added to LiveRez during the transition.
Can Claude log into my LiveRez dashboard directly?
Browser-driving AI tools exist, including Anthropic's Claude for Chrome, and they can navigate web dashboards. But for financial and reservation data you want deterministic, auditable files, not a screen-scrape. Run the report, download the file, upload it. You keep the artifact, and every number Claude cites traces back to a file you can open.
What about connecting Claude after I migrate to Streamline?
Streamline also has no official MCP server as of July 2026, and its API is partner-gated behind the Partner X portal. The difference: Streamline has a future, so partner API access (yours or a vendor's) can carry a custom MCP server, and the export-and-upload workflow works for everyone in the meantime. Our Streamline guide walks through all three paths, and the Project you built in this guide becomes the "before" half of your migration audit.
Sources
- Better Together: Uniting Property Management Platforms into One Team (Streamline / Inhabit, September 23, 2025)https://www.streamlinevrs.com/blog/uniting-property-management-platforms-under-streamline/
- LiveRez: Frequently Asked Questions (open API statement)https://www.liverez.com/faq/
- LiveRez: Industry Partners and Integration Marketplacehttps://www.liverez.com/industry-partners/
- LiveRez Acquired by Greater Sum Ventures (Vista Point Advisors, 2019)https://vistapointadvisors.com/news/liverez-acquired-by-greater-sum-ventures
- RapidEye: The Vacation Rental Landscape, State by State (VRMA member PMS data)https://rapideyeinspections.com/blog/vacation-rental-landscape-by-state/
Other guides in this series
The full library of PMS and STR-stack connection guides lives at /claude-guides/.
Connect Streamline to Claude
The platform LiveRez accounts are migrating to: partner API, exports, and what an MCP build takes.
Legacy PMSConnect Escapia to Claude
The other big legacy platform in the VRMA data, and a repeatable export-to-Claude pipeline.
Dynamic pricingConnect PriceLabs to Claude
A real self-serve API, so this one gets a working read-only MCP server in 10 minutes.