The Flexkeeping timeline
2012
Flexkeeping founded as a hotel housekeeping and staff collaboration platform. Per the acquisition press release, its tools made hotel teams 40% more productive and cut guest complaints by 45%.
2019
Flexkeeping and Mews become integration partners. Flexkeeping also integrates with Cloudbeds, RMS Cloud, Apaleo, Shiji, and Oracle OPERA.
2025
Mews announces the acquisition of Flexkeeping on September 30, 2025 (terms undisclosed). Housekeeping becomes "natively connected" to the Mews PMS.

The short version. You cannot connect Flexkeeping to Claude with an API key today. Flexkeeping publishes no public developer documentation, and as of July 2026 no MCP server exists for it, official or community-built. Two routes work now: export Flexkeeping data and Photo Proof images into a Claude Project, or, if your hotel runs Mews, reach the same operational layer through the Mews Connector API, which is fully documented and open. Since Mews acquired Flexkeeping in September 2025, the Mews API is the strategic front door to housekeeping data in this ecosystem.

What the acquisition means for AI access

On September 30, 2025, Mews announced it had acquired Flexkeeping for an undisclosed amount. According to the Mews press release, founder Richard Valtr framed it plainly: "For the first time, Mews' customers will have a truly best-in-class housekeeping platform natively connected to their PMS."

For anyone trying to get housekeeping data in front of an AI assistant, this changes the map. Flexkeeping on its own was a closed system: excellent inside the app, invisible outside it. Mews is the opposite. It maintains a public, versioned Open API with an OpenAPI spec on GitHub, and according to Mews its Marketplace carries 1,000+ integrations. As Flexkeeping's tools are wired "directly into the PMS," as the Mews blog puts it, the housekeeping layer inherits a documented API surface it never had.

Two things Flexkeeping said in its own announcement matter for planning. First, it will remain "an independent platform, committed to supporting every property, on the many PMS hoteliers rely on," so Cloudbeds, RMS, Oracle, Apaleo, and Shiji properties are not being cut off. Second, Mews acknowledged in its follow-up post that its own built-in housekeeping "works really well for smaller sized properties" and that Flexkeeping is the specialist layer for larger hotels and groups. Read together: Flexkeeping is the housekeeping product, Mews is the data platform.

What you would ask Claude with this data

The point of the connection is not novelty. A housekeeping or rooms division lead sitting on Flexkeeping task history can put questions like these to Claude:

"Here is last month's task completion export. Which room attendants have the longest average clean times, and does it correlate with the floors they were assigned?"
"Compare maintenance tickets raised by housekeeping this quarter vs last. Which recurring issues (AC, grout, caulking) are trending up by floor?"
"These are the Photo Proof images from today's checkouts on floor 4. Flag any room where the bed setup or amenity tray doesn't match our standard."
"Draft next week's deep-clean rotation given these occupancy forecasts and the rooms that missed their last scheduled deep clean."
"Turn this month's guest complaint log into the three root causes housekeeping can actually fix, with the rooms and shifts involved."

Prerequisites

Flexkeeping access
An account with permission to view analytics and export data. Flexkeeping's FAQ describes analytics spanning labour efficiency, repair tracking, linen usage, complaint trends, and task completion times.
Claude
A Claude plan with Projects (for a persistent housekeeping workspace), or Claude Desktop if you plan to use MCP against the Mews API.
For Route 2 only
A property running Mews, plus Connector API access tokens (see the Mews guide for the full setup).
Not required
A Flexkeeping API key. There is no self-serve developer portal to get one from.

The realistic routes

ROUTE 1

Exports into a Claude Project

Works today

The unglamorous route is the one that works for every Flexkeeping property regardless of PMS. Flexkeeping's reporting covers task completion times, labour efficiency, repairs, linen usage, and complaint trends. Pull those reports on a fixed cadence and give Claude a standing workspace:

  1. Create a Claude Project called something like Housekeeping Ops and put your cleaning standards, room-type checklists, and SLA targets in the project knowledge.
  2. Weekly, export or download your Flexkeeping reports (and any Photo Proof images you want reviewed) and upload them into a conversation in that Project.
  3. Ask the analysis questions above. Because the standards live in project knowledge, Claude scores each week's export against the same bar.

A prompt shape that works well as the first message of each weekly thread:

You are our housekeeping performance analyst. Attached is this week's task export from Flexkeeping and the Photo Proof images from checkout cleans. Against the standards in project knowledge: 1) flag rooms or tasks outside SLA, 2) name the top 3 recurring maintenance themes, 3) list anything in the photos that fails our visual standard, with room numbers.
ROUTE 2

Through the Mews Connector API

Mews properties

If your property runs Mews, you do not need Flexkeeping to open up, because the PMS side already is. The Mews Connector API is Mews' general-purpose API for accessing data and services in Mews Operations, with public docs and an OpenAPI definition maintained on GitHub (MewsSystems/open-api-docs). Reservations, spaces, and operational state live there, and it is the layer Mews says Flexkeeping is being natively connected to.

