The short version. There is no direct way to connect Enso Connect to Claude yet. As of July 2026, Enso Connect publishes no public developer API, no API reference, and no MCP server, official or community-built. Enso Connect is a layer that sits on top of your property management system, so the working route is to connect Claude to the PMS underneath it: Guesty, Hostaway, OwnerRez, Hostfully, or Lodgify all publish public APIs that a small MCP server can wrap in about 20 minutes. That gives Claude the reservations, guests, and properties Enso Connect itself works from. Data that lives only inside Enso Connect, like Boarding Pass engagement or upsell reports, you paste into Claude for analysis instead.
MCP, the Model Context Protocol, is an open standard from Anthropic that lets AI assistants talk to outside systems. EnsoAI, Enso Connect's built-in AI, is a different thing entirely: it answers your guests. Claude, wired into your stack, answers you. This guide covers all three routes and where each one stops.
Your three routes, ranked
Connect the PMS underneath
Enso Connect is not a PMS; it layers on top of one and syncs reservation data from it. That PMS has a public API. Run a small read-only MCP server against it and Claude sees the same bookings, guests, and properties Enso Connect does.
Works today, ~20 minPaste Enso data in
For the data that exists only inside Enso Connect, upsell reports, message threads, guidebook content, copy it out of the console and paste it into a Claude conversation or Project. Zero code, surprisingly far.
Works today, manualRequest access from Enso
Enso Connect built its whole platform around AI; a customer-facing API or MCP endpoint is a plausible future move. Ask your account manager or support@ensoconnect.com, and tell them why. Demand is how these ship.
Not available yetWhat you can ask Claude once Route 1 is live
With an MCP server wrapping your PMS, Claude reads the same reservation layer Enso Connect automates on top of:
- "Which guests check in over the next 72 hours, and which of those stays are first-time guests?"
- "Cross-reference this month's arrivals with the upsell report I'm pasting in from Enso Connect. Which properties convert early check-in best?"
- "List reservations with back-to-back turnovers this weekend so I know where check-in automation timing is tight."
- "Here are 30 guest threads EnsoAI escalated this month. Categorize the reasons and tell me what to add to our guidebook."
- "Draft Boarding Pass guidebook sections for the new listing from this house manual PDF."
The last two are Route 2: paste-ins. The first three come straight off the PMS connection.
Where EnsoAI ends and Claude begins
According to Enso Connect, EnsoAI runs in two modes: CoPilot drafts a reply to every guest message for a human to approve, and AutoPilot sends autonomously, governed by a confidence meter, with suggested responses instead of autonomous sends when its accuracy prediction drops below roughly 90 percent. Enso Connect states it translates across 200+ languages and pulls context from your guidebooks, conversation history, and PMS-connected reservation data. That is a guest-facing system, and if you run Enso Connect you should let it do that job.
Connecting Claude is about the other side of the desk:
Before you start
Route 1 needs three things: your PMS admin credentials (you will generate an API key or OAuth client in the PMS, not in Enso Connect), Node.js 18 or newer (check with node --version), and either Claude Desktop or Claude Code. Route 2 needs nothing but a Claude account.
Identify the PMS under your Enso Connect account
You already know this, it is whichever system you connected during Enso Connect onboarding. Enso Connect maintains marketplace integrations with the major PMS platforms; Guesty and Hostfully both document the pairing in their own help centers and integration pages. The key point: your reservation data's system of record is the PMS, not Enso Connect, which is why this route gets Claude the data without Enso Connect needing to expose anything.
Follow the matching MCP guide
We keep a worked, copy-paste MCP server guide for each major PMS Enso Connect pairs with. Each one is read-only by default and takes 15 to 20 minutes:
On a different PMS? The pattern is identical for any system with a public REST API; browse the full guide library for yours.
Set up a standing workspace for the Enso side
For the data that lives only in Enso Connect, the clean pattern is a dedicated Claude Project (in Claude Desktop or claude.ai) named something like Guest Experience Ops. Give it standing instructions once, then paste Enso Connect exports and threads into it as they come up:
You are the back-office analyst for a short-term rental operation
that runs Enso Connect for guest experience on top of [YOUR PMS].
When I paste guest message threads: categorize the guest's need,
flag anything EnsoAI escalated that a guidebook entry could have
answered, and suggest the guidebook addition.
When I paste upsell or engagement reports: normalize them into a
table, compare against any previous report in this project, and
call out the biggest movers with a one-line hypothesis each.
When I ask for guest-facing copy (guidebook sections, upsell
descriptions, check-in instructions): match our tone, keep it
scannable, and never invent house details I have not given you.If you also completed step 2, the same Claude account now has both halves: live PMS data through MCP tools, and Enso-side context through the project. Questions like the upsell cross-reference example above use both in one conversation.
Troubleshooting
I looked for an API key inside the Enso Connect console and can't find one
Because there isn't one to find. The API keys involved in an Enso Connect setup belong to your PMS: during onboarding, Enso Connect consumes your PMS credentials to pull reservations in. Nothing in the console issues credentials for pulling data out. Generate your key in the PMS itself (step 2's guides show exactly where for each one).
Claude sees my bookings but not my guest message threads
Expected. Messages that flow through Enso Connect's unified inbox live in Enso Connect (and partly in the source channel, like Airbnb), not in most PMS reservation APIs. That is exactly the boundary between Route 1 and Route 2: bookings and guests come through the MCP server, message content gets pasted in.
Won't Claude and EnsoAI conflict?
No, because they never touch the same surface. EnsoAI operates inside Enso Connect's inbox, messaging guests. The setup in this guide is read-only toward your PMS and has no pathway to send a guest anything. Claude cannot interfere with EnsoAI's drafts, AutoPilot sends, or workflows.
My MCP server connects but the tools never appear in Claude
Claude Desktop only reads its config at startup: fully quit (Cmd+Q on macOS, quit from the tray on Windows) and reopen. Still missing? Check for invalid JSON in claude_desktop_config.json, a non-absolute path to your server file, or Node missing from PATH. Each PMS guide has a fuller troubleshooting list.
I want Claude to write back, not just read
Every guide in this cluster ships read-only on purpose: exploration first, writes as a deliberate second step. If you add write tools to your PMS server, keep them in a separate MCP server from the read tools, and remember that anything you write to the PMS may sync onward into Enso Connect's automations. Test on a dummy reservation first.
The gap both systems share: nobody is looking at the property. EnsoAI handles what guests say; a PMS-connected Claude handles what your data says. What neither sees is what your cleaners' cameras see between stays. RapidEye reads the turnover photos and video your team already captures and flags damage and missed cleaning before the next Boarding Pass goes out. If you want findings delivered into your own stack, the RapidEye API is in early access.
FAQ
Does Enso Connect have a public API?
Not a public, self-serve one. As of July 2026 there is no developer documentation, API reference, or OpenAPI spec published anywhere we could find, and API directories list Enso Connect's developer-docs fields as empty. Enso Connect consumes the APIs of the PMS platforms it integrates with rather than exposing its own to customers. If your operation needs programmatic access, ask your account manager or support@ensoconnect.com directly.
Is there an Enso Connect MCP server?
No, neither official nor community-built as of July 2026. Without a public API to wrap, a community server cannot exist yet. The PMS route in this guide is the working substitute, and it covers the reservation data most questions actually need.
What is EnsoAI?
Enso Connect's built-in guest messaging AI. CoPilot mode drafts a reply to every guest message for human approval; AutoPilot mode sends autonomously when its confidence meter clears roughly 90 percent. According to Enso Connect, it works across 200+ languages and draws on guidebooks, conversation history, and PMS-connected reservation data, across 60,000+ listings.
Can Claude replace EnsoAI?
Different jobs. EnsoAI answers your guests in real time inside Enso Connect. Claude, connected as described here, answers you: analysis, drafting, and cross-system questions. Running both is the sensible setup, and this guide's read-only design means they cannot step on each other.
Is Enso Connect a PMS?
No. Enso Connect describes itself as an AI-native guest experience platform for vacation rentals and boutique hotels, and its own FAQ addresses the "is it a PMS" misconception directly. It layers on top of Guesty, Hostaway, OwnerRez, Hostfully, Lodgify, and others, which is precisely why the PMS route works.
Other guides in this library
Connect Guesty to Claude
An Enso Connect pairing Guesty documents in its own help center.
Connect Hostaway to Claude
Your Account ID doubles as the OAuth client ID.
Connect Breezeway to Claude
The turnover-ops side of the same stack.
Or browse all of them: Claude guides for the STR stack.
Sources
- Enso Connect: AI Guest Experience for Short Term Rentals (homepage)https://ensoconnect.com/
- EnsoAI: Elevate Your Guest Experience With AIhttps://ensoconnect.com/features/enso-ai
- What is Enso Connecthttps://ensoconnect.com/company/what-is-enso-connect
- Enso Connect API, API Tracker (no public developer docs listed)https://apitracker.io/a/ensoconnect
- Enso Connect, Guesty Help Centerhttps://help.guesty.com/hc/en-gb/articles/9361711686173-Enso-Connect
- Enso Connect integration, Hostfullyhttps://www.hostfully.com/integrations/enso-connect/
- Model Context Protocol: Build an MCP serverhttps://modelcontextprotocol.io/quickstart/server
- Claude Code: Connect to tools via MCPhttps://code.claude.com/docs/en/mcp
Independent integration guide. RapidEye is not affiliated with or endorsed by Enso Connect or Anthropic. Product capabilities and menus change; confirm specifics against the official sources above. Last reviewed July 19, 2026.