hdls Tasks

hdls Tasks is a headless, MCP-native task & project management backend. It manages tasks, projects, and comments, operated entirely through named tools your AI assistant calls. It stands in for tools like Asana, Jira, Linear — same job, no UI to run.

💬 Just ask

"Add a task to follow up with Acme by Friday and show me what's due this week."

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 Tasks is organized

The headline entity is the task — start there, then attach the rest to it. Records connect by reference: a task_label links to a task and a label. The comment table is an append-only timeline — every change and note lands there and is never edited or deleted.

Entity	Purpose	Relates to
`task`	A unit of work; nests into subtasks via parent_id and rolls up to a project.	`project`
`project`	Container grouping related tasks; the top-level unit of planning.	—
`label`	Reusable label/tag applied to tasks via the task_label join.	—
`task_label`	Join table assigning labels to tasks (many-to-many).	`task`, `label`
`comment`	Append-only discussion timeline on a task; semantically searchable across the workspace.	`task`

Common workflows

Each line is one real sequence of tool calls — your assistant chains them for you.

Set up a task end to end: create_task → assign_task
Move a task through its lifecycle: create_task → update_status

Tools

Call these at https://hdls.ai/api/mcp/tasks. 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_task`	Create a new task.	`title`	`project_id`, `parent_id`, `description`, `status`, `priority`, `assignee`

Update & advance

Tool	What it does	Required	Optional
`assign_task`	Assign task to a person or record.	`title`	`project_id`, `parent_id`, `description`, `status`, `priority`, `assignee`
`update_status`	Update the status of a task by `id`.	`id`	`status`

Find & read

Tool	What it does	Required	Optional
`list_tasks`	Search tasks by free-text and/or column filters (tenant-scoped, paginated).	—	`search`, `filters`, `limit`, `orderBy`
`semantic_search_comments`	Find search comments by meaning, not just keywords.	—	`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.

`task`

Field	Type	Required	Notes
`project_id`	id		Links to a `project`.
`parent_id`	id		Reference to a related record.
`title`	text	Yes	Display name.
`description`	text
`status`	text		Lifecycle state.
`priority`	text
`assignee`	text
`due_date`	date
`position`	number
`data`	json		Free-form JSON — custom fields live here.

`project`

Field	Type	Required	Notes
`name`	text	Yes	Display name.
`description`	text
`status`	text		Lifecycle state.
`owner`	text
`start_date`	date
`due_date`	date
`data`	json		Free-form JSON — custom fields live here.

`label`

Field	Type	Required	Notes
`name`	text	Yes	Display name.
`color`	text
`data`	json		Free-form JSON — custom fields live here.

`task_label`

Field	Type	Required	Notes
`task_id`	id	Yes	Links to a `task`.
`label_id`	id	Yes	Links to a `label`.

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 comment timeline is never edited or deleted — it's your audit trail.

Connect

On the concierge (https://hdls.ai/api/mcp), run install_product({ slug: "tasks" }) (admin/owner) to enable it for your workspace, then add https://hdls.ai/api/mcp/tasks 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_task
Arguments: {
  "title": "Follow up with Acme"
}

See All products · Connect your assistant · Automation