The practical move: build (or adopt) an MCP server against the Mews Connector API so Claude can query operational data directly, then treat Flexkeeping as the execution layer your team works in. We wrote that setup up separately: Connect Mews to Claude.

This is also the route to watch. Mews' stated integration direction, housekeeping "built directly into your PMS workflow," means housekeeping state should surface behind the documented API over time rather than behind a closed one.

ROUTE 3

Ask for partner-level access

On request

Flexkeeping clearly has integration machinery internally. It maintains two-way integrations with apaleo, RMS Cloud, Canary, Guesty, Beds24, and others, and those were built vendor-to-vendor. What it lacks is a public, self-serve developer surface.

If you operate at group scale and a live feed matters to you, raise it with your Flexkeeping account contact (or, post-acquisition, your Mews contact). Be specific: name the entities you want (task events, room status changes, Photo Proof attachments), the direction (read-only outbound), and the destination (your own middleware or an MCP server). Partner integrations exist because customers asked; AI access requests are the same conversation.

Where this is heading

The pattern across hospitality software is consistent: closed operational tools are being pulled into platforms with open APIs, and AI assistants sit on top of the API layer, not the app layer. The Flexkeeping acquisition is a clean example. The housekeeping product stays the housekeeping product; the data access story migrates to Mews.

If housekeeping photo documentation is the part you care about, that is our home turf. RapidEye analyzes room and turnover photos automatically to catch the damage and standard misses a manual review skips; the RapidEye API covers programmatic submission and results if you want that in your own stack.

Troubleshooting and FAQ

Does Flexkeeping have a public API?

No. There is no public developer documentation, no self-serve API key flow, and no developer portal on flexkeeping.com. Integrations with PMS platforms (Mews, Cloudbeds, RMS Cloud, Apaleo, Shiji, Oracle OPERA) are vendor-to-vendor partnerships. If you find a page claiming a Flexkeeping API key setup, it is usually the PMS side of a partner integration, not something you can build against yourself.

Is there a Flexkeeping MCP server?

No, as of July 2026. Neither Flexkeeping nor Mews ships one, and no community server exists, which follows from the lack of a public API to build on. If Mews ever ships an MCP server for its Connector API, that would effectively become the Flexkeeping MCP story too, given the native integration direction. Until then, Route 1 and Route 2 above are the honest options.

Did Mews really acquire Flexkeeping, and on what terms?

Yes. Mews announced it on September 30, 2025; financial terms were not disclosed. Flexkeeping was founded in 2012, had been a Mews integration partner since 2019, and its founder and CEO Luka Berger said joining Mews "accelerates our shared vision to make hotel operations effortless." Sources are linked at the bottom of this page.

We are on Cloudbeds / Apaleo / OPERA, not Mews. Are we stranded?

No. Flexkeeping committed in its acquisition announcement to remaining independent and supporting properties on other PMS platforms. Route 1 (exports into a Claude Project) works identically for you. If your PMS has its own open API, the Route 2 pattern applies with your PMS swapped in; check the rest of the Claude guides library for your stack.

Can Claude analyze our Photo Proof images?

Yes, once you get them out. Flexkeeping's Photo Proof feature prompts staff to attach photos when a task is completed, which per Flexkeeping "improves accountability and visibility for all staff." Those photos live inside Flexkeeping, so today the flow is manual: download, upload to Claude, review against your standards. Claude is genuinely good at spotting deviations in room photos when you give it the standard to compare against.

Claude gives inconsistent answers on the same export

Almost always a context problem, not a model problem. Put your standards, SLA thresholds, and room-type definitions in Claude Project knowledge once instead of restating them per chat, keep one thread per reporting period, and ask for structured output (a table with fixed columns) so week-over-week comparisons stay stable.

Sources & references

  1. Mews Acquires Flexkeeping, Delivering Next-Generation Housekeeping Innovation for Hoteliers (Mews press release, September 30, 2025)https://www.mews.com/en/press/mews-acquires-flexkeeping
  2. Flexkeeping and Mews Are Joining Forces (Flexkeeping blog)https://flexkeeping.com/blog/flexkeeping-and-mews-are-joining-forces
  3. Why Mews acquired Flexkeeping and what it means for hoteliers (Mews blog, October 2, 2025)https://www.mews.com/en/blog/why-mews-acquired-flexkeeping
  4. Flexkeeping FAQ (Photo Proof, analytics, PMS integrations)https://flexkeeping.com/resources/faq
  5. Mews Open API documentationhttps://docs.mews.com/
  6. MewsSystems/open-api-docs (Mews Open API source, includes the Connector API OpenAPI definition)https://github.com/MewsSystems/open-api-docs
  7. Mews Acquires Flexkeeping (Hospitality Net, September 30, 2025)https://www.hospitalitynet.org/news/4129132.html

Related guides

PMS · the new front door

Connect Mews to Claude

The open, documented API that Flexkeeping data is being natively connected to. Start here if you run Mews.

 Hotel ops

Connect HotSOS to Claude

The other big hotel service-order platform, and what its data access actually looks like.

 The full library

All Claude guides

PMS, pricing, screening, locks, and ops platforms, each with its honest connection story.