Docs›AI & automation
Connect Claude to Mangobeds with MCP
3 min read
Claude in your browser and on your phone can read your live Mangobeds data and answer questions about it in plain language. A Claude MCP connection takes about a minute, needs no API key and nothing technical: you paste one address, sign in, and approve. For the background on MCP, or if you use a different tool, start with Connect Mangobeds to AI tools with MCP.
This guide covers Claude at claude.ai and in the mobile app. Claude Code and Claude Desktop run on your own computer and connect with your API key instead, so they each have their own guide.
Before you start
You need a Mangobeds account and a paid Claude plan, because custom connectors are not available on Claude’s free plan. That is all. There is no key to copy and no file to edit.
Add the Claude MCP connector
- In Mangobeds, go to Apps > MCP and pick Claude (browser & mobile). Copy the MCP server URL.
- In Claude, open Settings > Connectors > Add custom connector.
- Give it a name, such as Mangobeds, and paste the URL.
- Leave the OAuth Client ID and Client Secret fields under Advanced settings empty. Claude and Mangobeds arrange that between themselves.
- Click Connect.
Mangobeds opens, asks you to sign in if you are not already, and shows an approval screen.
Choose what Claude may do
The approval screen asks two things:
- Which organization. If you belong to more than one, pick the one this connection is for. Claude never sees the others.
- Whether it may make changes. Leave this unticked and Claude can read everything and alter nothing. Tick it and it can also correct guest details, add a guest to a booking, and send one of your saved messages to a guest.
Approve, and Claude sends you back connected. Ask “what properties do I have in Mangobeds?” to check. It should answer without you giving it an ID.
Changed your mind later? Connect again and choose differently. The new approval replaces the old one.
What you can ask
Claude finds its own way around your account, so you never have to look up an ID. From there:
- Bookings: “Show the bookings checking in this week” or “Find the reservation for Maria Lopez”.
- Availability: “Which rooms are free next weekend?” or “What is my occupancy in August?”
- Blocked rooms: “Why is room 4 not bookable next Tuesday?” It tells a sold room from one you blocked, and shows the note you left.
- Prices: “What does the double room cost on 20 September?” or “Show me the seasonal rates on this room type.”
- Guests: “How many bookings has this guest had?” or “What did they put in the custom fields?”
- How Mangobeds works: Claude can read these help guides, so “how do I set up seasonal rates?” is answered next to what your own rates actually say.
If you allowed changes, be deliberate about one of them: sending a saved message delivers a real email or WhatsApp to the guest. Everything Claude changes is written into the booking’s activity with your name and Claude’s, so you can always see who authorised what.
Managing and disconnecting
Every connection made this way appears under Connected assistants on the Apps > MCP page: which assistant it is, who signed it in, what it may do and when it was last used. Disconnect ends that one connection and leaves every other integration running.
If you leave the organization, your connections stop working straight away. That is the practical advantage over an API key, which belongs to the whole organization: deleting a key disconnects everything using it at once.
If it does not connect
- Do not paste an API key. Claude in the browser cannot send one, so there is no value that would work. If a guide anywhere tells you to add an X-API-Key header here, it is out of date. Leave the OAuth fields empty.
- Start a new chat. Claude picks up the available tools when a conversation begins, so a chat opened before you connected, or before an update on our side, may still be working from an older set.
- Turn the connector off and on again in Claude’s settings if a new chat does not help.
- Check you actually approved. An approval screen closed without clicking Approve leaves nothing connected, and Claude reports a plain connection error rather than explaining why.