hdls Feedback
hdls Feedback is a headless, MCP-native product feedback & roadmap backend. It manages feature requests, votes, and roadmap, operated entirely through named tools your AI assistant calls. It stands in for tools like Canny, ProductBoard — same job, no UI to run.
💬 Just ask
"Create a request for Acme, then show me my requests."
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 Feedback is organized
The headline entity is the request — start there, then attach the rest to it. Records connect by reference: a vote links to a request; a comment links to a request. The activity table is an append-only timeline — every change and note lands there and is never edited or deleted.
| Entity | Purpose | Relates to |
|---|---|---|
request | A feature request/post on a board, with vote tally, roadmap status and semantic search. | board |
board | A feedback board grouping feature requests (e.g. Feature Requests, Bugs); also used as a roadmap lane. | — |
vote | A single upvote on a request; unique per voter so popularity is deduplicated. | request |
comment | A threaded discussion comment on a request (self-FK for replies); internal notes flagged. | request |
activity | Append-only timeline of status changes, merges, roadmap moves and other request events. | request |
Tools
Call these at https://hdls.ai/api/mcp/feedback. 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_request | Create a new request. | board_id, title | merged_into_id, body, author_name, author_email, status, roadmap_status |
Update & advance
| Tool | What it does | Required | Optional |
|---|---|---|---|
vote | Cast a vote on a record. | id | — |
merge_requests | Merge requests. | id | — |
set_roadmap_status | Set the roadmap status of a request. | id | roadmap_status |
Find & read
| Tool | What it does | Required | Optional |
|---|---|---|---|
search_requests | Search requests 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.
request
| Field | Type | Required | Notes |
|---|---|---|---|
board_id | id | Yes | Links to a board. |
merged_into_id | id | Reference to a related record. | |
title | text | Yes | Display name. |
body | text | ||
author_name | text | ||
author_email | text | ||
status | text | Lifecycle state. | |
roadmap_status | text | ||
priority | text | ||
vote_count | number | ||
comment_count | number | ||
data | json | Free-form JSON — custom fields live here. |
board
| Field | Type | Required | Notes |
|---|---|---|---|
key | text | Yes | |
name | text | Yes | Display name. |
description | text | ||
is_private | true / false | ||
data | json | Free-form JSON — custom fields live here. |
vote
| Field | Type | Required | Notes |
|---|---|---|---|
request_id | id | Yes | Links to a request. |
voter_id | text | Yes | Reference to a related record. |
weight | number | ||
data | json | Free-form JSON — custom fields live here. |
comment
| Field | Type | Required | Notes |
|---|---|---|---|
request_id | id | Yes | Links to a request. |
parent_id | id | Reference to a related record. | |
body | text | Yes | |
author_name | text | ||
is_internal | true / false | ||
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
activitytimeline is never edited or deleted — it's your audit trail.
Connect
On the concierge (https://hdls.ai/api/mcp), run install_product({ slug: "feedback" }) (admin/owner) to enable it for your workspace, then add https://hdls.ai/api/mcp/feedback 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_request
Arguments: {
"board_id": "<board-id>",
"title": "Add dark mode"
}