Breeze ChMS MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.39.2Updated Nov 14, 2026

Manage Breeze ChMS people, tags, events, check-ins, volunteers and contributions.

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Hosted MCP server that lets an assistant read and update Breeze ChMS church data: people, tags, events, attendance, volunteers and contributions.

What you can do
  • Read people, profile fields, tags, calendars, events and account summaries
  • Review attendance, forms, form fields and form entries
  • List volunteers, funds, contributions and the account log
  • Add or update people, create and assign or remove tags
  • Add events, check people in or out, and schedule volunteers
  • Check usage, request a feature, and upgrade or cancel the paid plan
When to use it
Useful for church or nonprofit staff who already run Breeze ChMS and want to ask questions in plain language, such as attendance counts, giving totals by fund, or who is volunteering this Sunday, and to make small record updates without opening the Breeze interface.
Requirements
A remote endpoint reached over streamable HTTP; no local install. Sign-in uses OAuth, and the login page asks for your Breeze subdomain and API key (found under Extensions, API). Do not add an Authorization header or API key to the client config. A free tier allows 50 tool calls per month.
Before you install
Write tools add or update people, create and assign tags, add events, record check-ins and schedule volunteers, so confirm before letting them run. The server stores your Breeze subdomain and API key per user. Paid plans are billed through Stripe Checkout links, and plan changes charge a prorated difference immediately; cancellation gives no refund for the current period. Usage is metered per tool call.

Installation

In SourceWeft

  1. Open Breeze ChMS MCP by usefulapi in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.usefulapi%2Fbreeze-chms/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "breeze-chms-by-usefulapi": {
      "type": "http",
      "url": "https://breeze-chms.usefulapi.io/mcp"
    }
  }
}

README

Breeze ChMS MCP by usefulapi

Use Breeze ChMS from Claude, Cursor, or any MCP client — read people, tags, events, attendance and contributions, add people, manage tags, check people in, and schedule volunteers. Hosted, no local install: connect with your own Breeze ChMS credentials.

Live endpoint: https://breeze-chms.usefulapi.io/mcp · Homepage: https://usefulapi.io/breeze-chms

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://breeze-chms.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http breeze-chms https://breeze-chms.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
json
{  "mcpServers": {    "breeze-chms": {      "url": "https://breeze-chms.usefulapi.io/mcp"    }  }}

Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Breeze ChMS credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/breeze-chms/

On first connect you'll provide your Breeze subdomain and API key (Extensions → API). They're validated, stored per-user, and scoped to you — no keys in config files.

Tools

ToolTypeWhat it does
breeze_get_account_summaryreadGet the account summary
breeze_list_peoplereadList people
breeze_get_personreadGet a person
breeze_list_profile_fieldsreadList profile fields
breeze_list_tagsreadList tags
breeze_list_eventsreadList events
breeze_get_eventreadGet an event instance
breeze_list_calendarsreadList calendars
breeze_list_attendancereadList attendance
breeze_list_formsreadList forms
breeze_list_form_fieldsreadList form fields
breeze_list_form_entriesreadList form entries
breeze_list_volunteersreadList volunteers
breeze_list_account_logreadList the account log
breeze_list_fundsreadList funds
breeze_list_contributionsreadList contributions
breeze_add_personwriteAdd a person
breeze_update_personwriteUpdate a person
breeze_add_tagwriteCreate a tag
breeze_assign_tagwriteAssign a tag to a person
breeze_unassign_tagwriteRemove a tag from a person
breeze_add_eventwriteAdd an event
breeze_record_attendancewriteCheck a person in or out
breeze_schedule_volunteerwriteSchedule a volunteer
breeze_chms_usage_statusmetaUsage status (free-tier meter)
breeze_chms_request_featuremetaRequest a missing feature
breeze_chms_upgrademetaUpgrade to Pro or Pro+
breeze_chms_cancel_subscriptionmetaCancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

PlanPriceLimit
Free$050 tool calls / month
Pro (per user)$9/mo or $90/yr (2 months free)10,000 tool calls / month
Pro+ (per user)$39/mo or $390/yr (2 months free)100,000 tool calls / month

Each paid plan covers this server only. Ask your AI to run breeze_chms_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with breeze_chms_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with breeze_chms_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT © usefulapi. Not affiliated with or endorsed by Breeze ChMS.

