Librent in Claude

Create reservations and manage clients and equipment right from a chat.

How to connect

  1. An owner or admin turns on the integration in Librent: Settings > Integrations.
  2. Copy the server address below.
  3. In Claude, open Customize > Connectors and select Add custom connector. Check the terms of your plan. Private plans usually do not provide a data processing agreement.
  4. Sign in to Librent, choose an organization and agree.

Server address

https://librent.app/api/mcp

What you can do

  • Clients: search, view, add, edit and delete. A client with reservations cannot be deleted. E-mail addresses, tax IDs and custom messages to clients stay in the panel.
  • Reservations: list, view, check availability, quote, create, edit and change status. Confirming or cancelling a pending reservation e-mails the customer.
  • Equipment: search, view, add and edit. New equipment is private. Publishing and the text of public equipment stay in the panel.

Data and permissions

  • Tool results, including your clients' personal data, reach Claude and may be processed outside the EEA. Further processing is governed by your company's agreement with the provider. Disconnecting Librent does not delete data from the chat history.
  • A client's ID document number and tax ID are not shared. Text fields such as notes reach the AI in full, with whatever someone typed in them.
  • The connection has your account's permissions and works only in the organization chosen at consent. Consent grants read access by default. You turn on write access separately.
  • Claude may ask you to approve write actions. Reservations from a chat count toward the same limit and billing as reservations from the panel.

Details are in the privacy policy and the AI Integration Terms.

How to disconnect

Disconnect in Settings > Integrations. Access ends at once. Turning off the integration permanently ends all of the organization's connections, and a password change ends the account's connections. After turning it back on, connect again.

Questions? Write to [email protected].