Let your agent launch and run your rental business.

Yes, for most of the work. Through the Louez MCP server, an agent such as Claude, ChatGPT, Grok, Codex or Cursor can create a store, set its legal identity, hours, delivery and taxes, build the catalogue with prices, seasons and deposits, take the store online, answer booking requests, record payments and deposit returns, and draft reminders for late returns. You keep the steps only you can take, such as Stripe's identity checks, and Louez shows a preview before sensitive actions. Creating a booking, changing its dates, refunding and writing free messages to customers are not open to agents yet.

Any client that accepts a remote MCP server with OAuth sign-in: Claude on every plan, ChatGPT on Business, Enterprise and Edu (read-only on Pro), Grok, Mistral Vibe and Perplexity on Pro, Max and Enterprise. Claude Code, Codex, Cursor and VS Code connect the same way. OpenClaw and n8n connect with a Louez API key sent as a Bearer token. The server address is https://app.louez.io/api/mcp.

https://app.louez.io/api/mcp. It is the same for every account and every client: after adding it, you sign in with Louez, with no API key. It is a remote server over Streamable HTTP, listed in the official MCP Registry as io.louez/louez. A self-hosted Louez serves it at its own address.

In Claude, open Customize, then Connectors, click Add and Add custom connector, and paste https://app.louez.io/api/mcp. Claude sends you to Louez to sign in, then you choose the stores, the rights (read-only, or read and edit) and the tools it gets. It works on every Claude plan, the free one included. In Claude Code, run claude mcp add --transport http louez https://app.louez.io/api/mcp, then /mcp to sign in.

The connector, added in Claude under Customize, Connectors, is for working on your store in a conversation, from claude.ai, the desktop app or your phone; it works on every Claude plan, the free one included. Claude Code is for the terminal or the editor: importing a catalogue from a file, scripting, running on a schedule. Claude Cowork, on Claude's paid plans, is Anthropic's agent for longer tasks without a terminal; it uses the connectors of your Claude account, and so do its scheduled tasks. All three reach the same Louez tools at the same address.

Run claude mcp list: Louez should show as connected. If it needs authentication, type /mcp in Claude Code and sign in to Louez; /mcp also retries a connection that failed. If Louez is missing, add it again with claude mcp add --transport http louez https://app.louez.io/api/mcp: a server is added to the current project only, unless you add --scope user. If only some tools are missing, your connection shows the groups of tools you ticked: add the others in Louez, under Settings, Integrations, MCP, Connected agents.

No. ChatGPT and Codex can manage an existing Louez store (catalogue, prices, bookings, customers, payments, settings), but they don't create stores, don't see the Louez billing and don't have the AI photo tools. Create your store in Louez, or from Claude, Claude Code, Cursor or Grok, then connect ChatGPT. Full read and write access needs a ChatGPT Business, Enterprise or Edu plan; Pro is read-only.

Not yet. The ChatGPT and Codex plugin is awaiting submission to OpenAI's Plugin Directory, and the Cursor plugin is awaiting review for the Cursor Marketplace, which also serves Grok Bot's Connect Apps. Until then, add https://app.louez.io/api/mcp as a custom MCP server or connector: the tools are the same. Grok on grok.com takes it as a custom connector, on every account. In Claude Code, the Louez plugin installs from GitHub with /plugin marketplace add Synapsr/louez-assistant-plugins, then /plugin install louez@louez.

Yes. Once connected, they read a file in your project, such as a CSV or a spreadsheet export, and create each product through the Louez tools, with its prices, degressive rates, seasons, deposit, stock and category. Each product comes back with its link in your Louez dashboard so you can check it. The Louez plugin for Claude Code adds three skills: getting started, the daily briefing and launching a store.

