DonorPerfect MCP Server
Donors, gifts, pledges and thank-yous in DonorPerfect, worked by your agent.
Hosted MCP Server
npx add-mcp 'https://cotlet.dev/mcp/v1/donorperfect'Installs into Claude Code, Codex, Cursor and more
Documentation
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
DonorPerfect API and MCP server: Let your AI agent enter gifts and thank donors in DonorPerfect.
DonorPerfect has no MCP server of its own (checked 27 Oct 2026). Its XML API reads and saves donors, gifts, pledges and contacts through raw procedure and SELECT calls, and the pricing page lists "Custom API Access" on the Pro plan only. Cotlet runs 14 DonorPerfect tools hosted, over MCP for agents and REST for scripts, in your own login on any plan.
Donors, gifts, pledges and thank-yous in DonorPerfect, worked by your agent. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
- Free 7-day trial, no card
- Unofficial, not affiliated with DonorPerfect
- Page: https://cotlet.dev/integrations/donorperfect-api-mcp-server
What can you automate in DonorPerfect?
- Enter a deposit list as gifts
- Apply payroll payments to pledges
- Log donor calls as contacts
- Send thank-you emails for new gifts
- Fix addresses from returned mail
- Add new donors and pledges
Does DonorPerfect have an MCP server or an API?
- An admin generates a key under User Management > API Self Service (since Sep 2025). The key has full data access, whatever your DonorPerfect user is allowed to see.
- The API returns at most 500 rows per call and has no call to send a thank-you email or list the gifts waiting for a receipt.
- There is no Zapier, n8n or Make app. APIANT runs 36 actions and an MCP server on the XML API, so it needs the same key.
| What you need | XML API | APIANT | Cotlet |
|---|---|---|---|
| Find donors, read gifts and pledges | Yes, 500 rows a call | Yes | Yes, paged for you |
| Add gifts, pledges and contacts | Yes, code by hand | Yes | Yes, after your OK |
| Apply a pledge payment | A gift with plink, codes typed in | Post pledge payment | Apply payment, pledge codes kept |
| Send a thank-you email | No | No | Yes, after your OK |
| Follows your user's permissions | No, full data access | No, same key | Yes, your login |
| What you need first | Pro or a request, plus a developer | An API key | Any plan |
Checked 27 Oct 2026. Sources: DonorPerfect pricing (Core, Plus, Pro features), DonorPerfect release notes (API Self Service, 3.32.1), APIANT: DonorPerfect integrations and MCP server, MCP Registry search for DonorPerfect (0 servers)
How does Cotlet connect to DonorPerfect?
- Sign in to DonorPerfect. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your DonorPerfect password, and no gift, pledge, donor change or thank-you email is saved or sent before you approve it.
Connect DonorPerfect to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Sign in to DonorPerfect in a Cloud Browser. Create a Cotlet account, open DonorPerfect in its Cloud Browser, sign in with your DonorPerfect username and the emailed code if it asks, then press Enable for agents.
- Add the Cotlet address. Paste https://cotlet.dev/mcp/v1 into the MCP server or connector field of your agent.
- Approve the connection. Chat apps send you to a Cotlet sign-in page. Code editors, n8n and scripts send an API key you create in the console.
https://cotlet.dev/mcp/v1 serves every Cotlet app you enable, DonorPerfect included. Enable DonorPerfect after you connect, and refresh the connector so its tools show up.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: donorperfect_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: donorperfect_write
How to use the DonorPerfect REST API
Create your Cotlet API key
Create a Cotlet API key with access to DonorPerfect and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect DonorPerfect in Cotlet and enable it for agents. Account access: Your own DonorPerfect username and password (the tools can do what your user can open in DonorPerfect).
Make your first DonorPerfect API request
REST:
curl "https://cotlet.dev/api/v1/donorperfect/donors/search?query=Whitfield" \
-H "Authorization: Bearer $COTLET_API_KEY"
Read donors and apply the operation limits
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "donorperfect",
"tool": "search_donors",
"result": {
"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
}
}
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.
limit: How many rows to return per page.
cursor: Next page cursor from the previous call.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
DonorPerfect workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | The donor record: name, address, email and phone. Use get_donor in your configured content report. |
| Make | HTTP > Make a request | Gifts on a donor record with date, amount and codes. Use list_gifts in your configured content report. |
| Python or Node.js | REST API | Pledges on a donor record with total, payments, billing amount and frequency. Use list_pledges in your configured content report. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads DonorPerfect; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
DonorPerfect API endpoints and MCP tools
Donors
One record at a time, by name, organization, donor ID or keyword. create_donor does not check for duplicates, so the agent searches first.
- Search donors (
search_donors, read): Finds donors and organizations by last name, organization name, donor ID or keyword. - Get donor (
get_donor, read): The donor record: name, address, email and phone. - Create donor (
create_donor, write, asks first): Adds an individual or an organization as a new donor record. - Update donor (
update_donor, write, asks first): Changes the address, email or phone on a donor record.
Gifts, codes and receipts
Codes are your organization's own, from Code Maintenance. A gift saved here starts any SmartAction you set up on new gifts. Letters stay in Instant Merge.
- List codes (
list_codes, read): The codes your organization uses for gifts, thank-you letters and contacts. - List gifts (
list_gifts, read): Gifts on a donor record with date, amount and codes. - Add gift (
add_gift, write, asks first): Saves one gift on a donor record with its codes. - List gifts waiting for a receipt (
list_receipts_due, read): Gifts the Receipts screen lists for acknowledgement, with each delivery preference. - Send thank-you email (
send_thank_you_email, write, asks first): Sends the thank-you email for one gift to the donor.
Pledges
A payment goes through Apply payment, so the pledge's codes carry over. The Schedule of payments is not edited.
- List pledges (
list_pledges, read): Pledges on a donor record with total, payments, billing amount and frequency. - Create pledge (
create_pledge, write, asks first): Adds a fixed or open-ended recurring pledge to a donor record. - Apply pledge payment (
apply_pledge_payment, write, asks first): Applies a payment to a pledge with the pledge's own codes.
Contacts
A contact reaches no donor, so add_contact runs without waiting for you.
- List contacts (
list_contacts, read): Contacts logged on a donor record: date, activity code, owner and comments. - Add contact (
add_contact, write): Logs a contact on a donor record with an activity code and an owner.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/donorperfect-api-mcp-server#tools
Who can see my DonorPerfect session, and how do I revoke it?
- What we store. Your signed-in DonorPerfect profile, encrypted with AES-256-GCM, in Finland. Never the password.
- What your agent gets. 14 DonorPerfect tools. No cookie, no login and no API key.
- What the session sees. Exactly what your DonorPerfect user may open. An API key would see everything.
- What no tool touches. Card and EFT details, Monthly Giving, Utilities, imports, Global Update and user settings.
- If DonorPerfect signs you out. We email you a link. You type the emailed MFA code yourself, we never do.
- How to cut access. Disable for agents, reset the browser or delete the key. The next call fails.
DonorPerfect's terms ask you not to store sensitive personal information in it, and your agent works under the same rule: keep health details out of contact notes. The Cotlet site has A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results); there is no SOC 2 report or third-party pentest yet.
Is it against DonorPerfect's terms? Account safety
You shall not use any bots, scrapers, spiders, crawlers, or similar technologies on any component of the Services.
DonorPerfect Terms of Service, Use Prohibitions (effective 1 May 2026)
An agent working in your login is such a technology, read strictly. The same terms let SofterWare suspend an account for a breach without notice, and termination includes "deletion of all data in your user account". We found no public case of a DonorPerfect account closed over automation (checked 27 Oct 2026). Keep your own exports and backups, and decide with your director before you start.
How we keep your account looking like you:
- Your own DonorPerfect user, signed in by you with your own MFA code
- One Cloud Browser with a steady IP and cookies, like the office computer
- Gifts, pledges, donor changes and thank-you emails wait for your OK
- One record at a time, never a bulk copy of your donor file
- If DonorPerfect objects, we pause the DonorPerfect tools for everyone within 24 h
Enter a large deposit over a few runs, not 300 gifts at once. The terms also ban use that could "overburden" SofterWare's servers.
What happens when DonorPerfect changes?
- 12 h between tests of DonorPerfect donor, gift, pledge and contact reads
- 24 h between tests of thank-you emails and other writes a donor would see
- $0 for a call to a DonorPerfect tool paused for a fix
DonorPerfect has listed 30 releases and fixes in 2026, about one every 10 days; 3.58 on 24 Sep 2026 moved sign-in to id.donorperfect.net and 3.59 switched it from email to username. When a screen moves, we repair the tool and keep its name. status.cotlet.dev checks the site, console and API every 3 minutes.
Approvals, undo and mistakes
- Matches each line. search_donors per line; two matches or none go on your list, not a guess.
- Checks your codes. Gift type, GL and solicitation from list_codes. An unknown code is left for you.
- Waits for your OK. Each gift waits in your Cotlet console with the donor, amount and codes.
- Totals it up. Entered total against the deposit total, and the lines it left.
| Action | Undo |
|---|---|
| Add a gift | Delete or adjust it in DonorPerfect; a SmartAction on new gifts may have run |
| Apply a pledge payment | Delete the payment gift in DonorPerfect |
| Create a pledge or donor | Delete it in DonorPerfect, or merge with Duplicate Maintenance |
| Update a donor | Run update_donor with the old values; get_donor shows them first |
| Send a thank-you email | Cannot be undone; the donor has it |
| Add a contact | Delete it on the record; nobody outside saw it |
6 of the 7 write tools ask first. add_contact runs at once, because a contact note stays inside your database. Reads run at once. For a scheduled run you can switch the wait off per tool.
DonorPerfect asks on save whether a gift belongs to an open pledge. add_gift answers no and lists the line, so a pledge payment never lands as a loose gift.
MCP call:
{
"name": "add_gift",
"arguments": {
"donor_id": 48213,
"date": "2026-10-21",
"amount": 250,
"gift_type": "Check",
"gl_code": "GEN",
"solicitation": "FALLAPPEAL",
"thank_you_letter": "STANDARD",
"reference": "4471"
}
}
REST:
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"}'
Response:
{
"gift_id": 90417,
"donor_id": 48213,
"date": "2026-10-21",
"amount": 250,
"gift_type": "Check",
"solicitation": "FALLAPPEAL",
"thank_you_letter": "STANDARD",
"status": "saved"
}
A donation form handler or a nightly script can call the same tools over REST at /api/v1/donorperfect, with one key and one price. A call your DonorPerfect user cannot make returns an error and costs nothing. Each tool row above lists its REST path.
How much does the DonorPerfect MCP server cost?
About $46 a month for a development office of 2, 7,940 credits. Works on Core, Plus or Pro; DonorPerfect quotes its plans on request.
| Job | Calls | Credits |
|---|---|---|
| Weekly deposit list, about 15 gifts | 35 × 4 | 1,400 |
| Payroll file to pledges, monthly | 34 × 1 | 340 |
| Call notes as contacts, 5 a workday | 16 × 22 | 3,520 |
| Thank-you emails, each workday | 4 × 22 | 880 |
| Returned mail, 10 new addresses | 30 × 1 | 300 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 7,940 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- No Pro plan, API key or developer needed
The month is our example: about 60 gifts from weekly deposits, a 12-line payroll file, 5 call notes a workday, 3 thank-you emails a workday and 10 returned-mail addresses. DonorPerfect publishes no typical size; it serves about 11,000 organizations. Dollars at the $29 pack rate.
DonorPerfect MCP server on GitHub, APIANT or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| APIANT MCP server | A hosted MCP server and 36 actions on the XML API, free to start. | Needs your API key, which sees all data; no thank-you email or receipt list. |
| LukeTowers/php-donorperfect-api | A PHP wrapper for the XML API, MIT. 4 stars, last push 5 Apr 2024. | Code for a developer, not an agent; needs a key. |
| betterworldcollective/donorperfect-php-sdk | A newer PHP SDK, MIT. 0 stars, last push 15 Oct 2026. | Same: a key and your own code. |
| nerveband/givewp2dp | A WordPress plugin that syncs GiveWP donations into DonorPerfect, recurring gifts as pledges. | One job, one direction; needs a key. |
If you are on Pro and have a developer, the XML API is the direct route for syncing another system. If you have a key and want an agent on it, APIANT wraps it. If your office should hand an agent the deposit list, the payroll file and the thank-yous without a key, Cotlet does that hosted in your own login.
Who runs Cotlet
Take Group sp. z o.o. runs Cotlet: a software company registered in Poland, EU (VAT PL6342984273), in business since 2019. The founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the DonorPerfect tools go to contact@cotlet.dev.
DonorPerfect API and MCP: questions
How do I get access?
Sign up free at https://cotlet.dev, open DonorPerfect under Integrations in the console and sign in to DonorPerfect in its Cloud Browser. The trial starts when you sign up and needs no card.
How do I connect DonorPerfect to ChatGPT or Claude?
Sign up at cotlet.dev, log in to DonorPerfect once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your DonorPerfect account through Cotlet, in their phone apps too.
What can ChatGPT do in DonorPerfect?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in DonorPerfect: enter gifts from a deposit list; apply payments to pledges; log donor calls as contacts. You ask in plain words, and anything that reaches other people waits for your OK first.
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.
Does it work with DonorPerfect's AI Donor Summary?
No. AI Donor Summary is a beta panel inside the donor record (since release 3.51, June 2026) and no outside agent can call it. Your agent reads gifts, pledges and contacts with the tools above and writes its own summary.
Does DonorPerfect have webhooks?
Not that we found. Connectors such as APIANT poll the donor and gift tables for new rows. To react to new gifts, run your agent on a schedule with list_receipts_due.
Is the MCP server different from the REST API?
Only in how you call it. Both have the same 14 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and form handlers use REST.
Is Cotlet affiliated with DonorPerfect?
No. Cotlet is independent and not affiliated with DonorPerfect or SofterWare.
Can I use the DonorPerfect API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
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
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.