hdls Drive
hdls Drive is a headless, MCP-native file storage & sharing backend. It manages folders, files, shares, and versions, operated entirely through named tools your AI assistant calls. It stands in for tools like Dropbox, OneDrive, Google Drive — same job, no UI to run.
💬 Just ask
"Create a folder for Acme, then show me my files."
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 Drive is organized
The headline entity is the file — start there, then attach the rest to it. Records connect by reference: a share links to a file and a folder. The file_version table is an append-only timeline — every change and note lands there and is never edited or deleted.
| Entity | Purpose | Relates to |
|---|---|---|
file | File metadata; bytes live in object storage at storage_key. | folder |
folder | Folder hierarchy (OneDrive-style). | — |
share | Shares a file or folder with a tenant/user/agent/public, optionally via link token. | file, folder |
file_version | Append-only version history per file. | file |
Common workflows
Each line is one real sequence of tool calls — your assistant chains them for you.
- Set up a file end to end:
create_folder→upload_file - Move a file through its lifecycle:
create_folder→move_file
Tools
Call these at https://hdls.ai/api/mcp/drive. 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_folder | Create a new folder. | name | parent_id, path, data |
Update & advance
| Tool | What it does | Required | Optional |
|---|---|---|---|
upload_file | Upload a file. | name | folder_id, mime_type, size_bytes, storage_key, checksum, created_by |
share_file | Share a file. | id | — |
move_file | Move a file. | id | — |
Find & read
| Tool | What it does | Required | Optional |
|---|---|---|---|
search_files | Search files by free-text and/or column filters (tenant-scoped, paginated). | — | search, filters, limit, orderBy |
list_file_versions | Search file versions 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.
file
| Field | Type | Required | Notes |
|---|---|---|---|
folder_id | id | Links to a folder. | |
name | text | Yes | Display name. |
mime_type | text | ||
size_bytes | number | ||
storage_key | text | ||
checksum | text | ||
data | json | Free-form JSON — custom fields live here. | |
created_by | text |
folder
| Field | Type | Required | Notes |
|---|---|---|---|
parent_id | id | Reference to a related record. | |
name | text | Yes | Display name. |
path | text | ||
data | json | Free-form JSON — custom fields live here. |
share
| Field | Type | Required | Notes |
|---|---|---|---|
file_id | id | Links to a file. | |
folder_id | id | Links to a folder. | |
audience | text | Yes | |
audience_id | text | Reference to a related record. | |
scope | text | ||
link_token | text | ||
expires_at | timestamp |
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
file_versiontimeline is never edited or deleted — it's your audit trail.
Connect
On the concierge (https://hdls.ai/api/mcp), run install_product({ slug: "drive" }) (admin/owner) to enable it for your workspace, then add https://hdls.ai/api/mcp/drive 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_folder
Arguments: {
"name": "Acme Corp"
}