[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)

# Bloomerang API and MCP server

> Yes, Bloomerang has a REST API for server-to-server integrations, but no MCP server for AI agents (checked 22 Oct 2026). An administrator creates the private key in User Settings under Edit My User, and that key can change any data in the database. Bloomerang also has a Zapier app with 7 triggers, 6 actions and 2 searches.

Donor CRM for nonprofits: constituent records with a timeline of gifts, interactions and notes, tasks, groups, reports and a Duplicate Constituents page.

## What is the Bloomerang API?

Cotlet's Bloomerang API exposes 12 endpoints for your own Bloomerang account: search constituents, get a constituent, list donations, list interactions, list funds, campaigns and appeals, list possible duplicates, create a constituent, update a constituent, log an interaction, create a task, record a received gift and merge two constituents. The search_constituents endpoint returns find constituents by name or account number, with the dashboard filters. Each endpoint takes simple JSON inputs like constituent_id, cursor or purpose and works both as an operation of the bloomerang_read or bloomerang_write MCP tool for agents and as a REST call for scripts.

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

Yes, Bloomerang has a REST API for server-to-server integrations, but no MCP server for AI agents (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for Bloomerang with 12 endpoints (6 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Bloomerang have an official API?

Yes, Bloomerang has a REST API for server-to-server integrations, but no MCP server for AI agents (checked 22 Oct 2026). An administrator creates the private key in User Settings under Edit My User, and that key can change any data in the database. Bloomerang also has a Zapier app with 7 triggers, 6 actions and 2 searches.

| Task | Bloomerang official | Cotlet |
|---|---|---|
| Search constituents by name | Yes: Zapier Find Constituent; REST API | Yes |
| Filter by lifecycle stage and donor type | Partly: Dashboard filters in the app; Zapier search is by name only | Yes |
| Read a constituent's gifts | Partly: Zapier fires on new transactions, with no action that reads history | Yes |
| Record a gift that already arrived | Yes: Zapier Create Donation, up to 10 line items; no MCP server for agents | Yes |
| Log an interaction | Yes: Zapier Create Interaction | Yes |
| Create a task for a colleague | Yes: Zapier Create Task | Yes |
| Create or update a constituent | Yes: Zapier Create and Update Constituent | Yes |
| Review and merge possible duplicates | No: No Zapier action; done on the Duplicate Constituents page | Yes |

Sources: [Bloomerang: API](https://bloomerang.com/product/integrations-data-management/api/), [Bloomerang: REST API documentation](https://bloomerang.com/api/rest-api/), [Zapier: Bloomerang triggers and actions](https://zapier.com/apps/bloomerang/integrations), [Bloomerang Help: User Permissions](https://help.bloomerang.com/en/articles/12632881-user-permissions)

## For AI agents

```text
Yes, Bloomerang has a REST API for server-to-server integrations, but no MCP server for AI agents (checked 22 Oct 2026). An administrator creates the private key in User Settings under Edit My User, and that key can change any data in the database. Bloomerang also has a Zapier app with 7 triggers, 6 actions and 2 searches.
Cotlet provides a hosted MCP server and REST API for Bloomerang: 12 tools (6 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=bloomerang, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    bloomerang_read, bloomerang_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/bloomerang, each operation at its own route, e.g. POST /api/v1/bloomerang/constituents/{constituent_id}/donations
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_constituents, get_constituent, list_donations, list_interactions, list_giving_options, list_duplicates, create_constituent, update_constituent, add_interaction, create_task, record_donation, merge_constituents
Confirm      record_donation, merge_constituents (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/bloomerang-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=bloomerang, requests Bloomerang in the Cotlet console and creates an API key there.
2. The user signs in to Bloomerang once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Bloomerang 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 Bloomerang 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 Bloomerang 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 Bloomerang 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 Bloomerang 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 Bloomerang's terms; Cotlet is not affiliated with Bloomerang.
```

## What can an AI agent do in Bloomerang?

Cotlet is best for nonprofit fundraisers and development staff who want an AI agent to merge duplicate donors, log gifts that already arrived and prepare lapsed-donor follow-ups without running or fixing a server.

- **[Log checks and cash gifts](https://cotlet.dev/integrations/bloomerang-api-mcp-server/log-checks-and-cash-gifts.md)** (runs: weekly): "Here is the deposit list from this week: Lena Ortiz 150 check, Priya Nair 40 cash. Find each donor in Bloomerang, record the gift in the Fall Appeal 2026 campaign, and tell me who you could not match." → `search_constituents`, `list_giving_options`, `record_donation`
- **[Merge duplicate constituents](https://cotlet.dev/integrations/bloomerang-api-mcp-server/merge-duplicate-constituents.md)** (runs: weekly): "Go through the possible duplicates in Bloomerang. Merge pairs where name and email are identical, keeping the record with the most recent gift. Leave the rest for me with a one-line reason." → `list_duplicates`, `get_constituent`, `merge_constituents`
- **[Prepare lapsed donor follow-ups](https://cotlet.dev/integrations/bloomerang-api-mcp-server/lapsed-donor-follow-ups.md)** (runs: weekly): "List Bloomerang donors who lapsed in the last 60 days with a gift of 100 or more. For each, read the last gift and the last interaction, and create a call task for Sam due next Friday. Skip anyone we contacted in the last 30 days." → `search_constituents`, `list_donations`, `list_interactions`, `create_task`
- **Log donor calls and follow-ups** (runs: daily): "Here are my notes from today's donor calls. Log each as a Phone interaction with purpose Acknowledgement or Solicitation, and create a follow-up task for me one week out where I said to call back." → `search_constituents`, `add_interaction`, `create_task`
- **Update contact details from a list**: "Update these donors in Bloomerang with the new emails and addresses from my sheet. Create anyone who is not in Bloomerang yet." → `search_constituents`, `update_constituent`, `create_constituent`

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

Yes. Cotlet does not replace your automation platform: it gives it a Bloomerang 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 log checks and cash gifts, 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/bloomerang/constituents/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/bloomerang/constituents/search with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 12 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 Bloomerang.

### search_constituents

Find constituents by name or account number, with the dashboard filters. Access: read. REST: `GET /api/v1/bloomerang/constituents/search`. MCP: `bloomerang_read → search_constituents`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Name, account number, head of household or primary contact. |
| `type` | string | no | Individual, Organization or Household. |
| `status` | string | no | Active, Inactive or Deceased. |
| `lifecycle_stage` | string | no | Prospective, Current or Lapsed. |
| `donor_type` | string | no | New, Retained, Recaptured or Recurring. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns 25 constituents per page with the dashboard columns: name, account number, primary email and phone, status, latest transaction amount and date. Lifecycle stage and donor type are the ones Bloomerang computes: Lapsed means the latest transaction is older than 13 months. Follow next_cursor to the end of a list.

Example response:

```json
{
  "constituents": [
    {
      "id": 48211,
      "account_number": 48211,
      "name": "Lena Ortiz",
      "type": "Individual",
      "email": "lena@example.org",
      "phone": "555-0142",
      "status": "Active",
      "latest_transaction_amount": 75,
      "latest_transaction_date": "2025-06-14"
    }
  ],
  "next_cursor": "eyJwIjoyfQ"
}
```

### get_constituent

Read one constituent profile with contact details and giving status. Access: read. REST: `GET /api/v1/bloomerang/constituents/{constituent_id}`. MCP: `bloomerang_read → get_constituent`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `constituent_id` | integer | yes | Constituent ID from search_constituents. |

Returns the profile: type, name, primary email, phone and address, relationship manager, lifecycle stage, donor types and the latest timeline entries. Household members come with the head of household. Gifts and interactions in full come from list_donations and list_interactions.

Example response:

```json
{
  "id": 48211,
  "type": "Individual",
  "name": "Lena Ortiz",
  "email": "lena@example.org",
  "phone": "555-0142",
  "address": "12 Mill Road, Dayton, OH 45402",
  "relationship_manager": "Sam Okafor",
  "lifecycle_stage": "Lapsed",
  "donor_types": [],
  "timeline": [
    {
      "kind": "donation",
      "date": "2025-06-14",
      "summary": "Donation 75.00 to General Fund"
    }
  ]
}
```

### list_donations

List the gifts on a constituent timeline. Access: read. REST: `GET /api/v1/bloomerang/constituents/{constituent_id}/donations`. MCP: `bloomerang_read → list_donations`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `constituent_id` | integer | yes | Constituent ID from search_constituents. |
| `since` | string | no | Only gifts on or after this date, YYYY-MM-DD. |
| `until` | string | no | Only gifts on or before this date, YYYY-MM-DD. |
| `fund` | string | no | Fund name from list_giving_options. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns each gift with date, amount, non-deductible amount, fund, campaign, appeal and payment method, as the timeline shows it. A gift with a split designation lists each designation. A user whose Transactions permission is No access gets APP_PERMISSION_DENIED.

Example response:

```json
{
  "donations": [
    {
      "id": 90417,
      "date": "2025-06-14",
      "amount": 75,
      "non_deductible": 0,
      "fund": "General Fund",
      "campaign": "Spring Appeal 2025",
      "appeal": "Spring mailer",
      "method": "Check"
    }
  ],
  "next_cursor": null
}
```

### list_interactions

List calls, emails and notes logged for a constituent. Access: read. REST: `GET /api/v1/bloomerang/constituents/{constituent_id}/interactions`. MCP: `bloomerang_read → list_interactions`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `constituent_id` | integer | yes | Constituent ID from search_constituents. |
| `purpose` | string | no | Purpose: Acknowledgement, ImpactCultivation, Newsletter, Receipt, Solicitation, SpecialEvent, VolunteerActivity, PledgeReminder, Welcome or Other. |
| `channel` | string | no | Channel: Email, Phone, TextMessage, Mail, InPerson, SocialMedia, Website or Other. |
| `since` | string | no | Only interactions on or after this date, YYYY-MM-DD. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns date, subject, channel and purpose for each interaction. A user without giving access does not see interactions with a giving-related purpose (Acknowledgement, PledgeReminder, Receipt, Solicitation); they are left out, not an error.

Example response:

```json
{
  "interactions": [
    {
      "id": 7305,
      "date": "2026-09-02",
      "subject": "Thank-you call",
      "channel": "Phone",
      "purpose": "Acknowledgement"
    }
  ],
  "next_cursor": null
}
```

### list_giving_options

List the fund, campaign and appeal names your database uses. Access: read. REST: `GET /api/v1/bloomerang/giving-options`. MCP: `bloomerang_read → list_giving_options`.

No parameters.

Returns the names that record_donation accepts in fund, campaign and appeal. Call it once per run so a gift is never filed under a name that does not exist.

Example response:

```json
{
  "funds": [
    "General Fund",
    "Shelter Repairs"
  ],
  "campaigns": [
    "Fall Appeal 2026",
    "Spring Appeal 2025"
  ],
  "appeals": [
    "Fall mailer",
    "Spring mailer",
    "Gala night"
  ]
}
```

### list_duplicates

List the pairs Bloomerang flagged as possible duplicate constituents. Access: read. REST: `GET /api/v1/bloomerang/duplicates`. MCP: `bloomerang_read → list_duplicates`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `cursor` | string | no | Next page cursor from the previous call. |

Returns each flagged pair with the criteria that matched and both records side by side. The Duplicate Constituents page is for admins; a standard user can review the pairs by default, and not at all without the Data Tools permission, which fails with APP_PERMISSION_DENIED. Pairs you dismissed with Not a Duplicate in the app do not return.

Example response:

```json
{
  "pairs": [
    {
      "pair_id": "p-2201",
      "matched_on": [
        "name",
        "email"
      ],
      "a": {
        "id": 48211,
        "name": "Lena Ortiz",
        "email": "lena@example.org",
        "latest_transaction_date": "2025-06-14"
      },
      "b": {
        "id": 51987,
        "name": "Lena Ortiz",
        "email": "lena@example.org",
        "latest_transaction_date": null
      }
    }
  ],
  "next_cursor": null
}
```

### create_constituent

Add an individual or organization, unless the same person is already there. Access: write. REST: `POST /api/v1/bloomerang/constituents`. MCP: `bloomerang_write → create_constituent`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `type` | string | yes | Individual or Organization. |
| `first_name` | string | no | For an individual. |
| `last_name` | string | no | For an individual. |
| `organization_name` | string | no | For an organization. |
| `email` | string | no | Primary email. |
| `phone` | string | no | Primary phone. |
| `street` | string | no | Primary address, street line. |
| `city` | string | no | City. |
| `state` | string | no | State or region. |
| `postal_code` | string | no | Postal code. |

Searches first. If a constituent with the same name and the same email, phone or address exists, it returns that record with created set to false and adds nothing. Otherwise it creates the record and returns its ID. It reaches no one and is undone by deleting the record in Bloomerang, so it does not wait for your OK.

Example response:

```json
{
  "id": 52004,
  "created": true,
  "name": "Priya Nair",
  "type": "Individual"
}
```

### update_constituent

Change contact details on an existing constituent. Access: write. REST: `PATCH /api/v1/bloomerang/constituents/{constituent_id}`. MCP: `bloomerang_write → update_constituent`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `constituent_id` | integer | yes | Constituent ID from search_constituents. |
| `email` | string | no | New primary email. |
| `phone` | string | no | New primary phone. |
| `street` | string | no | New primary address, street line. |
| `city` | string | no | City. |
| `state` | string | no | State or region. |
| `postal_code` | string | no | Postal code. |

Sets only the fields you pass and returns the profile as saved. It does not touch gifts, interactions or the relationship manager. It reaches no one and a second call puts the old value back, so it does not wait for your OK.

Example response:

```json
{
  "id": 48211,
  "name": "Lena Ortiz",
  "email": "lena.ortiz@example.org",
  "phone": "555-0142",
  "updated": [
    "email"
  ]
}
```

### add_interaction

Record a call, email, meeting or note on a constituent timeline. Access: write. REST: `POST /api/v1/bloomerang/constituents/{constituent_id}/interactions`. MCP: `bloomerang_write → add_interaction`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `constituent_id` | integer | yes | Constituent ID from search_constituents. |
| `date` | string | yes | YYYY-MM-DD. |
| `subject` | string | yes | Up to 255 characters. |
| `purpose` | string | yes | Purpose: Acknowledgement, ImpactCultivation, Newsletter, Receipt, Solicitation, SpecialEvent, VolunteerActivity, PledgeReminder, Welcome or Other. |
| `channel` | string | yes | Channel: Email, Phone, TextMessage, Mail, InPerson, SocialMedia, Website or Other. |
| `note` | string | no | Longer text kept with the interaction. |

Logs what already happened; it sends nothing to the constituent. A user without giving access cannot choose Acknowledgement, PledgeReminder, Receipt or Solicitation and gets APP_PERMISSION_DENIED. It reaches no one, so it does not wait for your OK.

Example response:

```json
{
  "id": 7311,
  "constituent_id": 48211,
  "date": "2026-10-21",
  "subject": "Called about lapsed gift",
  "channel": "Phone",
  "purpose": "Solicitation"
}
```

### create_task

Create a follow-up task for a staff member on a constituent. Access: write. REST: `POST /api/v1/bloomerang/constituents/{constituent_id}/tasks`. MCP: `bloomerang_write → create_task`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `constituent_id` | integer | yes | Constituent ID from search_constituents. |
| `user_id` | integer | yes | Bloomerang user the task is assigned to. |
| `due_date` | string | yes | YYYY-MM-DD. |
| `subject` | string | yes | Task subject. |
| `channel` | string | yes | Channel: Email, Phone, TextMessage, Mail, InPerson, SocialMedia, Website or Other. |
| `purpose` | string | no | Purpose: Acknowledgement, ImpactCultivation, Newsletter, Receipt, Solicitation, SpecialEvent, VolunteerActivity, PledgeReminder, Welcome or Other. |
| `note` | string | no | Task note. |
| `notify` | boolean | no | Send the assignee a notification email. Default false. |

Creates one task for the user you name and returns its ID. With notify false it sends no email; with notify true the assignee gets Bloomerang's task notification. It never contacts the donor, so it does not wait for your OK.

Example response:

```json
{
  "id": 3318,
  "constituent_id": 48211,
  "user_id": 12,
  "due_date": "2026-10-29",
  "subject": "Call about lapsed gift",
  "channel": "Phone",
  "notified": false
}
```

### record_donation

Record a gift that already arrived by cash, check, in kind or an outside payment service. Access: write, asks the user first. REST: `POST /api/v1/bloomerang/constituents/{constituent_id}/donations`. MCP: `bloomerang_write → record_donation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `constituent_id` | integer | yes | Constituent ID from search_constituents. |
| `date` | string | yes | Date the gift was made, YYYY-MM-DD. |
| `amount` | number | yes | Total amount. |
| `method` | string | yes | Cash, Check, InKind, PayPal, Venmo, ApplePay or GooglePay. The last three record payments made outside Bloomerang. |
| `non_deductible` | number | no | Part of the gift that is not tax deductible. Default 0. |
| `fund` | string | no | Fund name from list_giving_options. |
| `campaign` | string | no | Campaign name from list_giving_options. |
| `appeal` | string | no | Appeal name from list_giving_options. |

Adds the gift to the timeline and returns its ID. It records money that is already in your hands: it does not process a payment, so Credit Card, EFT and Saved Payment are refused, and there is no tool to refund or delete a gift. It leaves "send acknowledgement now" off, so no email goes to the donor. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "id": 90533,
  "constituent_id": 48211,
  "date": "2026-10-19",
  "amount": 150,
  "method": "Check",
  "fund": "General Fund",
  "campaign": "Fall Appeal 2026",
  "appeal": "Fall mailer",
  "acknowledgement_sent": false
}
```

### merge_constituents

Merge a duplicate into the record you keep. Access: write, asks the user first. REST: `POST /api/v1/bloomerang/keeps/{keep_id}/constituents/merge`. MCP: `bloomerang_write → merge_constituents`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `keep_id` | integer | yes | Constituent ID to keep. |
| `merge_id` | integer | yes | Constituent ID merged into it. |

Combines the two records the way the Merge button does: you pick the record to keep, and information on the other that the keeper lacks is added. Read both with get_constituent first; the app shows what will be lost in red, and this call does not. Needs the Duplicate Constituents or Merge Constituents page, so an admin or a standard user with Data Tools. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "kept_id": 48211,
  "merged_id": 51987,
  "name": "Lena Ortiz",
  "merged": true
}
```

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

Connecting Bloomerang takes three steps: sign up, sign in to Bloomerang 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 Bloomerang to your agent.

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

2. **Sign in to Bloomerang in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Bloomerang 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 Bloomerang 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 the deposit list from this week: Lena Ortiz 150 check, Priya Nair 40 cash. Find each donor in Bloomerang, record the gift in the Fall Appeal 2026 campaign, and tell me who you could not match.
```

### Call Bloomerang 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/bloomerang 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/bloomerang/constituents/48211/donations \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date":"2026-10-19","amount":150,"method":"Check","fund":"General Fund","campaign":"Fall Appeal 2026","appeal":"Fall mailer"}'
```

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

```
{
  "id": 90533,
  "constituent_id": 48211,
  "date": "2026-10-19",
  "amount": 150,
  "method": "Check",
  "fund": "General Fund",
  "campaign": "Fall Appeal 2026",
  "appeal": "Fall mailer",
  "acknowledgement_sent": false
}
```

## Why use Cotlet for Bloomerang?

**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 Bloomerang 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 Bloomerang changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Bloomerang to Cotlet?

Yes. You sign in to Bloomerang yourself, in your own Cloud Browser, and we never save your password. Your agents only get Bloomerang 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 Bloomerang integration?**

No, Cotlet is independent of Bloomerang. Bloomerang's own API is too limited for this work. Cotlet works through your own Bloomerang account, the way you use Bloomerang 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 Bloomerang in your console: your agents lose access at once and you stay signed in. Signing out of Bloomerang in the browser works too, and Reset browser deletes the whole profile.

## Is there a Bloomerang MCP server on GitHub?

Bloomerang has no MCP server of its own. Zapier's Bloomerang app, which an agent can reach through Zapier, gives you a fixed set of 6 actions and 2 searches. It cannot merge duplicates, filter by lifecycle stage or read a donor's gift history. Cotlet works in your signed-in Bloomerang and covers those screens. It runs alongside Zapier, not instead of it.

|  | Zapier | Cotlet |
|---|---|---|
| Setup | Connect Bloomerang to Zapier, pick the actions your agent may use | Sign up, sign in to Bloomerang once, add one MCP server or API key |
| What it covers | 6 actions and 2 searches: create and update constituents, donations, interactions and tasks | Also duplicates and merging, lifecycle filters, gift and interaction history |
| When Bloomerang changes | You get the actions Zapier has published | Our team tests it daily and fixes it for you; failed calls are free |
| Your Bloomerang access | Zapier holds the connection to your database | Signed in inside your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| Upkeep | Zaps and connections are yours to maintain | Nothing to host or update |
| Where it runs | Inside Zapier, or from AI tools through its MCP | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Your Zapier plan | 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 Bloomerang 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 Bloomerang API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Bloomerang 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 20 to 30 credits (25 for most tools, about $0.10 to $0.15), 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 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $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 Bloomerang 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 Bloomerang 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 Bloomerang only after you enable it. When Bloomerang 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 Bloomerang, sign out of Bloomerang 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.
- **Bloomerang's terms:** You use your own Bloomerang account and stay responsible for following Bloomerang's terms. Cotlet is independent and not affiliated with Bloomerang. [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 Bloomerang in the console and press Request access. Then you create your API key and connect Bloomerang there.

**Do I need to be technical?**

No. You sign in to Bloomerang 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 Bloomerang to Cotlet?**

Yes. You sign in to Bloomerang yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Bloomerang 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 Bloomerang 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 Bloomerang 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 Bloomerang's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Bloomerang 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 Bloomerang 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?**

Bloomerang 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).

**Which Bloomerang role does my agent need?**

The role of the account you sign in with. A standard user whose Transactions permission is View only cannot add gifts, and No access cannot view them. The Duplicate Constituents page is for admins; a standard user can merge by default, but not without the Data Tools permission. A call without the role fails with APP_PERMISSION_DENIED.

**Can my agent charge a card or refund a gift?**

No. record_donation only records gifts that already arrived by Cash, Check, In Kind or an outside payment service, and Credit Card, EFT and Saved Payment are refused because they process a payment in Bloomerang. No tool refunds or deletes a gift; Bloomerang has its own Refund or Delete Donations steps in the app.

**Do I need a Bloomerang API key?**

No. Cotlet works in your signed-in Bloomerang account and does not use the private REST API key, which an administrator creates in User Settings and which can change any data in the database.

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

No. Every call to record_donation or merge_constituents waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_constituent, update_constituent, add_interaction, create_task runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Bloomerang 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/bloomerang 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 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.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.