EZRentOut MCP by usefulapi

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

• Verbindung: Läuft in der Cloud
• Transport: Streamable HTTP
• Kategorie: Onlineshops & Zahlungen

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Du brauchst

• Läuft in der CloudNichts zu installieren; die Verbindung läuft übers Internet

Welche App nutzt du?

https://ezrentout.usefulapi.io/mcp

claude mcp add --transport http ezrentout https://ezrentout.usefulapi.io/mcp

{
  "mcpServers": {
    "ezrentout": {
      "url": "https://ezrentout.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "ezrentout": {
      "type": "http",
      "url": "https://ezrentout.usefulapi.io/mcp"
    }
  }
}

https://ezrentout.usefulapi.io/mcp

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 6. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.

• ezrentout_list_orders

  List all rental orders (25 per page) with status, customer and dates. Paged: add 1 to page for the next one. GET /baskets.api.

• ezrentout_get_order

  One order by its order number: customer, status, dates, line items (order_line_items), sub-rent items, totals and payments. GET /baskets/ .api.

• ezrentout_get_order_history

  The check-out / check-in history of one order. GET /baskets/ /history.api.

• ezrentout_list_payment_options

  The payment options (cash, check, ...) that ezrentout_record_order_payment accepts. GET /payment_options.api.

• ezrentout_list_coupons

  All pricing coupons of the company. GET /pricing_coupons.api.

• ezrentout_list_customers

  List customers (25 per page). Optional filter: email, category, taxed, non_taxed, inactive_customers, subscribed_emails, not_subscribed_emails, checked_out_orders, completed_orders, account_name. email, category, account_name and completed_orders (for example "> 50") need filter_

• ezrentout_get_customer

  One customer by id: name, email, phone, addresses, status, custom fields. GET /customers/ .api.

• ezrentout_search_member_by_email

  Look up the customer, business contact or business that has an email address. GET /api/members/search_by_email.api.

• ezrentout_list_businesses

  List business customers (20 per page). Optional filter: all, active_businesses, inactive_businesses, checked_out_orders, active_customers, completed_orders (completed_orders needs filter_val, for example "> 50"). GET /businesses.api.

• ezrentout_get_business

  One business customer by id. GET /businesses/ .api.

• ezrentout_list_business_contacts

  List the contact persons of business customers (25 per page). GET /contacts.api.

• ezrentout_get_business_contact

  One business contact by id. GET /contacts/ .api.

• ezrentout_list_customer_addresses

  The shipping/billing addresses of one customer. GET /customers/ /shipping_addresses.api.

• ezrentout_list_business_addresses

  The shipping/billing addresses of one business. GET /businesses/ /shipping_addresses.api.

• ezrentout_list_assets

  List fixed assets (the individually tracked rental items, 25 per page) with group, location and status. GET /assets.api.

• ezrentout_filter_assets

  Assets by a status filter. status: available, assets_being_serviced, availability_range, checked_out (= currently rented out), group, location, overdue, possessions_of, possessions_of_email, reserved, product_model_number, items_in_order, reservation_starting_today, retired, upda

• ezrentout_search_assets

  Search by asset name (3+ characters), or # followed by the item number, or @ followed by the identification number. GET /search.api (facet FixedAsset).

• ezrentout_get_asset

  One fixed asset by its asset number: details, group, location, status, rental prices, optionally service details and custom fields. GET /assets/ .api.

• ezrentout_get_asset_history

  The check-in/check-out and change history of one asset (5 entries per page). GET /assets/ /history_paginate.api.

• ezrentout_get_asset_booked_dates

  The dates on which an asset, inventory item or asset stock is booked or reserved. GET /assets/ /booked_dates.api.

• ezrentout_list_asset_comments

  The comments on one item (25 per page), optionally by one user. GET /assets/ /comments.api.

• ezrentout_list_assets_in_service

  Assets currently in maintenance (25 per page), optionally only one service type or state. GET /assets/filter.api?for_service=true&status=assets_being_serviced.

• ezrentout_list_inventory

  List inventory (consumable items tracked by quantity, 25 per page). GET /inventory.api.

• ezrentout_get_inventory_item

  One inventory item by item number, with its stock. GET /inventory/ .api.

• ezrentout_search_inventory

  Search inventory items by name, # or @ . GET /search.api (facet VolatileAsset).

• ezrentout_get_inventory_history

  The stock movements (added, sold, transferred) of one inventory item. GET /inventory/ /history.api.

• ezrentout_get_quantity_by_location

  The stock of an inventory or asset-stock item at one location. GET /locations/get_quantity_by_location.api.

• ezrentout_list_asset_stock

  List asset stock (bulk items tracked by quantity per location, 25 per page). GET /stock_assets.api.

• ezrentout_get_asset_stock

  One asset stock item by number. GET /stock_assets/ .api.

• ezrentout_list_users

  The company's users (staff/admins, 25 per page). Filter by email, employee_identification_number or status (filter_val: active, inactive, login, non_login, all). GET /members.api.

• ezrentout_get_user

  One user by id. GET /members/ .api.

