# DonorPerfect MCP connector

The DonorPerfect connector lets Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent look up donors, gifts, contacts and addresses in DonorPerfect and update records, with each person signed in as themselves and every call logged.

Source: https://elaichi.ai/connectors/donorperfect/

## Facts

| | |
| --- | --- |
| Application | DonorPerfect |
| Category | CRM |
| AI tools | 54 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once DonorPerfect is connected

- Summarize Maria Chen's gifts and contacts before tomorrow's meeting
- Update the Hendersons' mailing address to 42 Oak Street, Portland
- Create a donor for Lakeside Foundation and flag it as corporate

## Connect DonorPerfect in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick DonorPerfect.
2. Optionally set Share with, then press Connect.
3. Paste a DonorPerfect API key. One person generates a token in DonorPerfect and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which DonorPerfect tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## DonorPerfect MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## DonorPerfect MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## DonorPerfect MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## DonorPerfect MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## DonorPerfect MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect DonorPerfect to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a DonorPerfect tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with DonorPerfect through Elaichi

### Catch the donor record up after a call

Development. Describe the conversation and the agent logs it as a contact on the donor and updates the donor record from your notes. Nothing waits in a notebook until Friday.

### Prepare for a donor meeting in minutes

Major gifts. Ask for a donor's gifts, recent contacts and flags and get a plain summary before you walk in. No more clicking through tabs while the car is running.

### Fix a mailing address before the appeal

Donor relations. When a donor writes in with a new address, ask for it to be updated or added, and the record is right before the next mailing goes out.

### Flag everyone who came to the gala

Events. Create a flag for the event and apply it to the donors who attended, so next year's invitation list is already built.

### Add new donors without opening a form

Database. Paste a line from a pledge card or a sign-up sheet and the agent creates the donor, sets the right codes and checkbox values, and adds the address.

### Pull the month's gifts for reconciliation

Finance. Ask for every gift recorded in a date range and get a list to check against deposits, without exporting a report first.

## Elaichi vs Zapier MCP vs Composio for DonorPerfect

All three can connect DonorPerfect to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over DonorPerfect tools | Allow or restrict single DonorPerfect tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per DonorPerfect call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect DonorPerfect to Claude?

Connect DonorPerfect in Elaichi by pasting your DonorPerfect API key, which takes about a minute. There is no client ID or secret to generate and no OAuth application to register on the DonorPerfect side. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks and DonorPerfect is ready to use.

### Does DonorPerfect work with ChatGPT and Cursor as well as Claude?

Yes. The DonorPerfect connection in Elaichi is reached through one endpoint, https://api.elaichi.ai/mcp, and that same address works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect DonorPerfect once and every client picks it up.

### What can an AI agent actually do with my DonorPerfect data?

An agent connected to DonorPerfect can search for donors, read a donor's gifts, contacts and addresses, and summarize them in plain language. It can also create and update donors, log contacts, add or correct addresses, create codes and flags, and set checkbox values. Short, concrete asks such as "log a call with Maria Chen about the capital campaign" work better than long paragraphs.

### Does connecting DonorPerfect give the AI everything in my database?

No. Each person signs in to Elaichi as themselves, so an agent working in DonorPerfect sees only the donors, gifts and fields that person can already see. Elaichi can narrow that further with roles and restrictions, and it never widens what DonorPerfect itself allows.

### Can my team share one DonorPerfect connection?

Yes. One person connects DonorPerfect with the API key and shares the connection with a team in Elaichi, and nobody else on the team ever handles the key. Each person still signs in as themselves, so the audit log names the actual person who looked up a donor or logged a contact, not a shared account.

### Can I stop an agent from deleting or changing things in DonorPerfect?

Yes. Restrictions in Elaichi work per action, so you can allow reading DonorPerfect donors and gifts while restricting updates to donor records or bulk changes to checkbox values. A restriction is set on a role or on one person, and a restricted action still appears in Elaichi's tool search flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a DonorPerfect connection when someone leaves?

