MCP

Run your Lodgestory workspace from Claude, ChatGPT, or any MCP-compatible assistant — ask in plain language, and the assistant works inside Lodgestory on your behalf, secured by your own sign-in.

TL;DR

• What it is — a secure connector that lets an AI assistant read and act in your Lodgestory workspace: look up contacts and teams, check channels, manage chat assignments, run reports, send messages, and place calls — all by asking in chat.
• Who it's for — Account Owners and Admins who'd rather ask an assistant ("who's assigned to this chat?", "send me a call-log report for last week") than click through the dashboard.
• Top outcome — your assistant does real work in Lodgestory, scoped to one organisation and limited to exactly what your role can do — without ever seeing your password or any key.

At a glance

How to connect

From Claude Desktop

1. Open Settings → Connectors and choose Add custom connector.
2. Name it Lodgestory and paste the connection URL https://api.lodgestory.com/mcp. Leave the optional client ID / secret fields blank.
3. Click Add, then Connect — a browser window opens.
4. Sign in with your Lodgestory account (if you aren't already), and pick the organisation you want the assistant to work in.
5. You're returned to the assistant, and Lodgestory's actions are now available in any chat.

📸 [SCREENSHOT: mcp-connect-claude.png — Add custom connector dialog with the Lodgestory URL]

Claude on the web is the same path: Settings → Connectors → Add custom connector.
ChatGPT: add the same connection URL as a connector in its Apps & Connectors / Developer settings.

📸 [SCREENSHOT: mcp-org-picker.png — choosing which organisation to grant the assistant access to]

What you can do

Ask in plain language. The assistant picks the right action and shows you what it's about to do before it runs anything sensitive.

Contacts & teams

• List the people in your organisation, with their roles and team memberships.
• List your teams and who's on them.

Channels

• See which channels are connected (WhatsApp, Instagram, Email, and more) and their status.
• List your approved WhatsApp message templates.
• Author WhatsApp templates and submit them to Meta for review — standard shapes plus carousel (media cards) and limited-time-offer templates, with positional ({{1}}) or named ({{guest_name}}) placeholders (both fully sendable), coupon copy-code buttons, and a per-template delivery TTL. Header and card media upload from a public URL. (Submits to Meta for real review.)
• Edit an existing template: send just the parts you're changing (untouched components — including carousel cards and offer blocks — are preserved), or replace the full component set to restructure a carousel or limited-time offer; the delivery TTL can be changed the same way. Authentication/OTP templates are authored in the dashboard, not here.

Chats

• See who's assigned to a chat and which teams are on it.
• Assign or remove people and teams, and set the primary assignee.
• Assigning a team routes the chat the way the inbox does: an available member with spare capacity becomes the primary. If everyone on the team is offline or at their open-chat cap (set under Settings → Team Members), the chat stays with the team and no owner — it waits in the team's queue until someone claims it or an automation pulls it.

Messaging

• Start a new chat for a phone number on a channel.
• Send a message — text, media, or an approved template — to an existing chat. (This reaches a real customer.)

WhatsApp groups (WhatsApp Official channels with an Official Business Account)

• Create a WhatsApp group and follow its creation through to a ready-to-use chat. (Creates a real group on WhatsApp.)
• List your groups, or open one to see its members and their status (invited, pending approval, joined).
• Add or remove members by phone number, and fetch the shareable invite link. (Adding members notifies real people.)
• Approve or reject pending join requests for approval-required groups.
• The group behaves like any chat afterwards — send messages to it and assign agents or teams with the chat tools above.

Reports

• Generate a report — one of ten types: chats, contacts, tickets, call logs, goals, bookings, follow-ups, survey responses, WhatsApp Flow responses, or chat stage history (CHAT_STATE_HISTORY) — then check its status and get a download link. (Account Owners and Admins.)
• Chat stage history exports one row per workflow stage a chat entered — when it was entered and left, time in stage, who moved it and why — closed chats included. Narrow it with every chat filter plus a stage-date range and "moved by" users, for example "export every stage change on the Front Desk workflow last week". The chat report itself now exports every chat, open and closed, unless you ask for one side.
• Flow-response exports can be narrowed to particular flows, to how the flow was sent (journey, campaign, chat template, or test send), and to a date range — for example "export last month's answers from the lead-capture flow".

Voice (if Voice is enabled for your organisation)

• Review call history, recordings, and transcripts.
• See your phone numbers, agents, and accounts.
• Place a click-to-call from an agent to a customer, or end a live call. (Placing a call rings a real phone.)
• Place a one-shot voice broadcast — dial a number and play a spoken message generated on the fly (text-to-speech), then hang up; no agent involved. (Reaches a real phone.)
• List the available text-to-speech voices to pick one for a broadcast.
• Manage your Masked Connect customer list.

Example prompts

• "List the team members in my organisation."
• "Which channels do I have connected, and which WhatsApp templates are approved?"
• "Who's assigned to the chat with Asha? Add Ravi and make him the primary."
• "Generate a call-log report for last week and give me the download link when it's ready."

How sign-in keeps you safe

• You sign in, not the assistant. Connecting sends you to Lodgestory's own sign-in screen. The assistant receives a limited, time-bound access token — never your password or an API key.
• One organisation at a time. Each connection is bound to the single organisation you pick. To work in another, add a second connection and choose that organisation.
• Your role, your limits. The assistant can only do what you can do. An action your role can't perform in the dashboard is refused here too.
• You approve sensitive actions. Assistants ask before running an action that sends a message, places a call, or changes data — review it first.

Roles & permissions

If you connect as a team member without the right role, those actions return a "not permitted" message — sign in as an Account Owner or Admin for the full set.

Connections

• Lodgestory CRM — contacts, teams, chats, channels, assignments, and messaging are all reachable.
• Lodgestory Voice — calls, recordings, transcripts, agents, and Masked Connect, once Voice is enabled for your organisation.
• Reports — the same reports you can run from the dashboard.
• Your sign-in — uses the same Lodgestory account and roles as the app; nothing separate to manage.

Errors & FAQ

Do I need an API key?
No. You connect with just the URL and sign in with your Lodgestory account — there's nothing to copy or paste.

Can the assistant see my password?
No. You sign in on Lodgestory's own screen; the assistant only ever receives a limited, time-bound access token.

It sent me to a sign-in screen.
You weren't signed in to Lodgestory in that browser. Sign in and the connection continues on its own.

A voice action says the Voice API isn't enabled.
Voice actions need Voice API access for your organisation. Contact your account team to switch it on; everything else works without it.

An action says it's "not permitted".
The account you connected with doesn't have the role for that action (for example, reports are Account-Owner / Admin only). Reconnect as an Account Owner or Admin.

Can it work across two organisations at once?
Each connection covers one organisation. Add a second connection and pick the other organisation to work in both.

Which assistants are supported?
Any that support the Model Context Protocol — including Claude (desktop and web) and ChatGPT.

Related

• Accounts & sign-in — how Lodgestory sign-in and the partner API work.
• What is Lodgestory? — the platform overview.