• ezrentout_get_user_checked_out_items

  The assets currently checked out to one user (a read; the vendor API uses PUT for this lookup). PUT /members/ /checked_out_items.api?page=N with item_type in the form body.

• ezrentout_list_locations

  The company's locations (25 per page); status all, active or inactive. GET /locations/get_line_item_locations.api.

• ezrentout_get_location

  One location by id. GET /locations/ .api.

• ezrentout_get_location_quantities

  The quantity of every asset, asset-stock and inventory item at one location. GET /locations/ /quantities_by_asset_ids.api.

• ezrentout_list_groups

  The asset groups (categories, 25 per page) with their items. GET /assets/classification_view.api.

• ezrentout_list_subgroups

  All subgroups, or those of one group. GET /groups/get_sub_groups.api.

• ezrentout_list_bundles

  Bundles (items rented together, 25 per page). GET /bundles.api.

• ezrentout_get_bundle

  One bundle by id, with its items. GET /bundles/ .api.

• ezrentout_list_vendors

  The company's vendors/suppliers (25 per page). GET /assets/vendors.api.

• ezrentout_list_custom_fields

  The custom fields defined for items (names and ids). GET /assets/custom_attributes.api.

• ezrentout_list_purchase_orders

  All purchase orders. GET /purchase_orders.api.

• ezrentout_get_purchase_order

  One purchase order with its items. GET /purchase_orders/ .api.

• ezrentout_list_work_orders

  Maintenance work orders (25 per page), optionally by status filter (open, in_progess [sic, as the vendor spells it], review_pending, complete) or by work order type. GET /tasks.api.

• ezrentout_get_work_order

  One work order by number. GET /tasks/ .api.

• ezrentout_list_work_order_types

  The work order types of the company. GET /task_types.api.

• ezrentout_list_custom_reports

  The saved custom reports (id, name, description). GET /reports/list_custom_reports.api.

• ezrentout_create_customer

  Create a customer (a person who rents). First and last name are required. Does not create an order. POST /customers.api.

• ezrentout_create_order

  Create a new rental order (a draft until it is booked or rented out) for a customer, optionally with assets and dates. If the customer belongs to several businesses, pass business_id. Does not rent anything out and does not charge. POST /baskets.api.

• ezrentout_add_assets_to_order

  Add assets (or bundles as -b) to an existing order. PATCH /baskets/ /update_basket_from_show.api.

• ezrentout_book_order

  Reserve an order's assets for a period (books the order). EZRentOut may notify the customer according to the account's settings. PATCH /baskets/ /reservation.api.

• ezrentout_add_order_custom_entry

  Add a custom line (a named amount, for example a delivery fee) to an order; it raises the order total. Not possible on sold, void, completed or cancelled orders. POST /baskets/ /custom_entries.api.

• ezrentout_record_order_payment

  Record a payment received for an order (a prepayment). It records the amount in EZRentOut; it does not charge a card (credit card payments are not supported by the API). Use a payment_method_name from ezrentout_list_payment_options. PATCH /baskets/ /charge_pre_payment.api.

• ezrentout_rent_out_order

  Check an order out: its assets go to the customer and the rental clock and billing start. EZRentOut may email the customer according to the account's settings. Give rentout_date and return_date, or use_current_datetime. PATCH /baskets/ /checkout.api.

• ezrentout_return_order

  Check an order in: the customer returned the assets, rental billing ends and the assets become available again. Give return_date (and return_time), or use_current_datetime to return now. Returns the whole order (no partial returns, late fees or payment here; use ezrentout_record_

• ezrentout_add_asset_comment

  Add a comment to an asset, asset stock or inventory item. POST /assets/ /comments.api.

• ezrentout_create_work_order

  Create a work order with a title, type and due date, optionally for assets. By default the linked assets are marked unavailable (mark_items_unavailable). POST /tasks.api.

• ezrentout_start_work_order

  Mark a work order in progress. PATCH /tasks/ /mark_in_progress.api.

• ezrentout_complete_work_order

  Mark a work order complete; its assets may become available again. PATCH /tasks/ /mark_complete.api.

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026

• ✓ Bestanden

  Entwickler passt zum Repo

  Der Registry-Name wurde über die Domain usefulapi.io bestätigt (die Registry prüft, wem die Domain gehört)

• … Noch nicht geprüft

  Wird noch gepflegt

  Dieses Repo haben wir noch nicht von GitHub gelesen

• … Noch nicht geprüft

  Hat eine Lizenz

  Dieses Repo haben wir noch nicht von GitHub gelesen

• ✓ Bestanden

  Endpunkt antwortet

  Antwort in 15 ms (HTTP 200)

• – Nicht zutreffend

  Anmeldung mit OAuth

  Keine Anmeldung nötig

• ✓ Bestanden

  Keine versteckten Anweisungen in Tool-Beschreibungen

  Wir haben 59 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Im Vergleich mit anderen in Onlineshops & Zahlungeni

• Mehr Sterne als 0 % der anderen 1745 Server in dieser Kategorie
• Neuer in der Registry veröffentlicht als 97 % der anderen 1745 Server in dieser Kategorie
• Basischecks gleich gut wie oder besser als bei 100 % der anderen 1745 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

README vom Entwickler

{