hdls Bookmarks
hdls Bookmarks is a headless, MCP-native bookmarks & link saving backend. It manages folders and saved links (url, title, description), operated entirely through named tools your AI assistant calls. It stands in for tools like Raindrop, Pocket — same job, no UI to run.
💬 Just ask
"Create a bookmark for Acme, then show me my bookmarks."
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 Bookmarks is organized
The headline entity is the bookmark — start there, then attach the rest to it.
| Entity | Purpose | Relates to |
|---|---|---|
bookmark | A saved link: url, title, description, tags; semantically searchable. | folder |
folder | Folder records. | — |
Common workflows
Each line is one real sequence of tool calls — your assistant chains them for you.
- Set up a bookmark end to end:
create_bookmark→create_folder
Tools
Call these at https://hdls.ai/api/mcp/bookmarks. 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_bookmark | Create a new bookmark. | url | folder_id, title, description, tags, created_by, data |
create_folder | Create a new folder. | name | parent_id |
Update & advance
| Tool | What it does | Required | Optional |
|---|---|---|---|
tag_bookmark | Tag a bookmark. | id | — |
Find & read
| Tool | What it does | Required | Optional |
|---|---|---|---|
search_bookmarks | Search bookmarks by free-text and/or column filters (tenant-scoped, paginated). | — | search, filters, limit, orderBy |
list_bookmarks | Search bookmarks 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.
bookmark
| Field | Type | Required | Notes |
|---|---|---|---|
folder_id | id | Links to a folder. | |
url | text | Yes | |
title | text | Display name. | |
description | text | ||
tags | list | Free-form labels. | |
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. |
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.
Connect
On the concierge (https://hdls.ai/api/mcp), run install_product({ slug: "bookmarks" }) (admin/owner) to enable it for your workspace, then add https://hdls.ai/api/mcp/bookmarks 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_bookmark
Arguments: {
"url": "example"
}