Review work orders
list_work_ordersList the signed-in company's work orders and optionally filter them by status.
The MaintenEase MCP server gives compatible AI clients a controlled way to read maintenance data and create work orders after a user signs in and approves access. Your database credentials are never shared with the model.
Available tools
Each tool has a declared purpose and validated input schema. The MCP server remains the boundary between the AI client and your maintenance records.
list_work_ordersList the signed-in company's work orders and optionally filter them by status.
create_work_orderCreate an authorized work order with a title, description, priority, due date, and optional asset.
list_assetsBrowse equipment and assets available to the signed-in user's company.
list_locationsList the sites, buildings, rooms, and other locations the company tracks.
list_maintenance_requestsRead the maintenance request inbox before turning a valid request into tracked work.
MCP does not bypass authentication or hand an AI model direct database access. MaintenEase applies the same identity and company boundaries used by the application.
OAuth consent keeps the user in control of whether an AI client can connect to MaintenEase.
Every tool call carries the authorized user's identity instead of relying on a shared organization credential.
Database row-level security limits records to the signed-in user's company.
The client can call only the maintenance actions published by the MCP server and their validated inputs.
Connection flow
Use the endpoint or server card in an AI client that supports remote MCP servers and OAuth.
The client opens the MaintenEase authorization flow without receiving the user's password.
The user confirms the connection before the client receives an access token.
The AI client can select an available tool while MaintenEase continues to enforce user and company permissions.
It is a Model Context Protocol service that publishes controlled CMMS tools for compatible AI clients. It can list work orders, assets, locations, and maintenance requests and can create a work order after user authorization.
They can connect when the relevant product, plan, and workspace policy support remote OAuth-authenticated MCP servers. Availability and setup controls can vary by AI client.
No. The client receives a revocable OAuth access token after user consent. MaintenEase applies the signed-in user's permissions and tenant-scoped data rules to every tool call.
Yes. The create_work_order tool accepts a narrow, validated set of fields. The work order is created for the signed-in user's company and records that user as its creator.
Use the MCP server card, the clean Markdown version of this page, llms.txt, llms-full.txt, and the structured AI catalog at /api/ai.json.
Read how MCP fits a maintenance workflow, how OAuth preserves user identity, and how controlled tools support an agentic CMMS.