hdls Give
hdls Give is a headless, MCP-native fundraising & donor management backend. It manages donors, donations, and campaigns, operated entirely through named tools your AI assistant calls. It stands in for tools like Bloomerang, DonorPerfect — same job, no UI to run.
💬 Just ask
"Record a $100 donation from Ada and show me this month's total."
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 Give is organized
The headline entity is the donation — start there, then attach the rest to it. The interaction table is an append-only timeline — every change and note lands there and is never edited or deleted.
| Entity | Purpose | Relates to |
|---|---|---|
donation | A recorded gift from a donor, optionally attributed to a campaign. | donor, campaign |
donor | A supporter/constituent record; carries denormalised lifetime giving for fast donor screening. | — |
campaign | A fundraising campaign/appeal with a target goal and denormalised raised total. | — |
interaction | Append-only engagement timeline of touchpoints (calls, emails, meetings, notes) with a donor. | donor |
Common workflows
Each line is one real sequence of tool calls — your assistant chains them for you.
- Set up a donation end to end:
create_donor→record_donation→create_campaign
Tools
Call these at https://hdls.ai/api/mcp/donations. 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_donor | Create a new donor. | name | email, phone, donor_type, status, lifetime_value, last_gift_at |
create_campaign | Create a new campaign. | name | description, goal_amount, raised_amount, currency, status, starts_at |
Update & advance
| Tool | What it does | Required | Optional |
|---|---|---|---|
record_donation | Record a donation. | donor_id, amount | campaign_id, currency, method, frequency, status, is_anonymous |
log_interaction | Log interaction. | donor_id, body | kind, subject, author |
Find & read
| Tool | What it does | Required | Optional |
|---|---|---|---|
search_donations | Search donations 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.
donation
| Field | Type | Required | Notes |
|---|---|---|---|
donor_id | id | Yes | Links to a donor. |
campaign_id | id | Links to a campaign. | |
amount | numeric(14,2) | Yes | |
currency | text | ||
method | text | ||
frequency | text | ||
status | text | Lifecycle state. | |
is_anonymous | true / false | ||
designation | text | ||
received_at | timestamp | ||
data | json | Free-form JSON — custom fields live here. |
donor
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Display name. |
email | text | ||
phone | text | ||
donor_type | text | ||
status | text | Lifecycle state. | |
lifetime_value | numeric(14,2) | ||
last_gift_at | timestamp | ||
data | json | Free-form JSON — custom fields live here. |
campaign
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Display name. |
description | text | ||
goal_amount | numeric(14,2) | ||
raised_amount | numeric(14,2) | ||
currency | text | ||
status | text | Lifecycle state. | |
starts_at | date | ||
ends_at | date | ||
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
interactiontimeline is never edited or deleted — it's your audit trail.
Connect
On the concierge (https://hdls.ai/api/mcp), run install_product({ slug: "donations" }) (admin/owner) to enable it for your workspace, then add https://hdls.ai/api/mcp/donations 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_donor
Arguments: {
"name": "Acme Corp"
}