Limble CMMS

Active

An AI agent for Limble CMMS. It works in a scene with a live connection to Limble CMMS. It asks before it writes, and every run is traced.

Connect Limble CMMS to pin locations, machines and work orders as assets, read the maintenance backlog with real names instead of ids, and let an agent turn a downtime event or an alarm into a work order — with the upstream reference stored on the task so both systems stay in sync.

Data & Databases Custom 4 asset types

What you can connect

Add these to your scene and AI gets access.

Limble Account Limble Accounts

A Limble CMMS customer, connected with API Client ID and Secret

RegionClient IDClient SecretCustomerPlan

Location Locations

A plant, lab or site in Limble

Location IDTimezoneRegion

Machine Machines

A Limble asset — a machine, line or piece of equipment under maintenance

Asset IDLocation IDLocationRegion

Work Order Work Orders

A Limble task — work order, preventive maintenance or work request

Task IDTypeMachineLocationRegion

Connect Limble CMMS over MCP

Daslab is itself an MCP server.

Connect Limble CMMS in a scene, then pin that scene's URL in Claude Code, Cursor, or any MCP client. The agent there gets your Limble CMMS tools, and your approval gate and trace travel with them.

https://daslab.run/mcp/<your-world>/<your-scene>

One scene can hold Limble CMMS and everything else you connect, so a single endpoint carries them all. Set up a client.

Use cases

Turn a machine downtime event into a Limble work order and write the number back
Watch a machine's open and overdue work as a live tile
Close a work order from the floor with a note and downtime
Submit work requests from operator-facing flows for a reviewer to approve