Connect Claude, ChatGPT or Microsoft Copilot to your AssetLab account and work with live data in plain language: ask what is overdue, raise a work order, build a PM program from a manufacturer’s PDF, or brief council on a capital plan. Every major resource in AssetLab is a tool, and your API key decides which ones the assistant can use.
Which work orders at the arena are overdue? Bump the chiller one to urgent.
Three are overdue at the arena. WO-2291 is now urgent.
| WO-2291 | Chiller 2 low suction pressure | Urgent |
| WO-2264 | Zamboni room exhaust fan | 9 days |
| WO-2240 | Lobby door closer | 14 days |
- 480+
- tools
- 100+
- resources
- Read & write
- per scope
- Hosted or local
- HTTP or stdio
Connect your assistant
Four clients, one server. Each needs an AssetLab API key, created by an administrator in Settings → API Keys.
- 01Create an API key in AssetLab under Settings → API Keys.
- 02In claude.ai, open Settings → Connectors → Add connector.
- 03Paste the connector URL
https://mcp.assetlab.ca. - 04When asked to authorize, paste your API key.
Any other MCP client: point it at https://mcp.assetlab.ca and authorize with your API key.
Tools
Names follow one pattern, so an assistant can build them rather than search: list_ and get_ to read, create_, update_ and delete_ to write, plus the resource, as in create_work_order.
Work management
7 resources
Work orders, comments, schedules, work requests, PM schedules and templates.
Assets & maintenance records
17 resources
Assets, condition assessments, costs, parts, replacement plans and lifecycle strategies.
Sites, buildings & systems
11 resources
Sites and FCI history, buildings, locations, systems, floorplans and regions.
Infrastructure
11 resources
Networks, feature classes, segments and nodes with GeoJSON geometry, inspections, zones.
Projects & capital planning
20+ resources
Projects, tasks and dependencies, phases, budget items, risks, cost snapshots.
Finance & vendors
10 resources
Budgets, expenses, invoices, purchase orders, change orders, contracts and vendors.
Compliance, forms & levels of service
15 resources
Compliance items and records, inspection forms and responses, LoS measures and targets.
Admin & analytics
6 resources
Dashboard summaries and snapshots, custom fields, users, bulk create and update.
Scopes & security
A key carries read and write scopes per resource, such as work_orders:read or assets:write. The assistant never gets more than the key allows. Start with a read-only key for a week, then add write scopes where they earn it.
Read-only by default
Write tools only appear when the key has write scopes for that resource.
Tenant-bound
A key reaches one organization; the server ignores any attempt to address another.
Audited
Every call lands in AssetLab’s audit log under the key that made it.
Revocable
Revoke a key in Settings → API Keys and every connected assistant stops at once.
OAuth 2.0 with PKCE
Hosted connectors authorize through mcp.assetlab.ca, which keeps your key only in encrypted form.
Data stays put
Customer Data is hosted in Canada. The MCP server processes records in flight and stores none.
The MCP server runs on Cloudflare’s edge nearest the caller, generally outside Canada. The Trust Center lists it with every other supporting service.
REST API & webhooks
The MCP server is a translator over the same REST API you can call directly, with the same keys and scopes. Use it for integrations that should not involve an assistant: syncing an ERP, pushing sensor readings, or reacting to new work orders with webhooks.
This website, for agents
Researching AssetLab with an AI agent? assetlab.ca registers WebMCP tools in the browser, so agents that support it can ask for pricing or compare vendors instead of scraping pages. Every answer names its source and how fresh it is.
- get_pricing
- Plans and prices, as published
- search_faq
- Answers from the site FAQ
- lookup_glossary_term
- Definitions from the glossary
- calculate_cmms_roi
- The ROI calculator, as a function
- compare_with
- Comparison pages for a named vendor
- get_demo_availability
- Real open demo times (reserves nothing)
- get_product_profile
- Structured fit, limitations and compliance
- request_demo
- Asks for a demo: the only tool that acts
Prefer plain text? The site summary for language models is at /llms.txt.
FAQ
Does AssetLab have an MCP server?
Yes. AssetLab runs a hosted MCP server at mcp.assetlab.ca and publishes the same server on npm as @assetlab/mcp-server for local use. It exposes 480+ tools across 100+ resources, from work orders and PM schedules to capital projects and infrastructure networks, and is listed in the official MCP Registry as ca.assetlab/mcp-server.
Which AI assistants work with AssetLab?
Claude (claude.ai, Claude Desktop and Claude Code), ChatGPT through custom connectors, and Microsoft 365 Copilot through an agent built once in Copilot Studio. Any other client that speaks the Model Context Protocol can connect to mcp.assetlab.ca with an AssetLab API key.
Which AssetLab plan includes the API and MCP server?
API keys, which the REST API, webhooks and the MCP server all use, are included on the Enterprise plan and available on other plans as an add-on. The MCP server is off until an administrator creates a key.
Can an AI assistant change data in AssetLab?
Only if its API key has write scopes. Scopes are set per resource in Settings > API Keys, so a key can read work orders but not touch budgets, or read everything and write nothing. Every call is tenant-bound, recorded in the audit log, and stops the moment the key is revoked.
Where is data processed when I use the MCP server?
Customer Data stays hosted in Canada. The MCP server itself runs on Cloudflare’s edge at the location nearest the caller, generally outside Canada: it processes the records a request returns while in flight and stores none, and holds your API key only in encrypted form. The Trust Center lists it with the other supporting services.
Put an assistant on your assets
API keys come with the Enterprise plan, or as an add-on to other plans. We’ll set one up with you on a demo.
