Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Bloomerang to Claude Code

Make Claude log gifts and update constituent records in Bloomerang. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Bloomerang to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Bloomerang, you add a Bloomerang MCP server: a small hosted service that exposes Bloomerang's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Bloomerang account. No API keys pasted into config files.

claude mcp add --transport http bloomerang https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Bloomerang once connected?

Full read-write Bloomerang access lets Claude log a gift to the right constituent, update contact details and household links, create interactions and notes, set custom field values, and attribute a gift to the right fund, campaign, or appeal when you log it. The record-keeping that used to mean manual data entry happens inside Bloomerang, after you approve it.

  • Log a gift or pledge against the correct constituent record
  • Create an interaction or note documenting a call, visit, or email
  • Update constituent contact details, addresses, and household links
  • Set custom field values on a constituent record to support segmentation
  • Attribute a logged gift to the correct fund, campaign, or appeal
  • Create a new constituent record from intake details you provide

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Bloomerang access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Bloomerang API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Bloomerang changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Bloomerang connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Bloomerang connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Bloomerang account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Bloomerang's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Bloomerang?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Bloomerang account it signs in with. Revoking access is one click in Bloomerang.

More on the Bloomerang connector

Bloomerang connector for claude.aiMyCase + Claude CodePracticePanther + Claude CodeFilevine + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us