Offboarding a person in Elaichi ends their access to DonorPerfect through every client at once. A DonorPerfect connection shared with a team keeps working for everyone else on it. If you want it gone entirely, disconnecting DonorPerfect once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

### Does the DonorPerfect MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. DonorPerfect is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for DonorPerfect?

Yes. Both let Claude, ChatGPT or Cursor use DonorPerfect. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every DonorPerfect call.

### How is Elaichi different from Composio for DonorPerfect?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to DonorPerfect: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 54 DonorPerfect tools

Every tool below is callable through https://api.elaichi.ai/mcp once DonorPerfect is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all DonorPerfect address udfs** (List). List address user defined fields (DPADDRESSUDF table) with a dynamic SELECT, ordered by address_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **Create a DonorPerfect address** (Create). Add a secondary (seasonal) address for a donor with dp_saveaddress. Returns the new address_id. Required: donor_id. DonorPerfect procedure: dp_saveaddress.
- **Update a DonorPerfect address by ID** (Update). Update a secondary address with dp_saveaddress. Every field is overwritten; send all values. Required: id, donor_id. DonorPerfect procedure: dp_saveaddress.
- **List all DonorPerfect addresses** (List). List secondary / seasonal addresses (DPADDRESS table) with a dynamic SELECT, ordered by address_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **Get single DonorPerfect address by ID** (Get). Get one row of secondary / seasonal addresses (DPADDRESS table) by address_id with a dynamic SELECT. Required: id.
- **DonorPerfect checkbox fields bulk update** (Update). Set the checked values of one checkbox field for a donor with mergemultivalues: codes in valuestring are checked, all others in that field are unchecked. Required: matchingid, fieldname, valuestring. DonorPerfect procedure: mergemultivalues.
- **Create a DonorPerfect checkbox value** (Create). Check one checkbox value (DPUSERMULTIVALUES) for a donor with dp_savemultivalue_xml. checkbox_fields.bulk_update is usually better. Required: matching_id, field_name, code. DonorPerfect procedure: dp_savemultivalue_xml.
- **DonorPerfect checkbox values bulk delete** (Delete). Uncheck ALL checkbox values on one screen tab (MAIN, GIFT, PLEDGE, BIO or OTHER) for a donor with dp_deletemultivalues_xml. Irreversible; prefer checkbox_fields.bulk_update to change one field. Required: matching_id, table_name. DonorPerfect procedure: dp_deletemultivalues_xml.
- **List all DonorPerfect checkbox values** (List). List checked checkbox values (DPUSERMULTIVALUES table) with a dynamic SELECT, ordered by id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **Create a DonorPerfect code** (Create). Add a code (GL code, solicitation, campaign, ... as in Code Maintenance) with dp_savecode, or update one by setting original_code and overwrite=Y. Required: field_name, code, description. DonorPerfect procedure: dp_savecode.
- **List all DonorPerfect codes** (List). List code values used in drop-downs (DPCODES table; filter by field_name, e.g. GL_CODE, SOLICIT_CODE, CAMPAIGN, FLAG, MEMORY_HONOR) with a dynamic SELECT, ordered by code_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **Create a DonorPerfect contact** (Create). Create a contact record (activity / task on the Contact screen) for a donor with dp_savecontact. Returns the new contact_id. Required: donor_id. DonorPerfect procedure: dp_savecontact.
- **Update a DonorPerfect contact by ID** (Update). Update a contact record with dp_savecontact. Every field is overwritten; send all values. Required: id, donor_id. DonorPerfect procedure: dp_savecontact.
- **List all DonorPerfect contacts** (List). List contact records (DPCONTACT table) with a dynamic SELECT, ordered by contact_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **Get single DonorPerfect contact by ID** (Get). Get one row of contact records (DPCONTACT table) by contact_id with a dynamic SELECT. Required: id.
- **List all DonorPerfect donor gifts** (List). List all gifts of one donor with dp_gifts (a fixed set of fields: gift_id, gift_date2, amount, gl, solicit_code, campaign, record_type, balance...). For other fields use gifts.list with donor_id. Required: donor_id. DonorPerfect procedure: dp_gifts.
- **List all DonorPerfect donor udfs** (List). List donor user defined fields (DPUDF table, one row per donor) with a dynamic SELECT, ordered by donor_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **Get single DonorPerfect donor udf by ID** (Get). Get one row of donor user defined fields (DPUDF table, one row per donor) by donor_id with a dynamic SELECT. Required: id.
- **DonorPerfect donors search** (Search). Search donors like the DonorPerfect search screen (% is a wildcard, e.g. last_name=Pa%). Returns donor_id, name, address, gifts and gift_total for each match. DonorPerfect procedure: dp_donorsearch.
- **Create a DonorPerfect donor** (Create). Create a donor (constituent) with dp_savedonor. Returns the new donor_id as the record value. DonorPerfect procedure: dp_savedonor.
- **Update a DonorPerfect donor by ID** (Update). Update a donor with dp_savedonor. IMPORTANT: DonorPerfect overwrites every field of the donor; fields you leave out are cleared. Read the donor first (donors.get) and send all values back with your changes. Required: id. DonorPerfect procedure: dp_savedonor.
- **List all DonorPerfect donors** (List). List donors (DP table: name, address, phones, email, giving totals...) with a dynamic SELECT, ordered by donor_id. The connector pages through all rows 500 at a time (OFFSET/FETCH). modified_since matches COALESCE(modified_date, created_date), the incremental pattern in the DonorPerfect manual.

