EZRentOut MCP by usefulapi
Server Details
MCP server for EZRentOut — rental orders, assets, customers, inventory and work orders.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 59 tools
Most tools map to a single, clearly named resource and action, and descriptions explicitly disambiguate close pairs (get_asset vs get_asset_stock vs get_inventory_item; list_orders vs list_purchase_orders). The main friction is the asset read cluster — list_assets, filter_assets, search_assets and list_assets_in_service (which is literally filter_assets with status=assets_being_serviced) overlap enough that an agent may pick the wrong one. get_location_quantities vs get_quantity_by_location is a milder version of the same problem.
Every tool uses the same ezrentout_ prefix followed by a verb_noun pattern (get_, list_, create_, add_, search_, filter_, record_, start_, complete_, book_, rent_out_, return_). No casing drift or mixed conventions. Verbs are used consistently by intent: get_ for single-entity fetches, list_ for collections, search_ for query-based lookup.
59 tools is far above the comfortable range and forces an agent to sort through a large surface to pick the right call. The breadth is partly justified by a genuinely large domain (assets, stock, inventory, orders, work orders, purchase orders, customers, businesses, users, locations, vendors), and each tool does correspond to a distinct endpoint. Still, this is a near-1:1 mirroring of the vendor REST API rather than a curated, task-oriented tool set.
Read coverage is thorough and the order lifecycle (create, add assets, book, rent out, return, pay) plus work-order lifecycle are covered end to end. However, update/delete operations are largely absent — no update_customer, update_asset, delete/cancel/void order, remove_assets_from_order, or edit work order details — and creation is missing for assets, inventory and businesses. Agents will hit dead ends when they need to correct or remove data.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
MCP server for MarketTime — wholesale orders, customers, catalog and shipment tracking.
MCP server for Flex on the Job: inventory, jobs, customers, invoices, purchasing, sales orders.
MCP server for SkuVault — products, inventory, sales, purchase orders and stock adjustments.
MCP server for SmartAgent CRM: leads, tasks, sales pipelines, property listings
Related MCP Servers
- AlicenseAqualityCmaintenanceMCP server for the Snipe-IT asset management REST API, enabling read and write operations on assets, licenses, accessories, and more.13Apache 2.0
- -
- AlicenseNot gradedqualityCmaintenanceMCP server for ConnectWise PSA (Manage) enabling ticket management, time entry, and read-only lookups of companies, contacts, and configurations with role-based access control and bring-your-own-API-keys support.116 npm6MIT
- AlicenseAqualityCmaintenanceMCP server for interacting with the SuperOps.ai PSA/RMM platform, providing tools for managing clients, tickets, assets, and technicians via GraphQL API.21Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.