n8n works through its MCP Client Tool node, with the HTTP Streamable transport and a Louez API key as the Bearer token. OpenClaw adds Louez as a remote MCP server (Streamable HTTP) with the API key in the Authorization header; its OAuth sign-in has not been tried with Louez yet. Make has an MCP Client app in open beta that takes a server address and an access token; it has not been tried with Louez yet either. The owner creates API keys in Louez, under Settings, Integrations, MCP.

Not for Claude, ChatGPT, Grok, Claude Code, Codex, Cursor or VS Code: they sign in with your Louez account through OAuth, with no key to copy. An API key is for clients that don't sign in that way, such as n8n, OpenClaw or a script. A key carries its own rights per domain, and only the owner creates or revokes it, from the Louez dashboard.

The MCP server, at https://app.louez.io/api/mcp, is how an assistant reaches Louez: it lists the tools and runs them once you have signed in. A plugin packages that address for one client: the Louez plugin for Claude Code adds the server and three skills in one install. A skill is a written method the assistant follows, such as daily-briefing for "what's on at my shop today?": it calls the same tools and grants no extra right. The REST API, under /api/v1 with an API key, is for scripts; it serves the same procedures except customers, payments, analytics and the availability check, and its public reference is not published yet.

Recording or deleting a payment, recording a deposit return, spending AI credits on a photo, removing a team member and cancelling an invitation always return a preview first, on every connection. Deleting, archiving, accepting, refusing or cancelling a booking, changing taxes or delivery, creating a store and taking it online do too, unless you turn confirmations off for that connection. Louez does nothing until the request comes back with its one-time token, valid ten minutes. Your assistant is told to show you the preview and wait, but Louez cannot check that you answered: for an agent that must change nothing, choose read-only.

Not yet. An agent reads bookings, checks availability, accepts or refuses requests, changes statuses, adds notes and records payments and deposit returns. It cannot create a booking, change its dates or refund. Bookings come from your online store or from your dashboard, and refunds are made in Louez.

It follows them. It sees deposits about to expire and failed payments in the list of what needs attention, records a deposit return after a preview, and reads whether the customer has signed the rental contract. If the store requires a signed contract, Louez refuses to mark the rental as picked up until it is signed. The agent doesn't write contracts: Louez generates one for every booking, as it does without an agent.

Only when something starts it: Louez can't wake an agent up. Once running, it reads the list of what needs your attention with the cursor of its last call and gets only what is new; asked to keep watch, it calls every few minutes. n8n starts a workflow on a schedule with its Schedule Trigger node, and Claude Code runs without an interface (claude -p) from GitHub Actions, the desktop app's scheduled tasks or cloud scheduled tasks. An agent still doesn't write free messages to your customers: it drafts, you send.

There is no Louez CLI. The MCP server at https://app.louez.io/api/mcp is the documented way for agents. A REST API under /api/v1, with API keys, serves the same procedures except customers, payments, analytics and the availability check, but its public reference is not published yet. The source code of both is public on GitHub.

Connecting an agent is included in every plan: pay-as-you-go at 4% incl. VAT on your rentals with no subscription, or Pro or Ultra from $49 a month excl. VAT, with no commission. Your assistant reasons on your own subscription, so the connection uses no Louez AI credits; only AI photo edits spend them, after a preview of the price. Each connection is limited to 120 calls a minute.

Louez data stays hosted in France. An agent only gets the stores, rights and tools you chose, and never more than your role allows; a role taken away applies at its next action. Its changes to the catalogue, bookings, settings, online store and team are logged with its name. You disconnect it in one click from Settings, Integrations, MCP, Connected agents. What the agent reads then goes through your assistant's provider.

Yes. Louez is open source under the GNU AGPLv3 and runs on your own server with Docker. The MCP server is part of the app, so a self-hosted instance serves it at its own address, and API keys work there as on louez.io.

Yes, if you rent out equipment. The agent works in your Louez store whatever you rent: bikes, tools, event gear, cameras, skis, boats, trailers or childcare equipment. Products, prices, deposits, units and variants use the same tools for everyone. This page gives a request for each kind of rental Louez has a page for.