- **Get single DonorPerfect donor by ID** (Get). Get one row of donors (DP table: name, address, phones, email, giving totals...) by donor_id with a dynamic SELECT. Required: id.
- **Create a DonorPerfect flag** (Create). Set a flag on a donor with dp_saveflag_xml. Fails with a duplicate key error if the flag is already set. Required: donor_id, flag. DonorPerfect procedure: dp_saveflag_xml.
- **DonorPerfect flags bulk delete** (Delete). Remove ALL flags from a donor with dp_delflags_xml (single flags can't be removed). Read them first with flags.list and re-add the ones to keep. Required: donor_id. DonorPerfect procedure: dp_delflags_xml.
- **List all DonorPerfect flags** (List). List donor flags (DPFLAGS table) with a dynamic SELECT, ordered by donor_id, flag. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **Create a DonorPerfect gift tribute** (Create). Associate a gift with one or more tributes (dp_tribAnon_AssocTribsToGift). Required: giftid, tributeid_list. DonorPerfect procedure: dp_tribAnon_AssocTribsToGift.
- **List all DonorPerfect gift udfs** (List). List gift user defined fields (DPGIFTUDF table, one row per gift) with a dynamic SELECT, ordered by gift_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **Get single DonorPerfect gift udf by ID** (Get). Get one row of gift user defined fields (DPGIFTUDF table, one row per gift) by gift_id with a dynamic SELECT. Required: id.
- **Create a DonorPerfect gift** (Create). Create a gift with dp_savegift (record_type G gift, M main gift of a split, S soft credit; pledges use pledges.create). Pledge payments are gifts with plink = the pledge's gift_id. Returns the new gift_id. Required: donor_id, record_type, gift_date, amount. DonorPerfect procedure: dp_savegift.
- **Update a DonorPerfect gift by ID** (Update). Update a gift with dp_savegift. IMPORTANT: every field is overwritten; fields you leave out are cleared. Read the gift first (gifts.get) and send all values back. Also used for gift adjustments (see the README). Required: id, donor_id, record_type, gift_date, amount. DonorPerfect procedure: dp_savegift.
- **List all DonorPerfect gifts** (List). List gifts and pledges (DPGIFT table; record_type G gift, P pledge, M split main, S soft credit) with a dynamic SELECT, ordered by gift_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **Get single DonorPerfect gift by ID** (Get). Get one row of gifts and pledges (DPGIFT table; record_type G gift, P pledge, M split main, S soft credit) by gift_id with a dynamic SELECT. Required: id.
- **Create a DonorPerfect link** (Create). Link two donors (Links tab) with dp_savelink; the reciprocal link is created automatically. Returns the link_id. Required: donor_id, donor_id2, link_code. DonorPerfect procedure: dp_savelink.
- **Update a DonorPerfect link by ID** (Update). Update a donor link with dp_savelink. Required: id, donor_id, donor_id2, link_code. DonorPerfect procedure: dp_savelink.
- **List all DonorPerfect links** (List). List donor links (DPLINK table) with a dynamic SELECT, ordered by link_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **Create a DonorPerfect other info** (Create). Create an Other Info record for a donor with dp_saveotherinfo. Returns the other_id (use it as matching_id for its user defined fields). Required: donor_id. DonorPerfect procedure: dp_saveotherinfo.
- **Update a DonorPerfect other info by ID** (Update). Update an Other Info record with dp_saveotherinfo. Every field is overwritten; send all values. Required: id, donor_id. DonorPerfect procedure: dp_saveotherinfo.
- **List all DonorPerfect other info** (List). List Other Info records (DPOTHERINFO table) with a dynamic SELECT, ordered by other_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **Get single DonorPerfect other info by ID** (Get). Get one row of Other Info records (DPOTHERINFO table) by other_id with a dynamic SELECT. Required: id.
- **List all DonorPerfect other info udfs** (List). List Other Info user defined fields (DPOTHERINFOUDF table) with a dynamic SELECT, ordered by other_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **Create a DonorPerfect payment method** (Create). Store an EFT payment method reference (SafeSave vault, masked card or bank digits) for a donor with dp_PaymentMethod_Insert. Only for systems with EFT Transactions enabled; never send full card numbers. Required: donor_id, accounttype, dppaymentmethodtypeid. DonorPerfect procedure: dp_PaymentMethod_Insert.
- **List all DonorPerfect payment methods** (List). List EFT payment method references (DPPAYMENTMETHOD table) with a dynamic SELECT, ordered by DpPaymentMethodID. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **Create a DonorPerfect pledge** (Create). Create a pledge (parent recurring commitment, record_type P) with dp_savepledge. Payments are created with gifts.create using plink. Returns the pledge's gift_id. Required: donor_id, gift_date, start_date, total, bill, frequency. DonorPerfect procedure: dp_savepledge.
- **Update a DonorPerfect pledge by ID** (Update). Update a pledge with dp_savepledge. IMPORTANT: every field is overwritten; send all values. Required: id, donor_id, gift_date, start_date, total, bill, frequency. DonorPerfect procedure: dp_savepledge.
- **DonorPerfect queries execute** (Execute). Run your own read-only SQL SELECT on the DonorPerfect tables (DP, DPUDF, DPGIFT, DPGIFTUDF, DPCODES, DPADDRESS, DPCONTACT, DPFLAGS, DPLINK, DPOTHERINFO, DPUSERMULTIVALUES, DPPAYMENTMETHOD, ...). At most 500 rows per call; page with OFFSET ... FETCH NEXT. Required: sql.
- **List all DonorPerfect tribute gift links** (List). List gift-to-tribute associations (DPTRIBUTESANON_GIFTASSOC table) with a dynamic SELECT, ordered by gift_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **Create a DonorPerfect tribute notification** (Create). Create the tribute gift notification record for a recipient (dp_tribNotif_Save); it appears as a Send Notification gift on the recipient. Required: donor_id, glink, tlink, amount, total. DonorPerfect procedure: dp_tribNotif_Save. Optional membership fields (membership_type, membership_level, membership_enr_date, membership_exp_date) are sent only when given.

- **Create a DonorPerfect tribute recipient** (Create). Add a notification recipient for one tribute gift (dp_tribAnon_SaveTribRecipient). Follow with tribute_notifications.create. Required: donorid, tributeid, giftid. DonorPerfect procedure: dp_tribAnon_SaveTribRecipient.
- **List all DonorPerfect tributes** (List). List tributes (In Honor Of / In Memory Of) with gift totals and notification names, via dp_tribAnon_MyTribSummary. DonorPerfect procedure: dp_tribAnon_MyTribSummary.
- ...and 4 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
