hdls Assets
hdls Assets is a headless, MCP-native asset tracking backend. It manages assets, assignments, and maintenance, operated entirely through named tools your AI assistant calls. It stands in for tools like Asset Panda, Snipe-IT — same job, no UI to run.
💬 Just ask
"Create an asset for Acme, then show me my assets."
You don't call these tools yourself — just tell your assistant in plain English. Everything below is the reference for when you (or your assistant) want the exact details.
How Assets is organized
The headline entity is the asset — start there, then attach the rest to it. Records connect by reference: an assignment links to an asset; a maintenance links to an asset. The asset_history table is an append-only timeline — every change and note lands there and is never edited or deleted.
| Entity | Purpose | Relates to |
|---|---|---|
asset | A tracked physical asset (tag, serial, model) with lifecycle status and condition. | — |
assignment | A checkout/assignment of an asset to a person, department, location, or project. | asset |
maintenance | A maintenance record (repair/preventive/inspection/calibration/upgrade) against an asset. | asset |
asset_history | Append-only lifecycle event log for an asset (checkout, checkin, maintenance, audit, moves). | asset |
Common workflows
Each line is one real sequence of tool calls — your assistant chains them for you.
- Set up an asset end to end:
create_asset→assign_asset→log_maintenance
Tools
Call these at https://hdls.ai/api/mcp/assets. Required fields you must supply; optional fields refine the call. You never pass tenant_id — it is stamped server-side.
Create
| Tool | What it does | Required | Optional |
|---|---|---|---|
create_asset | Create a new asset. | name | asset_tag, description, category, manufacturer, model, serial_number |
Update & advance
| Tool | What it does | Required | Optional |
|---|---|---|---|
assign_asset | Assign asset to a person or record. | name | asset_tag, description, category, manufacturer, model, serial_number |
log_maintenance | Log maintenance. | asset_id, title | description, maint_type, status, cost, currency, performed_by |
checkout_asset | Check out an asset. | id | — |
Find & read
| Tool | What it does | Required | Optional |
|---|---|---|---|
search_assets | Search assets by free-text and/or column filters (tenant-scoped, paginated). | — | search, filters, limit, orderBy |
Field lists come from the product's live schema and are embedded in each tool's own description — read the tool description for the exact, current fields.
Field reference
Every field you can set on each record. Custom fields you add live alongside these in data.
asset
| Field | Type | Required | Notes |
|---|---|---|---|
asset_tag | text | ||
name | text | Yes | Display name. |
description | text | ||
category | text | ||
manufacturer | text | ||
model | text | ||
serial_number | text | ||
status | text | Lifecycle state. | |
condition | text | ||
location | text | ||
purchase_cost | numeric(14,2) | ||
currency | text | ||
purchased_on | date | ||
warranty_until | date | ||
data | json | Free-form JSON — custom fields live here. |
assignment
| Field | Type | Required | Notes |
|---|---|---|---|
asset_id | id | Yes | Links to an asset. |
assignee | text | Yes | |
assignee_type | text | ||
status | text | Lifecycle state. | |
checked_out_at | timestamp | ||
due_at | timestamp | ||
returned_at | timestamp | ||
note | text | ||
data | json | Free-form JSON — custom fields live here. |
maintenance
| Field | Type | Required | Notes |
|---|---|---|---|
asset_id | id | Yes | Links to an asset. |
title | text | Yes | Display name. |
description | text | ||
maint_type | text | ||
status | text | Lifecycle state. | |
cost | numeric(14,2) | ||
currency | text | ||
performed_by | text | ||
scheduled_for | date | ||
completed_at | timestamp | ||
data | json | Free-form JSON — custom fields live here. |
Tailor it with custom fields
Add fields without a schema change. add_custom_field defines one, list_custom_fields shows what's defined, and promote_custom_field (admin) shares a personal field with the whole workspace. The value lives in each row's data (JSON) and is set and read through the normal record tools. See Products, tools & custom fields for the full model.
Roles & safety
- Tenant isolation is automatic. Your credential is pinned to one workspace; you never pass
tenant_id, and you can only ever see your own data (enforced by Postgres row-level security). - Role-gated. Permissions run
reader < member < admin < owner. Installing a product and promoting a custom field workspace-wide need admin/owner. - History is append-only. The
asset_historytimeline is never edited or deleted — it's your audit trail.
Connect
On the concierge (https://hdls.ai/api/mcp), run install_product({ slug: "assets" }) (admin/owner) to enable it for your workspace, then add https://hdls.ai/api/mcp/assets as a connector in your assistant — see Connect your assistant.
A worked example
The literal call your assistant makes when you ask it to create the headline record:
Tool: create_asset
Arguments: {
"name": "Acme Corp"
}