Louez MCP server: your store in Claude, ChatGPT and Grok.

MCP (Model Context Protocol) is the open standard AI assistants use to connect to other software. The Louez MCP server, at https://app.louez.io/api/mcp, lets Claude, ChatGPT, Grok or a coding tool read and run your rental store with 100+ tools: bookings, products, prices, customers, payments and figures. You sign in with your Louez account, and the assistant only gets the stores, rights and tools you choose.

Any assistant that accepts a remote MCP server with OAuth sign-in: Claude, on every plan, ChatGPT, on the Business, Enterprise and Edu plans, Grok, Mistral Vibe, and Perplexity, on the Pro, Max and Enterprise plans. Claude Code, Codex, Cursor and VS Code connect the same way. On a team plan, an administrator adds the connector first. ChatGPT and Codex don't create stores: create yours in Louez. For n8n or a script, use a Louez API key.

No. The connection uses OAuth: your assistant sends you to Louez to sign in, then you choose what it can do. API keys are for scripts, n8n and clients that can't sign in with OAuth.

It manages your catalogue (products with their whole form, degressive pricing, seasons, deposit, taxes, promotions, stock, variants, accessories, categories), follows your bookings (list, calendar over the period you choose, detail, statuses, notes, pickups and returns, late returns, availability), your customers and your payments, and reads your analytics. It also sets up your store (contact details, opening hours, pickup points, delivery, taxes, legal documents, online store) and can create a new one, then put it online once you agree (except ChatGPT and Codex: you create the store in Louez). It sees your team and its invitations, removes a member or cancels an invitation after a confirmation, and invites someone as a member: the invitation is only created once you approve it from the link it gives you, within 24 hours. Creating a booking or changing its dates, refunding, writing a free message to your customers, changing a member's role or changing plans are not open to it yet.

Payments, always: recording or deleting a payment and recording a deposit return ask for confirmation even on a connection with confirmations turned off, as do spending credits on an AI photo edit, removing a team member and cancelling an invitation. Deleting, archiving, removing units, confirming, declining or cancelling a booking (which sends your customer the usual message, per your notification settings), changing your taxes or delivery, and creating a store or putting it online ask too, unless you turn confirmations off for that connection. Louez then answers with a preview and a single-use token, valid for ten minutes and tied to that exact action, and does nothing until the request comes back with that token. Your assistant is told to show you the preview and wait for your go-ahead, but it is the assistant that sends the request back: Louez cannot check that you answered. For an agent that must change nothing, choose read only.

Only the ones you tick when you connect it, or all of them, future ones included, if you choose so. In each store it never has more rights than your role, and a role taken away applies from its next action.

Its changes to the catalogue, bookings, settings, online store and team are logged with the agent's name. In Settings, Integrations, MCP, Connected agents, you see each agent, its stores, its rights and its last logged change, and you disconnect it in one click. Its actions on customers and payments are not in this log yet. For logged changes, a creation retried with the same idempotency key creates no duplicate.

Yes, in every formula. Your assistant does the thinking, on your own subscription: the connection uses no Louez AI credits. Only Louez's AI photo edits spend them, when they are paid, and always after a preview of the price. Each connection is limited to 120 calls a minute.