OAuth 2.1
Lueira MCP server
Read bookings, customers and availability from a compatible MCP client. Write tools cover customers, shop stock and, with the marketing scopes, email campaigns, subject to granted permissions.
- 🗓️ List bookings
- 👤 Look up a customer
- 📦 Check stock
- 📦 Update authorized stock
- ✉️ Prepare email campaigns
- 📊 Query occupancy
Connect Lueira to your AI assistant
The Lueira MCP server can read bookings, customers, catalogue and availability. With write permissions it supports customer and shop-stock operations and, with the optional, sensitive `marketing:read` and `marketing:write` scopes, email campaign management: rule-based customer groups, templates and sends. A real send needs explicit confirmation and a recipient count matching a fresh pre-check, and only reaches customers who gave consent; it does not create orders, record payments or change marketing settings. It uses OAuth 2.1 over Streamable HTTP.
Before you start: you need a Lueira account with API access enabled.
Pick your client
Select the tool you use. Every one connects to the same server URL above; only the steps differ.
Manual setup in about a minute.
- 1Open claude.ai, click your profile icon, then Personalize, then Connectors.
- 2Click the "+" button and choose "Add custom connector".
- 3Paste the MCP server URL from above.
- 4Click Connect. The browser will redirect you to Lueira's login.
- 5Authorize access. Done.
OAuth 2.1 authentication
The connection uses OAuth 2.1 over Streamable HTTP. You never paste your password or an API key into the MCP client: you authenticate on Lueira in your browser and decide which permissions to grant.
1. The client requests access
The MCP client (Claude, ChatGPT…) connects to mcp.lueira.com and starts an OAuth 2.1 flow. Sign-in and consent are handled by Lueira's authorization server at api.lueira.com — that's the domain you'll see in the browser. The first time, the client registers automatically (dynamic client registration).
2. You sign in to Lueira
The browser opens Lueira's login screen with your usual account. You never share credentials with the MCP client.
3. You choose the permissions
Lueira shows the requested permissions to read data or modify customers and shop stock; you choose which to grant.
4. The token is issued
On approval, Lueira issues a token with those permissions. It's stored in the MCP client and refreshed automatically while the connection is active.
You decide what your AI can do
Your assistant always inherits the permissions of your own Lueira user: it can never do anything you can't. When you authorize the connection, Lueira asks which profile to grant within those limits. Change it any time from Settings → Developers → Credentials.
Analyst
Read-onlyYour assistant can look up bookings, customers, products, availability and occupancy. It can read but never change anything.
Operator
Read + writeAdds authorized customer and shop-stock operations. It does not create orders or record payments.
Custom
Your rulesPick exactly which scopes to grant, one by one. Reuse the same scopes as the REST API for full control.
Check that it works
Ask your assistant something about your account. It will use the Lueira tools to fetch real data.
- 💬 List my bookings this week
- 💬 Show me customers with pending dives
- 💬 How much kayak stock do I have?
- 💬 Show availability for tomorrow at 10:00
Manage the connection
The connection creates an access token in Lueira with the permissions you granted to the MCP. You can review it at any time in Settings → Developers → Credentials.
- Disconnect: in your client's connector settings, click Lueira and choose Disconnect.
- Reconnect: repeat the install steps above.
- Revoke from Lueira: in Settings → Developers → Credentials, revoke the MCP client's token in one click.
Troubleshooting
"0 tools visible"
Your Lueira account may lack the required permissions, or the profile you granted is too narrow. Review Credentials and re-authorize if needed.
"Session not found"
Disconnect and reconnect from your MCP client.
OAuth error
Make sure your Lueira account has API access enabled and you're using the exact MCP server URL.
Token stops working
Tokens refresh automatically. If the client has been closed for a long time the refresh may have expired — reconnect and you're good.