Cloudbeds MCP connector
The Cloudbeds connector brings group allotment blocks, folio adjustments, guest email templates and schedules, custom fields, property settings and dashboards to Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, with every action tied to the person who signed in.
- Connects over OAuth
- Free 14-day trial
- No credit card
Which allotment blocks still have unsold rooms this weekend?
Working in Cloudbeds with Elaichi
-
List all Cloudbeds oauth metadata
-
List all Cloudbeds userinfos
-
List all Cloudbeds get allotment blocks
How to connect Cloudbeds to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Cloudbeds MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Cloudbeds MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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.
Cloudbeds MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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.
Cloudbeds MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Cloudbeds MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Cloudbeds to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Cloudbeds through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Cloudbeds is logged.
-
Group sales
Set up a group block once the contract signs
Create the allotment block in Cloudbeds with the agreed dates and room count, then add the notes from the contract so the front desk sees the terms without asking.
-
Reservations
Adjust a block when the group changes
Update the allotment block when the organizer adds rooms or shifts dates, and drop the block cleanly if the group cancels.
-
Front desk
Post a folio adjustment during checkout
Apply a credit for a maintenance issue or a correction for a misposted charge in Cloudbeds while the guest is still at the desk.
-
Finance
Reverse a batch of adjustments posted in error
Remove a set of mistaken adjustments in one pass instead of opening each folio, with a record of who did it and when.
-
Guest communications
Draft and schedule pre-arrival emails
Write a new email template for early check-in offers or parking instructions, then set the schedule so it goes out a set number of days before arrival.
-
Operations
Check settings and custom fields across properties
Pull the property settings, currency settings and custom fields for each hotel in Cloudbeds, spot the ones that drifted, and add a missing custom field where a property needs it.
Try asking
- “Which allotment blocks still have unsold rooms this weekend?”
- “Summarize adjustments posted against the Lisbon property yesterday.”
- “Add a note to the group allotment block for March.”
What connecting Cloudbeds gets you
6 screens from Elaichi, each doing one job for your Cloudbeds account.
Ask Elaichi to work across your apps.
Which allotment blocks still have unsold rooms this weekend?
Summarize adjustments posted against the Lisbon property yesterday.
Add a note to the group allotment block for March.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about tonight's allotment blocks in plain language.
Elaichi's agent answers from live Cloudbeds adjustments, allotment blocks and property settings.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Cloudbeds here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
555 Cloudbeds tools cataloged and ready to call.
Allotment blocks, adjustments, block notes and property settings, with no custom code written.
Toolboxes
Every team gets its own Cloudbeds toolbox.
Revenue, front desk and finance each see a toolbox curated for their work.
Shared connections
Share a Cloudbeds property, never the credential.
The connections table shows who connected each account and which teams use it.
Audit log
Every Cloudbeds call is written down.
When, who, what happened, type and resource, in an append only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Cloudbeds digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch adjustments
Cloudbeds
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Cloudbeds
Queued
Automations
A schedule fires, the digest posts back.
Cloudbeds adjustments are fetched, grouped, drafted by an agent, approved, then posted back.
Cloudbeds health
Refreshed 4 minutes ago · every 15 minutes · from the adjustments collection
Adjustments
1,284 ↓ 12%
Allotment blocks
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Adjustments created
Last 14 days
By team
Share of activity
Lisbon resort 34%
City hotels EMEA 27%
Groups and events 21%
Finance 18%
Collections and dashboards
Cloudbeds numbers arrive before anyone asks.
Four metrics, 14 days of records created and a team breakdown, computed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Cloudbeds
All three can connect Cloudbeds 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.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Cloudbeds tools | Allow or restrict single Cloudbeds 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 Cloudbeds 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Cloudbeds tools for your AI agents
555 tools are ready to call through Elaichi's MCP endpoint the moment you connect Cloudbeds, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 247 of 555 Cloudbeds tools here. Connect Cloudbeds and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
How do I connect Cloudbeds to Claude?
Two steps. First, connect Cloudbeds in Elaichi: Cloudbeds asks you to register an OAuth application in your own Cloudbeds account, so one person brings that client ID and secret once, then signs in to Cloudbeds and approves the connection. Second, in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude then signs you in through Elaichi and Cloudbeds is available in your conversations.
Does Cloudbeds work with ChatGPT and Cursor as well as Claude?
Yes. Once Cloudbeds 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 Cloudbeds once and every client you use picks it up.
What can an AI agent actually do with my Cloudbeds data?
It can create, update and remove group allotment blocks and their notes, post adjustments to folios or reverse a batch of them, read your dashboards, and look up property settings, currency settings and custom fields in Cloudbeds. It can also draft email templates and set email schedules for guest messages. Because Cloudbeds exposes several hundred actions, short concrete asks like "add two rooms to the Morgan wedding block" work better than long paragraphs.
Does connecting Cloudbeds give the AI access to all my properties?
No. Every action runs as the person who signed in to Cloudbeds, so the AI sees only the properties and settings that person can already reach. Elaichi can narrow that further, for example limiting a team to allotment blocks and email templates, but it never grants anything the person could not do in Cloudbeds directly.
Can I stop an agent from deleting or changing things in Cloudbeds?
Yes. Restrictions in Elaichi apply per action, so you can allow reading dashboards and property settings while restricting the removal of allotment blocks or the bulk deletion of adjustments in Cloudbeds. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a Cloudbeds connection when someone leaves?
Offboarding that person in Elaichi ends their access to Cloudbeds through every client at once. A shared Cloudbeds connection keeps working for everyone else on the team. If you disconnect Cloudbeds in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.
Does the Cloudbeds MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Cloudbeds 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 Cloudbeds?
Yes. Both let Claude, ChatGPT or Cursor use Cloudbeds. 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 Cloudbeds call.
How is Elaichi different from Composio for Cloudbeds?
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 Cloudbeds: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Cloudbeds in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot