MaintainX MCP integration for AI agents.
Connect AI agents to MaintainX through 16 structured actions, including get location, create location, and delete location. Review authentication, inputs, wo…
- ACTION CONTRACTS
- 16
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the MaintainX integration exposes
The MaintainX Agent App exposes 16 provider-backed actions for productivity and data work. Its current contract lets an authorized agent retrieve one maintainx location by id, create a maintainx location, and delete a maintainx location by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected MaintainX account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real MaintainX capabilities.
Showing 12 of 16 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_locationREADRetrieve one MaintainX location by id.
INPUTS: id
create_locationWRITECreate a MaintainX location.
INPUTS: name / description / address / barcode / parentId
delete_locationHIGH IMPACTDelete a MaintainX location by id.
INPUTS: id / skipWebhook
create_userWRITECreate a MaintainX user.
INPUTS: firstName / lastName / email / phoneNumber / role
create_work_orderWRITECreate a MaintainX work order.
INPUTS: title / description / assetId / locationId / priority
create_work_order_commentWRITECreate a comment on a MaintainX work order.
INPUTS: id / content / skipWebhook
get_userREADRetrieve one MaintainX user by id.
INPUTS: id / organizationId
get_work_orderREADRetrieve one MaintainX work order by global id.
INPUTS: id / expand / useSequentialId
list_locationsREADList MaintainX locations with filters and cursor pagination.
INPUTS: cursor / limit / organizationId / organizationIds / name
list_usersREADList MaintainX users with filters and cursor pagination.
INPUTS: cursor / limit / organizationId / onlyAssignable / email
list_work_order_commentsREADList comments on a MaintainX work order.
INPUTS: id / cursor / limit
list_work_ordersREADList MaintainX work orders with filters and cursor pagination.
INPUTS: cursor / limit / organizationId / title / assets
INPUT CONTRACTS
Know what the action needs before it runs.
get_location
idOPTIONAL- MaintainX location id.
create_location
nameREQUIRED- MaintainX location name.
descriptionOPTIONALaddressOPTIONALbarcodeOPTIONALparentIdOPTIONAL
delete_location
idREQUIRED- MaintainX location id.
skipWebhookOPTIONAL- Whether MaintainX should skip triggering subscribed webhooks.
create_user
firstNameREQUIRED- MaintainX user's first name.
lastNameREQUIRED- MaintainX user's last name.
emailOPTIONALphoneNumberOPTIONALroleOPTIONAL
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Location
Retrieve one MaintainX location by id. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_locationControl Create Location
Create a MaintainX location. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_locationVerify with Get User
Retrieve one MaintainX user by id. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_userSAFETY BOUNDARY
Operate MaintainX with explicit limits
- Authorize MaintainX with API key and grant only the provider access required by the selected actions.
- 8 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_location` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in MaintainX rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the MaintainX task completed successfully.
CONNECTION MODEL
API key
MaintainX REST API key sent with the Authorization: Bearer header. Generate a key in MaintainX under Settings > Integrations > API Keys: https://app.getmaintainx.com/settings/integrations/apiKeys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 8
- WRITE SIGNALS
- 7
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by MaintainX.