Source: servers/breeze-chms/README.md at commit 3c1b3df

Tools

24

breeze_get_account_summary

Get the account summary

The church account this key belongs to: name, subdomain, status, timezone and country/currency. A cheap way to confirm BREEZE_SUBDOMAIN and BREEZE_API_KEY are right. Breeze: GET /api/account/summary.

Takes no parameters.

breeze_list_people

List people

List people in the church database, optionally filtered (by tag, status, gender, etc.) and paginated with limit/offset. Without details you get id, first_name, last_name and photo path; with details=true every profile field is returned keyed by field_id (slower). Filter keys are profile field_ids (see breeze_list_profile_fields) or special keys, e.g. {"tag_contains":"y_16681"} for people in a tag, or {"2000138015":"226-227"} for a Status field matching options 226 or 227. Breeze: GET /api/people.

Parameterslimitfilteroffsetdetails

breeze_get_person

Get a person

Fetch one person's profile by id, including address and — by default — every profile field keyed by field_id, plus family members. Pair with breeze_list_profile_fields to label the field ids. Breeze: GET /api/people/{person_id}.

Parametersdetailsperson_idrequired

breeze_list_profile_fields

List profile fields

The church's profile layout: sections, each with its fields (field_id, field_type, name) and, for multiple-choice fields, their options (option_id, name). Needed to read person details, to build list_people filters, and to write fields with breeze_add_person / breeze_update_person. Breeze: GET /api/profile.

Takes no parameters.

breeze_list_tags

List tags

