hdls Members
hdls Members is a headless, MCP-native memberships & community backend. It manages members, plans, and access, operated entirely through named tools your AI assistant calls. It stands in for tools like Memberful, Circle — same job, no UI to run.
💬 Just ask
"Create a member for Acme, then show me my members."
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 Members is organized
The headline entity is the member — start there, then attach the rest to it. Records connect by reference: a subscription links to a member and a plan; a payment links to a member and a subscription; an access_grant links to a member. The member_event table is an append-only timeline — every change and note lands there and is never edited or deleted.
| Entity | Purpose | Relates to |
|---|---|---|
member | A person who belongs to the community via one or more subscriptions. | — |
plan | A membership pricing tier (price + billing interval) members subscribe to. | — |
subscription | A member enrolment in a plan with billing-period and cancellation state. | member, plan |
payment | Billing transaction tied to a member/subscription (charge, failure, refund). | member, subscription |
access_grant | Entitlement giving a member access to a gated resource; revoked_at ends it. | member |
member_event | Append-only timeline of membership lifecycle and access changes for a member. | member |
Common workflows
Each line is one real sequence of tool calls — your assistant chains them for you.
- Set up a member end to end:
create_member→grant_access→log_event - Move a member through its lifecycle:
create_member→grant_access
Tools
Call these at https://hdls.ai/api/mcp/memberships. 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_member | Create a new member. | name | email, status, bio, tags, joined_at, data |
Update & advance
| Tool | What it does | Required | Optional |
|---|---|---|---|
manage_subscription | Manage a subscription. | id | — |
grant_access | Grant access. | id | — |
log_event | Log event. | id | — |
Find & read
| Tool | What it does | Required | Optional |
|---|---|---|---|
search_members | Search members 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.
member
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Display name. |
email | text | ||
status | text | Lifecycle state. | |
bio | text | ||
tags | list | Free-form labels. | |
joined_at | timestamp | ||
data | json | Free-form JSON — custom fields live here. |
plan
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Display name. |
description | text | ||
price_cents | number | ||
currency | text | ||
interval | text | ||
trial_days | number | ||
is_active | true / false | ||
data | json | Free-form JSON — custom fields live here. |
subscription
| Field | Type | Required | Notes |
|---|---|---|---|
member_id | id | Yes | Links to a member. |
plan_id | id | Links to a plan. | |
status | text | Lifecycle state. | |
started_at | timestamp | ||
current_period_end | timestamp | ||
cancel_at | timestamp | ||
cancelled_at | timestamp | ||
external_ref | text | ||
data | json | Free-form JSON — custom fields live here. |
payment
| Field | Type | Required | Notes |
|---|---|---|---|
member_id | id | Yes | Links to a member. |
subscription_id | id | Links to a subscription. | |
amount_cents | number | ||
currency | text | ||
status | text | Lifecycle state. | |
external_ref | text | ||
paid_at | timestamp | ||
data | json | Free-form JSON — custom fields live here. |
access_grant
| Field | Type | Required | Notes |
|---|---|---|---|
member_id | id | Yes | Links to a member. |
resource_type | text | ||
resource_ref | text | Yes | |
granted_at | timestamp | ||
revoked_at | timestamp | ||
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
member_eventtimeline is never edited or deleted — it's your audit trail.
Connect
On the concierge (https://hdls.ai/api/mcp), run install_product({ slug: "memberships" }) (admin/owner) to enable it for your workspace, then add https://hdls.ai/api/mcp/memberships 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_member
Arguments: {
"name": "Acme Corp"
}