hdls Content
hdls Content is a headless, MCP-native headless content management backend. It manages content entries, types, and assets, operated entirely through named tools your AI assistant calls. It stands in for tools like Contentful, Sanity — same job, no UI to run.
💬 Just ask
"Create a new blog entry, then show me my published entries."
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 Content is organized
The headline entity is the entry — start there, then attach the rest to it. The entry_revision table is an append-only timeline — every change and note lands there and is never edited or deleted.
| Entity | Purpose | Relates to |
|---|---|---|
entry | A typed content document; field values live in fields per its content_type. | content_type |
content_type | Defines a content model (its fields) that entries are instances of. | — |
asset | Uploaded media (image, file) that entries reference; alt_text aids search and a11y. | — |
entry_revision | Append-only version history; each row snapshots an entry at a publish/save action. | entry |
Common workflows
Each line is one real sequence of tool calls — your assistant chains them for you.
- Move an entry through its lifecycle:
create_entry→publish_entry
Tools
Call these at https://hdls.ai/api/mcp/cms. 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_entry | Create a new entry. | title | content_type_id, slug, locale, status, body, fields |
Update & advance
| Tool | What it does | Required | Optional |
|---|---|---|---|
update_entry | Update an existing entry by id. | id | title, content_type_id, slug, locale, status |
publish_entry | Publish an entry. | id | — |
Find & read
| Tool | What it does | Required | Optional |
|---|---|---|---|
search_content | Search content by free-text and/or column filters (tenant-scoped, paginated). | — | search, filters, limit, orderBy |
list_types | Search types 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.
entry
| Field | Type | Required | Notes |
|---|---|---|---|
content_type_id | id | Links to a content_type. | |
title | text | Yes | Display name. |
slug | text | ||
locale | text | ||
status | text | Lifecycle state. | |
body | text | ||
fields | json | ||
author | text | ||
published_at | timestamp | ||
version | number | ||
data | json | Free-form JSON — custom fields live here. |
content_type
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Display name. |
api_id | text | Yes | Reference to a related record. |
description | text | ||
field_schema | json | ||
is_active | true / false | ||
data | json | Free-form JSON — custom fields live here. |
asset
| Field | Type | Required | Notes |
|---|---|---|---|
title | text | Display name. | |
filename | text | Yes | |
url | text | Yes | |
mime_type | text | ||
size_bytes | number | ||
alt_text | text | ||
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
entry_revisiontimeline is never edited or deleted — it's your audit trail.
Connect
On the concierge (https://hdls.ai/api/mcp), run install_product({ slug: "cms" }) (admin/owner) to enable it for your workspace, then add https://hdls.ai/api/mcp/cms 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_entry
Arguments: {
"title": "Welcome to our blog"
}