@assetlab/mcp-server 1.0.0 → 1.0.2

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 AssetLab
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,112 @@
+# @assetlab/mcp-server
+
+Connect [Claude](https://claude.ai) to your [AssetLab](https://assetlab.ca) account via the [Model Context Protocol](https://modelcontextprotocol.io). Ask Claude questions about your assets, work orders, PM schedules, and more — in plain language.
+
+## Prerequisites
+
+- [Node.js](https://nodejs.org) 18 or later
+- An AssetLab account with an API key (create one in **Settings → API Keys**)
+- [Claude Desktop](https://claude.ai/download) or [Claude Code](https://claude.ai/code)
+
+## Setup
+
+### Claude Desktop
+
+1. Open your Claude Desktop config file:
+   - **Mac:** `~/Library/Application Support/Claude/claude_desktop_config.json`
+   - **Windows:** `%APPDATA%\Claude\claude_desktop_config.json`
+
+2. Add the following to the `mcpServers` object (replace `al_live_...` with your API key):
+
+```json
+{
+  "mcpServers": {
+    "assetlab": {
+      "command": "npx",
+      "args": ["-y", "@assetlab/mcp-server"],
+      "env": {
+        "ASSETLAB_API_KEY": "al_live_...",
+        "ASSETLAB_API_URL": "https://mxxqgiqimawzeoajiklw.supabase.co/functions/v1/api-gateway"
+      }
+    }
+  }
+}
+```
+
+> **Tip:** The easiest way to get the correct config is to click **Copy Claude Config** directly on your API key in AssetLab Settings — it pre-fills your key and API URL automatically.
+
+3. Restart Claude Desktop. You should see the AssetLab tools available.
+
+### Claude Code
+
+```bash
+claude mcp add assetlab npx @assetlab/mcp-server \
+  -e ASSETLAB_API_KEY=al_live_... \
+  -e ASSETLAB_API_URL=https://mxxqgiqimawzeoajiklw.supabase.co/functions/v1/api-gateway
+```
+
+## Example prompts
+
+Once connected, you can ask Claude things like:
+
+- *"Show me all overdue work orders"*
+- *"List critical assets at Site A"*
+- *"What PM schedules are due this month?"*
+- *"Summarize the current state of our facilities"*
+- *"Which projects are at risk or delayed?"*
+- *"Show me all assets linked to the HVAC system in Building 3"*
+- *"List open corrective work orders at all sites"*
+
+## Available tools
+
+| Tool | Description |
+|------|-------------|
+| `list_assets` | List assets with filters for site, building, system, and search |
+| `get_asset` | Get full details for a specific asset |
+| `list_work_orders` | List work orders filtered by status, priority, type, or site |
+| `get_work_order` | Get full details for a specific work order |
+| `list_sites` | List all sites in your organization |
+| `get_site` | Get details for a specific site |
+| `list_buildings` | List buildings, optionally filtered by site |
+| `list_locations` | List rooms and areas, optionally filtered by building |
+| `list_systems` | List systems (HVAC, plumbing, electrical, etc.) |
+| `list_system_groups` | List system groups |
+| `list_system_classes` | List top-level system classifications |
+| `list_pm_schedules` | List PM schedules filtered by status, frequency, or site |
+| `get_pm_schedule` | Get a PM schedule including tasks and linked assets |
+| `list_pm_templates` | List reusable PM templates |
+| `list_projects` | List capital projects filtered by status or health |
+| `get_project` | Get project details including budget and progress |
+| `list_contracts` | List vendor contracts |
+| `list_compliance_items` | List compliance/regulatory items |
+| `get_compliance_item` | Get a compliance item with linked PM schedules |
+| `get_dashboard_summary` | Get aggregated stats across assets, work orders, and sites |
+
+## Scopes
+
+API keys use scopes to control what Claude can access. Grant only the scopes you need:
+
+| Scope | Access |
+|-------|--------|
+| `assets:read` | Assets |
+| `work_orders:read` | Work orders |
+| `sites:read` | Sites and buildings |
+| `locations:read` | Locations |
+| `systems:read` | Systems, system groups, system classes |
+| `pm_schedules:read` | PM schedules and templates |
+| `projects:read` | Capital projects |
+| `contracts:read` | Vendor contracts |
+| `compliance:read` | Compliance items |
+| `dashboard:read` | Dashboard summary stats |
+| `*:*` | All resources |
+
+## Security
+
+- The MCP server runs **locally** on your machine via stdio — no network server is exposed
+- Your API key is scoped to your organization only
+- All data access is read-only and logged in AssetLab's audit log
+- API keys can be revoked at any time in **Settings → API Keys**
+
+## Support
+
+Questions or issues? Email [support@assetlab.ca](mailto:support@assetlab.ca).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@assetlab/mcp-server",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "MCP server for AssetLab — connect Claude to your asset management data",
   "type": "module",
   "bin": {
@@ -13,7 +13,7 @@
     "start": "node dist/index.js"
   },
   "keywords": ["mcp", "assetlab", "asset-management", "claude"],
-  "license": "UNLICENSED",
+  "license": "MIT",
   "files": [
     "dist"
   ],