









































Works out-of-box with your favorite AI agents

Maintenance Care is a maintenance management platform used to schedule work orders, track assets, and keep equipment running. Makini's MCP server brings Maintenance Care data and workflows to AI agents directly, with no custom integration to build.
Have any questions? We’re here to help You
Maintenance Care is a CMMS from a Cambridge, Ontario company with a Free Forever plan, but the free tier is small: 2 users, 3 preventive maintenance schedules, 5 assets, 3 vendors and the Mobile App Lite. The main paid plan is a flat $250 per month for unlimited users, work orders, PMs and assets, and Enterprise Elite is custom priced. Senior care, healthcare, hospitality, education, manufacturing and local government sites are typical customers.
Maintenance Care has an API, but only on the top plan: API access is listed as an Enterprise Elite feature, not in the Free or standard $250 per month plan, and there is no public developer documentation. Standard plan customers rely on vendor built integrations such as Amazon Alexa, Google Calendar and Excel exports. For an MCP agent this is Makini's concern: you authorize a login through Makini Link and get_connection_details shows what is exposed.
The Maintenance Care online work order page is a request form that staff submit from any browser; each submission becomes a task in the work order list with a status, priority and creation date, and the paid plans run a duplication checker so the same leak is not reported twice. Maintenance staff then assign, update and close the task in the web or mobile app, and requesters receive notifications as it moves.
To connect Maintenance Care to Claude or ChatGPT, authorize your Maintenance Care login through Makini Link, then paste the MCP endpoint Makini issues into Claude, ChatGPT, Cursor or any other MCP client. Credentials are entered in Makini Link, not in the chat client. Call get_connection_details afterwards to see which objects the connection exposes; Makini's unified models cover work orders, assets, locations, stock items and maintenance triggers where the connection supports them.
An AI agent can turn Maintenance Care records into the reports the paid plans already export to PDF or Excel, but on demand: open work orders by age and priority, preventive maintenance completed versus scheduled this month, repair history and spend on one asset, or parts below their reorder minimum. It works from whatever the connection exposes, so if asset history or parts are missing from get_connection_details, say so before the agent guesses.
Creating work orders in Maintenance Care over MCP may work without the Elite API, because Makini connects with the credentials you already use rather than a vendor API key and its tool list includes work order creation and update tools; still, a write succeeds only where the connection and the user's rights allow it, which can depend on your plan. Start with reads, then try a draft work order that a supervisor reviews.
Maintenance Care integrates with Amazon Alexa, so a technician can create or check tasks by voice, and sells wireless sensors that monitor equipment remotely and can raise work orders; it also offers room booking and a 3D space view on the Elite plan. An MCP agent sees the resulting records, such as sensor generated work orders or meter readings, only where the connection exposes them; it never talks to Alexa or the sensors directly.
Authorize the Makini connection with a Maintenance Care login that already sees all facilities, assets and parts the agent should cover, ideally a dedicated user named for the agent so audit logs separate its activity from staff; audit logs exist on the paid plans, not the free one. The MCP endpoint Makini issues is scoped to that login, so a login limited to one building limits the agent to that building as well.