GuestPoint MCP connector

Connecting GuestPoint to Claude takes two steps. First, open Elaichi, choose GuestPoint and paste in your GuestPoint API key, which is the only sign-in step, so there is no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. After that Claude can check availability, quote rates and create reservations in GuestPoint on your behalf.

Yes. Once GuestPoint 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. You connect GuestPoint once and every client uses it.

With GuestPoint connected, an AI agent can check room availability at your properties for a set of dates, look up the best available rates, and create or update a reservation. It can also add an extra such as breakfast or parking to a property, and look up the currencies and exchange rates GuestPoint holds so it can quote an international guest in their own currency. It cannot do anything in GuestPoint beyond those actions.

No. The AI only sees what the GuestPoint API key it was connected with can see, so if that key covers two properties, the agent works with those two properties and nothing else. Elaichi can narrow that access further by restricting specific actions, but it can never widen it beyond what GuestPoint itself allows.

Yes. One person connects GuestPoint in Elaichi with the API key and shares the connection with a team, and nobody else on the team ever handles that key. Each teammate still signs in to Elaichi as themselves, so every reservation created or changed in GuestPoint is recorded in the audit log under the name of the person who asked for it.

Yes. In Elaichi you can restrict each GuestPoint action separately, so you could allow checking availability and rates while restricting the creation or updating of reservations. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.

When you offboard a person in Elaichi, their access to GuestPoint through every client ends at once, and the audit log keeps the record of what they did. If they were using a shared GuestPoint connection, it keeps working for everyone else on the team. If you want to remove GuestPoint entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

Yes. GuestPoint 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.

Yes. Both let Claude, ChatGPT or Cursor use GuestPoint. 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 GuestPoint call.

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 GuestPoint: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.