List tags (Breeze's groups/lists) with id, name, created_on and folder_id, optionally only those in one folder. To list the people in a tag, call breeze_list_people with filter {"tag_contains":"y_<tag_id>"}. Breeze: GET /api/tags/list_tags.

Parametersfolder_id

breeze_list_events

List events

List event instances in a date range (default: the current month), optionally on one calendar. Each row's `id` is the INSTANCE id used by attendance, volunteer and get_event tools; `event_id` is the series. Responses are cached by Breeze and may lag up to 15 minutes. Breeze: GET /api/events.

Parametersendlimitstartdetailseligiblecategory_id

breeze_get_event

Get an event instance

Fetch one event instance, optionally with the other instances in its series (then the response is an array of {id, start} only). Cached by Breeze, may lag up to 15 minutes. Breeze: GET /api/events/list_event.

Parametersdetailseligiblescheduleinstance_idrequiredschedule_limitschedule_direction

breeze_list_calendars

List calendars

List the church's event calendars (id, name, color and iCal feed address). The id is the category_id for breeze_list_events and breeze_add_event. Breeze: GET /api/events/calendars/list.

Takes no parameters.

breeze_list_attendance

List attendance

Who checked in to one event instance (person_id, check-in time created_on, check_out), optionally with each person's details, or the anonymous head count instead. Breeze: GET /api/events/attendance/list.

Parameterstypedetailsinstance_idrequired

breeze_list_forms

List forms

List the church's online forms (id, name, url_slug, is_archived) — active ones by default, or archived ones. Breeze: GET /api/forms/list_forms.

Parametersarchived

breeze_list_form_fields

List form fields

The fields of one form (field_id, field_type, name, options). Form entry responses are keyed by these field_ids. Breeze: GET /api/forms/list_form_fields.

Parametersform_idrequired

breeze_list_form_entries

List form entries

Submissions to one form (id, created_on, person_id), and with details=true each entry's responses keyed by form field_id (see breeze_list_form_fields). Breeze: GET /api/forms/list_form_entries.

Parametersdetailsform_idrequired

breeze_list_volunteers

List volunteers

Volunteers scheduled for one event instance: person_id, response, comment, rsvped_on and role_ids. Breeze: GET /api/volunteers/list.

Parametersinstance_idrequired

breeze_list_account_log

List the account log

The account's audit log for one action type (e.g. person_updated, tag_assign, contribution_added), optionally within a date range or by one user. Good for 'what changed since…' and incremental sync. Breeze: GET /api/account/list_log.

Parametersendlimitstartactionrequireddetailsuser_id

breeze_list_funds

List funds

List giving funds (id, name, tax_deductible, is_default), optionally with the total given to each. Legacy endpoint: no longer shown on Breeze's current API reference; churches whose giving runs through Tithely may get an error. Breeze: GET /api/funds/list.

Parametersinclude_totals

breeze_list_contributions

List contributions

List recorded contributions (gifts) given within a date range, optionally narrowed by giver (with their family), amount, payment method, fund, envelope, batch or form. Read-only: this server never adds, edits or deletes gifts. Legacy endpoint: no longer shown on Breeze's current API reference; churches whose giving runs through Tithely may get an error. Breeze: GET /api/giving/list.

Parametersendrequiredformsstartrequiredbatchesfund_idsperson_idamount_maxamount_minmethod_idsinclude_familyenvelope_number

breeze_add_person

Add a person

WRITE: create a new person profile with a first and last name, and optionally set profile fields in the same call (same field shape as breeze_update_person). Check breeze_list_people first to avoid duplicates. Returns the new profile including its id. Breeze: GET /api/people/add.

Parameterslastrequiredfirstrequiredfields

breeze_update_person

Update a person

WRITE: set profile fields on an existing person — email, phone, address, dates, multiple-choice options, family role, and custom fields. Only the fields you pass change; the previous values are overwritten (read them first with breeze_get_person if you may need to restore them). field_id and option ids come from breeze_list_profile_fields. Breeze: GET /api/people/update.

Parametersfieldsrequiredperson_idrequired

breeze_add_tag

Create a tag

WRITE: create a new tag, at the top level or inside a folder. Returns the new tag with its id. Breeze: GET /api/tags/add_tag.

Parametersnamerequiredfolder_id

breeze_assign_tag

Assign a tag to a person

WRITE: add a tag to one person (e.g. put them in a small group or list). Undo with breeze_unassign_tag. Breeze: GET /api/tags/assign.

Parameterstag_idrequiredperson_idrequired

breeze_unassign_tag

Remove a tag from a person

WRITE: remove a tag from one person. The person and the tag both remain; re-assign with breeze_assign_tag. Breeze: GET /api/tags/unassign.

Parameterstag_idrequiredperson_idrequired

breeze_add_event

Add an event

WRITE: create an event on the church calendar, optionally as another instance of an existing series. Times are Unix timestamps in seconds. This server cannot delete events, so a mistaken event must be removed in the Breeze app. Breeze: GET /api/events/add.

Parametersnamerequiredall_dayends_onevent_idstarts_onrequiredcategory_iddescription

breeze_record_attendance

Check a person in or out

WRITE: record attendance for one person at one event instance — check them in (default) or check them out (records when they left; checking out someone not checked in creates a record with matching in/out times). Breeze: GET /api/events/attendance/add.

Parametersdirectionperson_idrequiredinstance_idrequired

breeze_schedule_volunteer

Schedule a volunteer

WRITE: schedule one person as a volunteer for one event instance. Breeze: GET /api/volunteers/add.

Parametersperson_idrequiredinstance_idrequired

Version history

26
  1. v1.39.2LatestNov 14, 2026
  2. v1.39.1Nov 13, 2026
  3. v1.38.0Nov 12, 2026
  4. v1.37.3Nov 11, 2026
  5. v1.36.5Nov 8, 2026
  6. v1.36.4Nov 7, 2026
  7. v1.35.3Nov 5, 2026
  8. v1.35.2Nov 5, 2026
  9. v1.35.1Nov 4, 2026
  10. v1.35.0Nov 3, 2026
  11. v1.34.1Nov 3, 2026
  12. v1.33.0Nov 1, 2026
  13. v1.31.0Oct 31, 2026
  14. v1.30.0Oct 31, 2026
  15. v1.29.2Oct 30, 2026
  16. v1.29.0Oct 30, 2026
  17. v1.24.0Oct 26, 2026
  18. v1.21.3Oct 25, 2026
  19. v1.21.0Oct 25, 2026
  20. v1.20.0Oct 24, 2026
  21. v1.17.0Oct 23, 2026
  22. v1.16.4Oct 22, 2026
  23. v1.16.3Oct 21, 2026
  24. v1.11.1Oct 9, 2026
  25. v1.10.0Oct 9, 2026
  26. v1.0.0Sep 29, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Usefulapi integrations