[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# DonorPerfect API and MCP server

> DonorPerfect has an XML API with read and write access to donors, gifts, pledges and contacts, and no official MCP server (checked 23 Oct 2026). Calls are raw procedure or SELECT requests, and an admin generates the key under Settings > User Management > API Self Service.

Fundraising CRM for nonprofits: donor records, gifts and pledges, receipts and thank-yous, contacts, online forms and SmartActions.

## What is the DonorPerfect API?

Cotlet's DonorPerfect API exposes 14 endpoints for your own DonorPerfect account: search donors, get donor, list gifts, list pledges, list contacts, list codes, list gifts waiting for a receipt, create donor, update donor, add gift, create pledge, apply pledge payment, add contact and send thank-you email. The search_donors endpoint returns finds donors and organizations by last name, organization name, donor ID or keyword. Each endpoint takes simple JSON inputs like donor_id, limit or cursor and works both as an operation of the donorperfect_read or donorperfect_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Creators & communities](https://cotlet.dev/integrations/category/creators-communities.md)
- **Endpoints:** 14 (7 read, 7 write)
- **Updated:** 2026-10-20

DonorPerfect has an XML API with read and write access to donors, gifts, pledges and contacts, and no official MCP server (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for DonorPerfect with 14 endpoints (7 read, 7 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does DonorPerfect have an official API?

DonorPerfect has an XML API with read and write access to donors, gifts, pledges and contacts, and no official MCP server (checked 23 Oct 2026). Calls are raw procedure or SELECT requests, and an admin generates the key under Settings > User Management > API Self Service.

| Task | DonorPerfect official | Cotlet |
|---|---|---|
| Search and read donors | Yes: dp_donorsearch and a SELECT on the donor table | Yes |
| Create and update donors | Yes: dp_savedonor | Yes |
| Add gifts | Yes: dp_savegift, with the codes passed as parameters | Yes |
| Create pledges and apply pledge payments | Yes: dp_savepledge, then dp_savegift with the pledge gift ID in plink | Yes |
| Add contacts | Yes: dp_savecontact | Yes |
| Read code lists | Partly: A SELECT on DPCODES, 500 rows at a time | Yes |
| Send a thank-you email from a gift | No | Yes |
| Use it from an AI agent over MCP | No | Yes |

Sources: [DonorPerfect Online XML API Documentation (v7.2, 19 Jun 2026)](https://softerware-uploads.s3.amazonaws.com/community/donorperfect/DPO_XML_API_Documentation.pdf), [DonorPerfect release notes](https://www.donorperfect.com/clients/release-notes/), [DonorPerfect: Managing pledges](https://www.donorperfect.com/video/managing-pledges-donorperfect/), [DonorPerfect: The Power of Thank Yous](https://www.donorperfect.com/video/the-power-of-thank-yous/)

## Quick reference

```text
DonorPerfect has an XML API with read and write access to donors, gifts, pledges and contacts, and no official MCP server (checked 23 Oct 2026). Calls are raw procedure or SELECT requests, and an admin generates the key under Settings > User Management > API Self Service.
Cotlet provides a hosted MCP server and REST API for DonorPerfect: 14 tools (7 read, 7 write).
Access       Sign up at https://cotlet.dev/app/signup?app=donorperfect, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    donorperfect_read, donorperfect_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/donorperfect, each operation at its own route, e.g. POST /api/v1/donorperfect/donors/{donor_id}/gifts
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   search_donors, get_donor, list_gifts, list_pledges, list_contacts, list_codes, list_receipts_due, create_donor, update_donor, add_gift, create_pledge, apply_pledge_payment, add_contact, send_thank_you_email
Confirm      create_donor, update_donor, add_gift, create_pledge, apply_pledge_payment, send_thank_you_email (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/donorperfect-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=donorperfect, requests DonorPerfect in the Cotlet console and creates an API key there.
2. The user signs in to DonorPerfect once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables DonorPerfect for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted DonorPerfect server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to DonorPerfect in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get DonorPerfect only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no DonorPerfect login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following DonorPerfect's terms; Cotlet is not affiliated with DonorPerfect.
```

## What can an AI agent do in DonorPerfect?

Cotlet is best for nonprofit development staff who are not developers and want an AI agent to enter gifts, apply pledge payments and log donor calls in DonorPerfect without running or fixing a server.

- **[Enter gifts from a deposit list](https://cotlet.dev/integrations/donorperfect-api-mcp-server/enter-gifts-from-a-deposit-list.md)** (runs: weekly): "Here is this week's deposit list. For each line find the donor in DonorPerfect, add the gift with the codes I gave, and leave anything unclear for me." → `search_donors`, `list_codes`, `create_donor`, `add_gift`, `list_gifts`
- **[Apply payments to pledges](https://cotlet.dev/integrations/donorperfect-api-mcp-server/apply-pledge-payments.md)** (runs: weekly): "This payroll file lists payments per employee. For each one find the open pledge in DonorPerfect and apply the payment. Leave any line where the amount or the pledge is unclear." → `search_donors`, `list_pledges`, `apply_pledge_payment`
- **[Log donor calls as contacts](https://cotlet.dev/integrations/donorperfect-api-mcp-server/log-donor-calls-in-contacts.md)** (runs: daily): "Here are my notes from today's donor calls. For each one add a contact in DonorPerfect with the right activity code, today's date and me as the owner. Ask me about any note you cannot place." → `list_codes`, `search_donors`, `list_contacts`, `add_contact`
- **Thank new donors by email** (runs: daily): "List the gifts waiting for a receipt in DonorPerfect. For donors whose delivery preference is Email or Email and Letter, send the thank-you email. List the letter donors for me." → `list_receipts_due`, `get_donor`, `send_thank_you_email`
- **Update donor details from a returned-mail list** (runs: weekly): "Here are the corrected addresses from our returned mail. Find each donor in DonorPerfect and update their address. Leave any donor with more than one match." → `search_donors`, `get_donor`, `update_donor`

## Can DonorPerfect automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a DonorPerfect connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to enter gifts from a deposit list, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/donorperfect/donors/search. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/donorperfect/donors/search with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 14 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to DonorPerfect.

### search_donors

Finds donors and organizations by last name, organization name, donor ID or keyword. Access: read. REST: `GET /api/v1/donorperfect/donors/search`. MCP: `donorperfect_read → search_donors`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | What to look for. |
| `by` | enum | no | last_name, organization, donor_id or keyword. Default: last_name. |
| `limit` | integer | no | How many rows to return per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Runs the Lookup on the Search screen and returns the matches in the order DonorPerfect lists them. Each row has the donor ID, the type (individual or organization), the name, the city and the email, enough to tell two people with the same name apart. Use donor_id in the other tools. An empty list means no match; create_donor adds a record.

Example response:

```json
{
  "donors": [
    {
      "donor_id": 48213,
      "type": "individual",
      "name": "Dana Whitfield",
      "city": "Portland",
      "email": "dana.whitfield@example.org"
    },
    {
      "donor_id": 50122,
      "type": "individual",
      "name": "Dana Whitfield",
      "city": "Salem",
      "email": "dwhitfield@example.com"
    }
  ],
  "next_cursor": null
}
```

### get_donor

The donor record: name, address, email and phone. Access: read. REST: `GET /api/v1/donorperfect/donors/{donor_id}`. MCP: `donorperfect_read → get_donor`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `donor_id` | integer | yes | Donor ID from search_donors. |

Opens the donor record and returns its demographic fields: name, address, email and phone. Use it to check a match from search_donors before you write to the record. It does not return gifts, pledges or contacts; list_gifts, list_pledges and list_contacts do.

Example response:

```json
{
  "donor_id": 48213,
  "type": "individual",
  "first_name": "Dana",
  "last_name": "Whitfield",
  "email": "dana.whitfield@example.org",
  "phone": "555-0142",
  "address": "120 Example Street",
  "city": "Portland",
  "state": "OR",
  "zip": "97201"
}
```

### list_gifts

Gifts on a donor record with date, amount and codes. Access: read. REST: `GET /api/v1/donorperfect/donors/{donor_id}/gifts`. MCP: `donorperfect_read → list_gifts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `donor_id` | integer | yes | Donor ID from search_donors. |
| `limit` | integer | no | How many rows to return per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the gifts on one donor record in the order the record lists them, with the gift ID, date, amount, gift type, general ledger, solicitation, sub solicitation, thank you letter and reference. Pass next_cursor back as cursor for the next page. Pledge payments appear as gifts too. Use it to check what a donor gave before you thank or call them.

Example response:

```json
{
  "gifts": [
    {
      "gift_id": 90417,
      "date": "2026-10-21",
      "amount": 250,
      "gift_type": "Check",
      "gl_code": "GEN",
      "solicitation": "FALLAPPEAL",
      "sub_solicitation": null,
      "thank_you_letter": "STANDARD",
      "reference": "4471"
    },
    {
      "gift_id": 88034,
      "date": "2026-03-02",
      "amount": 100,
      "gift_type": "Credit Card",
      "gl_code": "GEN",
      "solicitation": "SPRINGAPPEAL",
      "sub_solicitation": null,
      "thank_you_letter": "STANDARD",
      "reference": null
    }
  ],
  "next_cursor": null
}
```

### list_pledges

Pledges on a donor record with total, payments, billing amount and frequency. Access: read. REST: `GET /api/v1/donorperfect/donors/{donor_id}/pledges`. MCP: `donorperfect_read → list_pledges`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `donor_id` | integer | yes | Donor ID from search_donors. |

Returns the pledges on the Pledges tab of one donor record: pledge ID, pledge date, start date, total, number of payments, billing amount and frequency. A recurring pledge with no end has a total of 0 and only a billing amount. Use pledge_id and billing_amount with apply_pledge_payment.

Example response:

```json
{
  "pledges": [
    {
      "pledge_id": 77120,
      "pledge_date": "2026-01-05",
      "start_date": "2026-02-01",
      "total": 1200,
      "payments": 12,
      "billing_amount": 100,
      "frequency": "Monthly",
      "gl_code": "GEN",
      "solicitation": "PAYROLL"
    }
  ]
}
```

### list_contacts

Contacts logged on a donor record: date, activity code, owner and comments. Access: read. REST: `GET /api/v1/donorperfect/donors/{donor_id}/contacts`. MCP: `donorperfect_read → list_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `donor_id` | integer | yes | Donor ID from search_donors. |
| `limit` | integer | no | How many rows to return per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the contacts on one donor record with the contact ID, date, activity code, the Assigned To value and the comments, in the order the record lists them. Use it before add_contact to avoid a duplicate entry, or to read the history of a donor before a call.

Example response:

```json
{
  "contacts": [
    {
      "contact_id": 31502,
      "date": "2026-09-14",
      "activity_code": "EMAIL",
      "assigned_to": "KHALL",
      "notes": "Sent the gala invitation."
    }
  ],
  "next_cursor": null
}
```

### list_codes

The codes your organization uses for gifts, thank-you letters and contacts. Access: read. REST: `GET /api/v1/donorperfect/codes`. MCP: `donorperfect_read → list_codes`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `field` | enum | yes | solicitation, general_ledger, gift_type, thank_you_letter, activity_code or by_whom. |

Returns the code and its description for one code list from Settings > Code Maintenance. field picks the list. The codes belong to your organization, so the answer differs from one DonorPerfect account to the next. add_gift, create_pledge and add_contact take the code, not the description.

Example response:

```json
{
  "field": "thank_you_letter",
  "codes": [
    {
      "code": "STANDARD",
      "description": "Standard thank you"
    },
    {
      "code": "MAJOR",
      "description": "Major donor thank you"
    }
  ]
}
```

### list_receipts_due

Gifts the Receipts screen lists for acknowledgement, with each delivery preference. Access: read. REST: `GET /api/v1/donorperfect/receipts-dues`. MCP: `donorperfect_read → list_receipts_due`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `limit` | integer | no | How many rows to return per page. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the gifts that the Receipts, Acknowledgements and Notifications screen lists for receipting: gift ID, donor, date, amount and the receipt delivery preference of the gift (Email, Letter or Email and Letter). It sends nothing and marks nothing as receipted. Pass next_cursor back as cursor for the next page.

Example response:

```json
{
  "gifts": [
    {
      "gift_id": 90417,
      "donor_id": 48213,
      "donor": "Dana Whitfield",
      "date": "2026-10-21",
      "amount": 250,
      "delivery": "Email"
    },
    {
      "gift_id": 90421,
      "donor_id": 50877,
      "donor": "Mark Ellis",
      "date": "2026-10-21",
      "amount": 100,
      "delivery": "Letter"
    }
  ],
  "next_cursor": null
}
```

### create_donor

Adds an individual or an organization as a new donor record. Access: write, asks the user first. REST: `POST /api/v1/donorperfect/donors`. MCP: `donorperfect_write → create_donor`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | enum | yes | individual or organization. |
| `last_name` | string | no | Required for an individual. |
| `first_name` | string | no | First name of an individual. |
| `organization` | string | no | Required for an organization. |
| `email` | string | no | Email address. |
| `phone` | string | no | Phone number. |
| `address` | string | no | Street address. |
| `city` | string | no | City. |
| `state` | string | no | State or province. |
| `zip` | string | no | ZIP or postal code. |

Adds a record the way Add Individual or Add Organization does on the Search screen. An individual needs a last name, an organization needs its name. It returns the new donor_id. It does not check for duplicates: run search_donors first, and use Duplicate Maintenance under Utilities if one slips in. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "donor_id": 52004,
  "type": "individual",
  "name": "Priya Nair",
  "status": "created"
}
```

### update_donor

Changes the address, email or phone on a donor record. Access: write, asks the user first. REST: `PATCH /api/v1/donorperfect/donors/{donor_id}`. MCP: `donorperfect_write → update_donor`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `donor_id` | integer | yes | Donor ID from search_donors. |
| `email` | string | no | New email address. |
| `phone` | string | no | New phone number. |
| `address` | string | no | New street address. |
| `city` | string | no | New city. |
| `state` | string | no | New state or province. |
| `zip` | string | no | New ZIP or postal code. |

Saves the fields you pass on the donor record and leaves the others as they are. It changes demographic fields only: gifts, pledges and contacts are not touched. It returns the record as saved, so you can compare it with what you sent. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "donor_id": 48213,
  "address": "45 Sample Avenue",
  "city": "Portland",
  "state": "OR",
  "zip": "97205",
  "status": "saved"
}
```

### add_gift

Saves one gift on a donor record with its codes. Access: write, asks the user first. REST: `POST /api/v1/donorperfect/donors/{donor_id}/gifts`. MCP: `donorperfect_write → add_gift`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `donor_id` | integer | yes | Donor ID from search_donors. |
| `date` | date | yes | Gift date. |
| `amount` | number | yes | Gift amount. |
| `gift_type` | string | yes | Gift type code from list_codes. |
| `gl_code` | string | no | General ledger code from list_codes. |
| `solicitation` | string | no | Solicitation code from list_codes. |
| `sub_solicitation` | string | no | Sub solicitation code. |
| `campaign` | string | no | Campaign code. |
| `thank_you_letter` | string | no | Thank you letter code from list_codes. |
| `reference` | string | no | Reference, such as a check number. |
| `memo` | string | no | Comments saved with the gift. |

Saves one gift on the donor record, like Add Gift in the app. Codes are DonorPerfect codes from list_codes, not descriptions. If your organization has a SmartAction on new gifts, DonorPerfect runs it when the gift is saved. If the donor has an open pledge, DonorPerfect asks whether to apply the gift as a pledge payment; this tool answers no, so use apply_pledge_payment for pledge payments. It returns the gift_id. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "gift_id": 90417,
  "donor_id": 48213,
  "date": "2026-10-21",
  "amount": 250,
  "gift_type": "Check",
  "solicitation": "FALLAPPEAL",
  "thank_you_letter": "STANDARD",
  "status": "saved"
}
```

### create_pledge

Adds a fixed or open-ended recurring pledge to a donor record. Access: write, asks the user first. REST: `POST /api/v1/donorperfect/donors/{donor_id}/pledges`. MCP: `donorperfect_write → create_pledge`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `donor_id` | integer | yes | Donor ID from search_donors. |
| `pledge_date` | date | yes | When the donor made the commitment. |
| `start_date` | date | yes | When payments begin. |
| `frequency` | string | yes | As DonorPerfect lists it, for example monthly, quarterly, annually or bi-weekly. |
| `total` | number | no | Pledge total. Leave at 0 for an open-ended recurring pledge. |
| `payments` | integer | no | Number of payments of a fixed pledge. |
| `billing_amount` | number | no | Amount of each payment. Needed when total is 0. |
| `gl_code` | string | no | General ledger code from list_codes. |
| `solicitation` | string | no | Solicitation code from list_codes. |
| `thank_you_letter` | string | no | Thank you letter code from list_codes. |

Adds a pledge on the Pledges tab. For a fixed pledge pass total and payments, and the billing amount follows. For an open-ended recurring pledge leave total at 0 and pass billing_amount. The number of payments is set when the pledge is created. It returns the pledge_id for apply_pledge_payment. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "pledge_id": 77450,
  "donor_id": 52004,
  "pledge_date": "2026-10-22",
  "start_date": "2026-11-01",
  "total": 600,
  "payments": 6,
  "billing_amount": 100,
  "frequency": "Monthly",
  "status": "saved"
}
```

### apply_pledge_payment

Applies a payment to a pledge with the pledge's own codes. Access: write, asks the user first. REST: `POST /api/v1/donorperfect/donors/{donor_id}/pledges/{pledge_id}/payment/apply`. MCP: `donorperfect_write → apply_pledge_payment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `donor_id` | integer | yes | Donor ID from search_donors. |
| `pledge_id` | integer | yes | Pledge ID from list_pledges. |
| `amount` | number | yes | Payment amount. |
| `date` | date | no | Payment date. Default: the date DonorPerfect fills in. |

Uses Apply payment on the pledge, so the gift data comes from the pledge and nothing is edited by hand. It saves one payment of the amount you give and returns its gift_id. It does not change the pledge or its Schedule of payments. Take pledge_id from list_pledges. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "payment_gift_id": 91002,
  "donor_id": 51907,
  "pledge_id": 77120,
  "amount": 100,
  "date": "2026-10-22",
  "status": "applied"
}
```

### add_contact

Logs a contact on a donor record with an activity code and an owner. Access: write. REST: `POST /api/v1/donorperfect/donors/{donor_id}/contacts`. MCP: `donorperfect_write → add_contact`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `donor_id` | integer | yes | Donor ID from search_donors. |
| `activity_code` | string | yes | Activity code from list_codes. |
| `date` | date | yes | Date of the contact. |
| `notes` | string | no | Comments saved with the contact. |
| `assigned_to` | string | no | By Whom code from list_codes. |

Adds one contact to the donor record, like entering a contact in the app: an activity code, the date, who it is assigned to and the comments. The codes come from list_codes. It sends nothing to the donor and changes no other record, so it does not ask for your OK by default. Run list_contacts first to avoid a duplicate.

Example response:

```json
{
  "contact_id": 31550,
  "donor_id": 48213,
  "activity_code": "PHONE",
  "date": "2026-10-22",
  "assigned_to": "KHALL",
  "notes": "Called about the gala. Wants to host a table; send sponsor levels by Friday.",
  "status": "saved"
}
```

### send_thank_you_email

Sends the thank-you email for one gift to the donor. Access: write, asks the user first. REST: `POST /api/v1/donorperfect/donors/{donor_id}/thank-you-emails`. MCP: `donorperfect_write → send_thank_you_email`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `donor_id` | integer | yes | Donor ID from search_donors. |
| `gift_id` | integer | yes | Gift ID from list_receipts_due or list_gifts. |

Uses Thank Donor > Send an Email on the gift record. It works for donors whose delivery preference is Email or Email and Letter; for any other donor it stops and reports the preference. Letters are merged in Word with Instant Merge and are not part of this tool. It returns the address the email went to. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "gift_id": 90417,
  "donor_id": 48213,
  "to": "dana.whitfield@example.org",
  "status": "sent"
}
```

## How do I connect DonorPerfect to Claude Code, Codex or Cursor?

Connecting DonorPerfect takes three steps: sign up, sign in to DonorPerfect once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect DonorPerfect to your agent.

1. **Create an account** Sign up and add DonorPerfect in the console. Your API key is there too.

2. **Sign in to DonorPerfect in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to DonorPerfect there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the DonorPerfect tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Here is this week's deposit list. For each line find the donor in DonorPerfect, add the gift with the codes I gave, and leave anything unclear for me.
```

### Call DonorPerfect from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/donorperfect with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/donorperfect/donors/48213/gifts \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date":"2026-10-21","amount":250,"gift_type":"Check","gl_code":"GEN","solicitation":"FALLAPPEAL","thank_you_letter":"STANDARD","reference":"4471"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "gift_id": 90417,
  "donor_id": 48213,
  "date": "2026-10-21",
  "amount": 250,
  "gift_type": "Check",
  "solicitation": "FALLAPPEAL",
  "thank_you_letter": "STANDARD",
  "status": "saved"
}
```

## Why use Cotlet for DonorPerfect?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to DonorPerfect yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When DonorPerfect changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect DonorPerfect to Cotlet?

Yes. You sign in to DonorPerfect yourself, in your own Cloud Browser, and we never save your password. Your agents only get DonorPerfect once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official DonorPerfect integration?**

No, Cotlet is independent of DonorPerfect. DonorPerfect's own API is too limited for this work. Cotlet works through your own DonorPerfect account, the way you use DonorPerfect in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to DonorPerfect in your console: your agents lose access at once and you stay signed in. Signing out of DonorPerfect in the browser works too, and Reset browser deletes the whole profile.

## Is there a DonorPerfect MCP server on GitHub?

The realistic option today is the XML API: a developer writes and hosts the calls, using a key an admin generates in DonorPerfect. Open-source MCP servers for DonorPerfect are not a common choice. Cotlet hosts a ready MCP server and REST API that work in your own DonorPerfect login, and our team keeps them working.

|  | XML API | Cotlet |
|---|---|---|
| Setup | An admin adds an API user and generates a key; a developer writes procedure and SELECT calls | Sign up, sign in to DonorPerfect once, add one MCP server or API key |
| When DonorPerfect changes | Changes are listed in the release notes; you update your code | Our team tests it daily and fixes it for you; failed calls are free |
| Your DonorPerfect access | The key has full data access whatever the user's permissions say | Your own user in your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | The key keeps working when the user's password expires | Your Cloud Browser keeps you signed in; if DonorPerfect asks for multi-factor sign-in again, your agent gets a link and you complete it. Cotlet never bypasses it |
| Upkeep | You host, monitor and fix the code, and page through results 500 rows at a time | Nothing to host or update |
| Where it runs | Wherever you run your code | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Needs an API-enabled DonorPerfect setup (ask your Account Manager) and developer time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when DonorPerfect changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the DonorPerfect API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the DonorPerfect API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 10 credits (about $0.04 to $0.06), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own DonorPerfect account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to DonorPerfect yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get DonorPerfect only after you enable it. When DonorPerfect signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to DonorPerfect, sign out of DonorPerfect in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **DonorPerfect's terms:** You use your own DonorPerfect account and stay responsible for following DonorPerfect's terms. Cotlet is independent and not affiliated with DonorPerfect. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open DonorPerfect in the console and press Request access. Then you create your API key and connect DonorPerfect there.

**Do I need to be technical?**

No. You sign in to DonorPerfect once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect DonorPerfect to Cotlet?**

Yes. You sign in to DonorPerfect yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get DonorPerfect once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My DonorPerfect sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your DonorPerfect cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through DonorPerfect's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. DonorPerfect sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no DonorPerfect login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

DonorPerfect offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need a DonorPerfect API key for Cotlet?**

No. Cotlet works in your own DonorPerfect login and does not use the XML API. DonorPerfect generates API keys under Settings > User Management > API Self Service, and Cotlet needs none. What your user can open in DonorPerfect still counts.

**Can it print or merge thank-you letters?**

No. DonorPerfect merges letter receipts in Microsoft Word with Instant Merge, which Cotlet does not run. send_thank_you_email sends the email for donors whose delivery preference is Email or Email and Letter, and list_receipts_due shows which donors get a letter.

**What is not covered?**

Tributes and notifications, Batch Gift Entry, soft credits, split gifts, SmartAction setup, reports and mail merge are not tools. Gifts are entered one at a time on the donor record. DonorPerfect can ask for multi-factor sign-in (release notes, Sep 2026); you complete that step yourself.

**Can my agent post or send messages in DonorPerfect without asking me?**

No. Every call to create_donor, update_donor, add_gift, create_pledge, apply_pledge_payment or send_thank_you_email waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. add_contact runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the DonorPerfect API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/donorperfect from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.