How to connect Mews to Claude IA ?

That would be amazing if Mews could connect directly with Claude. Even better if it were a native integration built by Mews itself, rather than having to rely on third-party companies or external connectors. A direct Mews connection would make the whole setup much cleaner, safer, and easier to manage.

Hi ​@Cyprien & ​@JTJ46, thanks for voicing your interest in connecting Mews and Claude! Let me check with the team and I’ll let you know as soon as I know more  👍

Hello Cypren, 

No native integration yet. Jess already confirmed the team is looking into it. You don't need to wait though. We run Mews and Claude side by side every day across our properties, so here's what actually works. Four options, least effort first.

1. Export and upload. Zero code.
Export anything from Mews (reservations, availability, accounting report, customer list) as CSV or Excel and upload it straight into Claude. Then ask what you need: forecast occupancy, flag the bookings likely to cancel, find duplicate profiles, clean the ledger. Most people should start here. It's a snapshot, not live, but you can be running it in five minutes. Our whole cancellation risk dashboard works this way. Claude reads the Mews export and scores every booking.

2. Connector API into the Claude API. Needs some dev.
Ask Mews for API credentials for your property. You get a Client Token and an Access Token, plus a sandbox to test in. A small script then pulls from the Connector API and feeds it to Claude through Anthropic's API. This is for when you want it automated and repeatable instead of one question at a time.

3. MCP server. The cleanest setup.
The closest thing to a real connection today. You wrap the Mews Connector API in an MCP server (Anthropic's protocol, open source), and Claude queries Mews live in plain language, like "today's arrivals" or "ADR this week". More to set up, but worth it if you want Claude talking to Mews directly.

4. Make or Zapier. Low code, good for triggers.
Wire the Mews API into Make or Zapier with their HTTP steps. Both have Claude actions built in. Handy for things like: a new booking comes in, Claude drafts the message that goes out before check in, and it sends automatically. No real coding.

One thing on all of them: it's guest data, so keep your API tokens on the backend and don't paste personal info into a chat you don't control.

Tell me what you want Claude to actually do (analysis, automation, or guest messaging) and I'll point you to the right one.

Erick Adorno

Co-founder @ The Haus