# Lodgify MCP connector

The Lodgify connector brings bookings, availability, quotes, payment links, key codes and guest messages into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, with each person signed in as themselves and every action logged.

Source: https://elaichi.ai/connectors/lodgify/

## Facts

| | |
| --- | --- |
| Application | Lodgify |
| Category | CRM |
| AI tools | 73 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Lodgify is connected

- Which properties are free next weekend for four guests?
- Send a payment link for the Harbor View booking arriving Friday.
- Confirm all tentative bookings that check in this week.

## Connect Lodgify in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Lodgify.
2. Optionally set Share with, then press Connect.
3. Paste a Lodgify API key. One person generates a token in Lodgify and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Lodgify tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Lodgify MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Lodgify MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Lodgify MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Lodgify MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Lodgify MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Lodgify to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Lodgify tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Lodgify through Elaichi

### Book a stay straight from a phone enquiry

Reservations. Check which properties are free on the dates a caller wants, then create the Lodgify booking and send the quote while they are still on the line.

### Send tonight's arrivals their key codes

Guest services. Update key codes on every booking checking in today and message each guest with their arrival details in one go.

### Chase unpaid balances before arrival

Finance. Create payment links for bookings with money still owing and send payment requests to the guests, without opening each booking by hand.

### Mark the day's check-ins and check-outs done

Operations. Close out this morning's departures and record this afternoon's arrivals as checked in across all properties at once.

### Confirm or decline tentative bookings in bulk

Sales. Review every tentative Lodgify booking for the coming week, confirm the ones that have paid and decline the rest with a message to the guest.

### Reconcile bookings from other channels

Revenue management. Pull the bookings that arrived through external channels, compare them with Lodgify availability and reopen or recover any that went wrong.

## Elaichi vs Zapier MCP vs Composio for Lodgify

All three can connect Lodgify to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Lodgify tools | Allow or restrict single Lodgify tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Lodgify call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Lodgify to Claude?

Connect Lodgify in Elaichi, then open Claude and go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Lodgify's own sign-in step is pasting an API key from your Lodgify account into Elaichi. There is no OAuth application to register and no client ID or secret to generate, and the whole thing takes a few minutes.

### Does Lodgify work with ChatGPT and Cursor as well as Claude?

Yes. Once Lodgify is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. Connect Lodgify once and every client your team uses sees it.

### What can an AI agent actually do with my Lodgify bookings?

An agent can check which Lodgify properties are free on given dates, create a booking, send a quote, confirm or decline tentative bookings, create payment links and payment requests, message a guest, update key codes and mark check-ins and check-outs in bulk. It can also list bookings that came in from other channels and reopen or recover a booking. Short concrete asks work best, such as confirm all tentative bookings arriving Friday rather than a long paragraph.

### Does connecting Lodgify give the AI every property and booking in my account?

An agent working through the Lodgify connection can only reach what the connected Lodgify account can reach, and never more. Each person signs in to Elaichi as themselves, so the roles and restrictions set for that person apply to every Lodgify call they make. Elaichi can narrow what a person or role can do in Lodgify, and it can never widen it.

### Can my team share one Lodgify connection?

Yes. One person connects Lodgify with the API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in as themselves, so the audit log records exactly who created a booking, sent a payment link or changed a key code.

### Can I stop an agent from declining or changing bookings in Lodgify?

Yes. Restrictions in Elaichi work per action on Lodgify, so you can restrict declining bookings or updating key codes for a role or for one person while leaving quotes and messages open. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Lodgify connection when someone leaves?

Offboarding a person in Elaichi ends their access to Lodgify at once, across every client they used. A shared Lodgify connection keeps working for everyone else on the team. If you ever want Lodgify gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

### Does the Lodgify MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Lodgify is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Lodgify?

Yes. Both let Claude, ChatGPT or Cursor use Lodgify. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Lodgify call.

