How to Connect apaleo to Meta Muse via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → apaleo, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

apaleo + Meta Muse

Hotel operations in the apaleo cloud property management system: properties, rooms and room types, rate plans and rates, availability and offers, bookings, reservations and guests, groups, folios, payments, invoices, maintenance, housekeeping and performance reports. Creates bookings, assigns rooms and checks guests in and out. Connects as an app with OAuth2 client credentials; cancellations and no-shows install switched off.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

APALEO_CLIENT_ID, APALEO_CLIENT_SECRET

Step 1 — Get credentials

Setting up takes about 5 minutes. You need an apaleo account with access to Apps. There is no browser sign-in: the connector authenticates as an app with the OAuth2 client credentials grant.

1. In apaleo open Apps > Connected apps > Add a custom app (or on apaleo.dev register an OAuth simple client with client credentials).
2. Give the app the permissions the team needs. For reading, for example properties.read, unitgroups.read, units.read, rateplans.read, rates.read, services.read, companies.read, availability.read, offers.read, reservations.read, groups.read, blocks.read, folios.read, payments.read, invoices.read, maintenances.read and reports.read; for the writes reservations.create, reservations.manage, reservations.assign-unit, maintenances.create and operations.change-room-state. Leave out the write permissions for a read-only connector.
3. Copy the client id into APALEO_CLIENT_ID and the client secret into APALEO_CLIENT_SECRET. The secret is shown only once; if it is lost, create a new one in the app.
4. Install the connector and run apaleo_list_properties to check the connection.

The connector gets a token from https://identity.apaleo.com/connect/token and renews it every hour. Every call runs as the custom app with its permissions; a permission the app lacks answers 403.

What it reads:

• Inventory and rates: properties (hotels), unit groups (room types), units (rooms) with condition and maintenance, rate plans, prices per night with restrictions (apaleo_list_rates), services (extras such as breakfast or parking), cancellation policies and companies (corporate accounts).
• Availability and offers: rooms left per room type and night (apaleo_get_unit_group_availability), rooms free for a whole stay (apaleo_get_unit_availability), rooms that can be assigned to a reservation, and apaleo_get_offers, the bookable rate plans with prices for one stay.
• Bookings and reservations: apaleo_list_reservations with text_search (name, email, reservation id) and date_filter Arrival, Departure or Stay together with from and to; apaleo_count_reservations counts without loading them. Bookings, reservation services, groups and blocks. Guests are part of reservations (primaryGuest, additionalGuests) and bookings (booker).
• Billing: folios (guest bills, found by reservation_ids), folio payments and invoices.
• Operations and reports: maintenance windows, property performance (occupancy, ADR, RevPAR), revenues by account with net, gross and VAT (for a period of at most one year) and arriving reservations per day of a month.

What it writes:

• Bookings: apaleo_create_booking with the ratePlanId and one timeSlice per night taken from apaleo_get_offers. apaleo_update_booking and apaleo_update_reservation take JSON Patch operations such as [{"op": "replace", "path": "/comment", "value": "Late arrival"}]. apaleo_amend_reservation changes arrival, departure, number of guests, rate plan and price per night.
• Front desk: apaleo_assign_unit (apaleo picks a free room) or apaleo_assign_specific_unit, apaleo_unassign_units, apaleo_check_in_reservation (undo with apaleo_revert_check_in) and apaleo_check_out_reservation, which posts all open charges on the folio and only works when the departure is not later than tomorrow.
• Housekeeping and maintenance: apaleo_set_unit_conditions (Clean, CleanToBeInspected, Dirty) and apaleo_create_maintenance (OutOfService, OutOfOrder, OutOfInventory).

Bookings, check-ins and check-outs change the live hotel, so the AI shows you what it is about to change and waits for your yes.

Switched off at install: apaleo_cancel_reservation (the cancellation fee of the rate plan's policy applies, and a canceled reservation cannot be reactivated) and apaleo_set_reservation_no_show (posts the no-show fee to the folio and cannot be reverted). An admin switches them on when the team needs them.

Data formats: ids are readable codes: a property MUC, a unit group MUC-DBL, a unit MUC-101, a rate plan MUC-FLEX-DBL, a booking ABCDEF, its reservations ABCDEF-1 and ABCDEF-2, a folio ABCDEF-1-1. Money is {"amount": 120.0, "currency": "EUR"} in major units; a reservation's balance is negative when the guest still owes money. Dates are YYYY-MM-DD; times are ISO 8601 with the property's UTC offset. A night belongs to the business day it starts on; to is included for availability and performance, excluded for the revenues report. Reservation status is Confirmed, InHouse, CheckedOut, Canceled or NoShow. Filters with several values are comma-separated without spaces (status: Confirmed,InHouse), and expand adds embedded objects (expand: booker,assignedUnits).

Paging: lists take page_number (from 1) and page_size (up to 500) and return the total in count. A page past the end answers 204 No Content, which means there is nothing more.

Common errors: 401 means a wrong client id or secret or an expired token. 403 means a permission missing on the custom app. 404 is an unknown id. 422 is a business rule, for example a check-in before the arrival day, no unit assigned or a sold-out offer, with the reason in messages. 429 is the rate limit.

The connector does not post charges or payments, does not create invoices, does not change rate plans, prices or inventory, and does not manage apaleo users or apps.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Muse

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Muse adds remote MCP servers as custom connectors and signs in to them with OAuth.

1. In Muse, open Settings → Connectors and choose Add custom connector.
2. Paste the MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.
3. Muse opens the AnythingMCP sign-in page: sign in and approve access.
4. In a chat, ask Muse for something that needs the apaleo tools.

You can also set it up from a chat, on the web, in the iOS and Android apps or in WhatsApp. Send Muse this message:

Create a Custom Connector for a new remote MCP server, then connect to it:
Name: AnythingMCP
Transport: remote streamable HTTP
URL: https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID
Auth: OAuth

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Muse connects from Meta's cloud, so localhost does not work.

Available tools

Example prompts

• "Which reservations arrive today at MUC, and which of them still have no room assigned?"
• "How many double rooms are still free next Friday and Saturday, and what does the flexible rate cost for both nights?"
• "Show me occupancy, ADR and RevPAR for last month compared with the month before."
• "Assign a clean room to reservation ABCDEF-1 and check the guest in."
• "Mark rooms MUC-101 to MUC-105 as clean and put MUC-210 out of order until Monday because of a broken shower."

FAQ

Where is Muse available? Meta currently offers Muse in the US and Canada, on the web, in the iOS and Android apps and in WhatsApp.

Does Meta review this connector? No. Meta doesn't review custom connectors. Muse sees only the tools you switched on for this MCP server in AnythingMCP, and you can disconnect it anytime under Settings → Connectors.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Microsoft Copilot