Bloomerang MCP by usefulapi

Reviewed 1d ago.

• tools: 20 tools scanned
• metadata: scanned

No findings.

Tools (20)

• bloomerang_get_current_user

  Fetch the Bloomerang user the API key belongs to — name, email and permission level. A cheap way to confirm the key works and see what it may do. Bloomerang: GET /user/current.

• bloomerang_search_constituents

  Full-text search across constituents (individuals and organizations) and households by name, email, etc. Start here to find a donor's Id. Bloomerang: GET /constituents/search.

• bloomerang_list_constituents

  List constituents with filters — by Id, type, favorites, last-modified date, or a custom field value — and sorting. Good for syncing recent changes. Bloomerang: GET /constituents.

• bloomerang_get_constituent

  Fetch one constituent's full profile — names, primary and secondary contact details, household, communication preferences, engagement score and custom values. Bloomerang: GET /constituent/{id}.

• bloomerang_get_constituent_timeline

  The activity timeline for a constituent — gifts, interactions, notes, tasks and more, newest first. Pass a household Id to get the timeline of every member. Bloomerang: GET /constituent/{id}/timeline.

• bloomerang_list_constituent_relationships

  Relationships between this constituent and others (spouse, employer, board member ...), with the role on each side. Bloomerang: GET /constituent/{id}/relationships.

• bloomerang_get_household

  Fetch a household — its names, head of household (HeadId) and member constituent Ids. A constituent's HouseholdId points here. Bloomerang: GET /household/{id}.

• bloomerang_list_transactions

  List transactions — donations, pledges, pledge payments, recurring donations and their payments — with their designations (fund, campaign, appeal). Filter by constituent, amount range, type or last-modified date. Read only. Bloomerang: GET /transactions.

• bloomerang_get_transaction

  Fetch one transaction with its payment method, amounts, refund status and every designation (fund, campaign, appeal, tribute, acknowledgement status). Bloomerang: GET /transaction/{id}.

• bloomerang_list_funds

  List the funds gifts can be designated to (e.g. General Operating, Scholarship). Bloomerang: GET /funds.

• bloomerang_list_campaigns

  List fundraising campaigns with their goals and dates. Bloomerang: GET /campaigns.

• bloomerang_list_appeals

  List appeals — the specific asks (a year-end letter, a gala invitation) that gifts are attributed to. Bloomerang: GET /appeals.

• bloomerang_list_interactions

  List logged interactions (calls, emails, meetings, letters ...) — filter by constituent, channel or purpose. Bloomerang: GET /interactions.

• bloomerang_list_notes

  List notes, optionally for specific constituents. Bloomerang: GET /notes.

• bloomerang_list_tasks

  List tasks (follow-ups) — filter by status, due-date range, assignee user, constituent, channel or purpose. Bloomerang: GET /tasks.

• bloomerang_create_constituent

  WRITE: create a new individual or organization constituent. For an individual give first_name/last_name; for an organization give full_name. Search first (bloomerang_search_constituents) to avoid creating a duplicate donor. Bloomerang: POST /constituent.

• bloomerang_update_constituent

  WRITE: update fields on an existing constituent's profile (names, job, status, primary address/email/phone). Only the fields you supply are sent. Bloomerang: PUT /constituent/{id}.

• bloomerang_create_interaction

  WRITE: log an interaction with a constituent — a call, email, meeting, letter, etc. — on their timeline. Bloomerang: POST /interaction.

• bloomerang_create_note

  WRITE: add a note to a constituent's record. Bloomerang: POST /note.

• bloomerang_create_task

  WRITE: create a follow-up task, optionally tied to a constituent and assigned to a user (find user Ids via bloomerang_get_current_user or existing tasks). Bloomerang: POST /task.