### How is Elaichi different from Composio for Lodgify?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Lodgify: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 73 Lodgify tools

Every tool below is callable through https://api.elaichi.ai/mcp once Lodgify is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Lodgify availability** (List). Retrieves availability information for all properties and room types associated with the authenticated user for a given date range. Retrieves availability information for all properties and room types associated with the authenticated user for a given date range. Required: periodStart, periodEnd.
- **List all Lodgify availability v 2** (List). Retrieves availability calendar data for all properties associated with the authenticated user for a given date range. Retrieves availability calendar data for all properties associated with the authenticated user for a given date range. Required: start, end.
- **Lodgify booking check ins bulk update** (Update). Sets the check-in time for a booking. Sets the check-in time for a booking. Required: booking_id, time.
- **Lodgify booking check ins v 2 bulk update** (Update). Checkin a booking at the specified time. Required: booking_id, time.
- **Lodgify booking check outs bulk update** (Update). Sets the check-out time for a booking. Sets the check-out time for a booking. Required: booking_id, time.
- **Lodgify booking check outs v 2 bulk update** (Update). Checkout a booking at the specified time. Required: booking_id, time.
- **Lodgify booking confirmations bulk update** (Update). Sets a booking as booked. Changes the status of a booking to Booked and updates the availability calendar accordingly. Required: booking_id.
- **Lodgify booking declines bulk update** (Update). Sets a booking as declined. Declines a booking, changing its status to Declined. Required: booking_id.
- **List all Lodgify booking external bookings** (List). External bookings by Booking id. Get the list of external bookings belonging to the specified Id. Required: booking_id.
- **Lodgify booking key codes bulk update** (Update). Update rooms' access key codes. Updates the access key codes of rooms belonging to a given booking. Required: booking_id.
- **Create a Lodgify booking message** (Create). Add messages to a booking. Add one or more messages for a specific booking. Required: booking_id.
- **Lodgify booking not replied statuses bulk update** (Update). Marks a booking as not replied. Required: booking_id.
- **Create a Lodgify booking payment link** (Create). Creates a payment link for a booking. Generates a payment link for the booking. Returns false if the amount cannot be enforced due to pending schedules. Required: booking_id.
- **List all Lodgify booking payment links** (List). Retrieves the payment link URL for a booking's quote. Returns the URL to the payment page for the current quote of a booking. Required: booking_id.
- **Create a Lodgify booking payment links v 2** (Create). Create a payment link for a booking. Required: booking_id.
- **List all Lodgify booking payment links v 2** (List). Gets a booking's payment link. Retrieve the next payment link for a Booking. Required: booking_id.
- **Lodgify booking payment requests bulk update** (Update). Requests a payment for a booking. Requests a payment for the specified booking. This triggers an email to the guest requesting payment of the specified amount. Required: booking_id.
- **Create a Lodgify booking quote** (Create). Creates a quote for a booking. Creates a new Quote for a specific booking. Required: booking_id.
- **List all Lodgify booking quotes** (List). Retrieves the quote details associated with a booking. Returns the details of the current Quote associated with a specific Booking. Required: booking_id.
- **Lodgify booking recoveries bulk update** (Update). Restores a booking from the trash. Restores a booking that was previously moved to the trash. Required: booking_id.
- **Lodgify booking reopenings bulk update** (Update). Reopens a booking. Reopens a Booking, changing its status to Open. If the booking was previously Booked, this makes the room available again. Required: booking_id.
- **Lodgify booking replied statuses bulk update** (Update). Marks a booking as replied. Required: booking_id.
- **Lodgify booking tentative statuses bulk update** (Update). Sets a booking as tentative. Changes the status of a booking to Tentative. Required: booking_id.
- **Create a Lodgify booking** (Create). Creates a new booking. Creates a new booking in the system. You can optionally upgrade an existing enquiry to a booking using the 'from' parameter.
- **Delete a Lodgify booking by ID** (Delete). Moves a booking to the trash. Moves a booking to the trash. The booking is not permanently deleted and can be restored later. Required: id.
- **Get single Lodgify booking by ID** (Get). Retrieves the full details of a specific booking. Returns the full details for a specific Booking identified by its ID. Required: id.
- **Update a Lodgify booking by ID** (Update). Updates a booking. Updates an existing Booking with the provided details. Note that not all fields can be updated via this endpoint. Required: id.
- **Get single Lodgify bookings v 2 by ID** (Get). Booking by id. Required: id.
- **List all Lodgify bookings v 2** (List). List of bookings. Retrieve a list of bookings matching the query parameters. The connector pages through all results (50 per page, or your limit up to 50).
- **Create a Lodgify call me back request** (Create). Creates a "Call Me Back" request. Creates a new CallMeBack Request. This creates an enquiry and sends an email to the property owner with a scheduled time to call the client back. Required: guest_breakdown.
- **List all Lodgify channel inventory mappings** (List). Retrieve the channel inventory mapping: the sync feed OTAs and channel managers use to map Lodgify property and room type ids to their own. Lodgify asks partners to check the Last-Modified header before downloading the feed and to cache it for up to an hour. Needs the channel API key (an optional connect field); the account's Public API key doesn't work here.
- **Get single Lodgify country by ID** (Get). Country by code. Returns a country by given his code. Required: id.
- **List all Lodgify countries** (List). Countries Codes. Returns a list of all the available countries.
- **Get single Lodgify currency by ID** (Get). Currency by code. Returns the currency with the given code. Required: id.
- **List all Lodgify currencies** (List). Currencies codes. Returns a list of available currencies in Lodgify.
- **List all Lodgify deleted properties** (List). Gets deleted properties. Returns a paged list of all deleted properties since some date.
- **Create a Lodgify enquiry** (Create). Creates a new general enquiry. Creates a new general enquiry in the system with the provided data. Required: guest_breakdown.
- **Delete a Lodgify enquiry by ID** (Delete). Moves an enquiry to the trash. Moves an Enquiry to the trash. The enquiry is not permanently deleted and can be recovered later. Required: id.
- **Get single Lodgify enquiry by ID** (Get). Retrieves the full details of a specific enquiry. Returns the full details for a specific Enquiry identified by its ID. Required: id.
- **Lodgify enquiry declines bulk update** (Update). Declines an enquiry, changing its status to Declined. Declines an enquiry, changing its status to Declined. Required: enquiry_id.
- **Create a Lodgify enquiry message** (Create). Adds messages to an enquiry. Add one or more messages for a specific enquiry. Required: enquiry_id.
- **Lodgify enquiry not replied statuses bulk update** (Update). Marks an enquiry as not replied. Required: enquiry_id.
- **Lodgify enquiry recoveries bulk update** (Update). Restores an enquiry that was previously moved to the trash. Restores an Enquiry that was previously moved to the trash. Required: enquiry_id.
- **Lodgify enquiry reopenings bulk update** (Update). Reopens an enquiry, changing its status to Open. Reopens an enquiry, changing its status to Open. Required: enquiry_id.
- **Lodgify enquiry replied statuses bulk update** (Update). Marks an enquiry as replied. Required: enquiry_id.
- **Get single Lodgify property by ID** (Get). Property info by id. Get the basic info for a given property. Required: id.
- **List all Lodgify properties** (List). Properties info list. Returns the list of completed properties for a given user. This is a protected endpoint.
- **Get single Lodgify properties v 2 by ID** (Get). Property info by Id. Get the basic info for a given property. Required: id.
- **List all Lodgify properties v 2** (List). Properties info list. Returns a paged list of all properties. The connector pages through all results (50 per page, or your limit up to 50).
- **List all Lodgify property addons** (List). Available addons. Returns a list of available addons for the given property. If additional parameters are specified, then it'll return only those that are valid. Required: property_id.
- ...and 23 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
