Bloomerang MCP Server
# Bloomerang MCP server for ChatGPT and Claude
Bloomerang has a REST API for server-to-server integrations. The Cotlet.dev integration page reports no official Bloomerang MCP server, checked 22 October 2026. Cotlet.dev connects ChatGPT, Claude and other AI agents to constituents, gifts, interactions and duplicate records in your signed-in Bloomerang account. This repository provides a local MCP adapter to Cotlet.dev browser tools.
## What you can ask
> Find lapsed donors and prepare follow-up tasks.
> Read a constituent record and gift history.
> Record a check donation after I confirm the details.
> Compare duplicate constituent records before I approve a merge.
## Connect in 2 minutes
Get your API key at https://cotlet.dev/app and export it as `COTLET_API_KEY`.
### ChatGPT
Settings → Apps & Connectors → Create, use `https://cotlet.dev/mcp/v1/connect` with OAuth, then sign in with Cotlet.dev. No API key needed.
### Claude Code
```bash
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"
```
### Cursor
Copy `.cursor/mcp.json` from this repo into your project:
```json
{
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": {
"Authorization": "Bearer ${COTLET_API_KEY}"
}
}
}
}
```
## Run it locally (stdio)
This repo is a real MCP server. It speaks MCP over stdio, lists its Bloomerang tools without any key, and forwards every tool call to the hosted Cotlet.dev server. The hosted URL above stays the recommended way. Use this when your client only starts local servers.
```json
{"mcpServers":{"bloomerang":{"command":"uvx","args":["--from","git+https://github.com/cotlet-connect/bloomerang-mcp.git","bloomerang-mcp"],"env":{"COTLET_API_KEY":"your-key"}}}}
```
Or with Docker:
```bash
docker build -t bloomerang-mcp .
docker run -i --rm -e COTLET_API_KEY bloomerang-mcp
```
Tools: `bloomerang_guide`, `bloomerang_status`, `bloomerang_open`, `bloomerang_read`, `bloomerang_click`, `bloomerang_type`, `bloomerang_close`. Without `COTLET_API_KEY` a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".
## Command line
Python 3.10+, standard library only. Install from this repository:
```bash
pip install git+https://github.com/cotlet-connect/bloomerang-mcp.git
bloomerang-mcp connect
```
Or straight from this repo:
```bash
export COTLET_API_KEY="your-key"
python3 bloomerang_agent.py connect # ready config for Claude Code, Cursor, ChatGPT
python3 bloomerang_agent.py status # is Bloomerang ready in your Cotlet.dev account
python3 bloomerang_agent.py guide # Bloomerang screens and sign-in link
python3 bloomerang_agent.py read # open Bloomerang, read the page, close the browser
python3 bloomerang_agent.py tools # list Cotlet.dev tools
python3 bloomerang_agent.py serve # start the stdio MCP server (same as no argument)
```
## Questions from Bloomerang users
**Does Bloomerang have an API?**
Yes. Bloomerang has a REST API for server-to-server integrations. Cotlet.dev works in your signed-in Bloomerang account and does not require a Bloomerang private API key.
**Can ChatGPT and Claude work with Bloomerang?**
Yes. Sign up at https://cotlet.dev/signup?app=bloomerang, enable Bloomerang and sign in using your Cotlet.dev Cloud Browser. Add Cotlet.dev as a connector in ChatGPT or Claude.
**Can this charge a card or refund a gift?**
No. The hosted record_donation operation records gifts that already arrived. It does not charge cards, refund gifts or delete donations.
**What permissions apply?**
Calls use the permissions of the Bloomerang account you sign in with. Recording gifts and merging constituents require the relevant permissions. These two operations ask for confirmation by default.
**Is this official?**
No. Cotlet.dev is independent and is not affiliated with Bloomerang.
## Find it on
- [Bloomerang on Cotlet.dev](https://cotlet.dev/integrations/bloomerang-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=bloomerang&utm_content=find)
## Also works with
- [All apps connected through Cotlet.dev](https://github.com/cotlet-connect)
---
More: https://cotlet.dev/integrations/bloomerang-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=bloomerang
Start free: https://cotlet.dev/signup?app=bloomerang&utm_source=github&utm_medium=readme&utm_campaign=bloomerang
TDQS
Scored across 7 tools
Each tool maps to a distinct step in the browser workflow: onboarding guidance, account status, opening a page, reading it, clicking, typing, and closing. The boundaries between open/read/click/type/close are clear, and guide vs status is also distinguishable.
All tools share the bloomerang_ prefix and use short lowercase names, giving a predictable pattern. Minor deviation: guide and status are nouns rather than verbs, while the rest are actions.
Seven tools is well-scoped for a browser-automation server focused on Bloomerang. Each tool covers a necessary part of the workflow without redundant actions.
The surface covers the core browser lifecycle: onboarding, status, open, read, click, type, and close. Minor gaps exist around advanced interactions like scrolling, explicit waits, file upload, or dropdown selection, though many can be worked around with click and type.