Breeze ChMS MCP by usefulapi
Manage Breeze ChMS people, tags, events, check-ins, volunteers and contributions
Reviews
No review yet. Used Breeze ChMS MCP by usefulapi? Be the first to help others choose.What it does
Breeze ChMS MCP by usefulapi is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 4h ago (live check)Hosted endpoint
https://breeze-chms.usefulapi.io/mcpstreamable-http
In Claude Code: claude mcp add --transport http breeze-chms https://breeze-chms.usefulapi.io/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"breeze-chms": {
"url": "https://breeze-chms.usefulapi.io/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 4h agoONLINE Breeze ChMS MCP by usefulapi answered an MCP connection on 17 Nov 2026 and introduced itself as breeze-chms-mcp 1.40.0 (MCP protocol 2025-06-18).
24 tools offered to AI assistants
breeze_get_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.breeze_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 keyebreeze_get_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}.breeze_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 withbreeze_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.breeze_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 anbreeze_get_event· 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.breeze_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.breeze_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.breeze_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.breeze_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.breeze_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.
Show 12 more
breeze_list_volunteers· Volunteers scheduled for one event instance: person_id, response, comment, rsvped_on and role_ids. Breeze: GET /api/volunteers/list.breeze_list_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.breeze_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: GETbreeze_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 endpoibreeze_add_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 includbreeze_update_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_pbreeze_add_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.breeze_assign_tag· 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.breeze_unassign_tag· 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.breeze_add_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: GETbreeze_record_attendance· 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/attbreeze_schedule_volunteer· WRITE: schedule one person as a volunteer for one event instance. Breeze: GET /api/volunteers/add.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Version | 1.40.0 | DECLARED | SRC-001 Official MCP Registry | 9h ago |
| Hosted endpoint | https://breeze-chms.usefulapi.io/mcp | DECLARED | SRC-001 Official MCP Registry | 9h ago |
| Website | https://usefulapi.io/breeze-chms/ | DECLARED | SRC-001 Official MCP Registry | 9h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 9h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 9h ago |
| Repository | https://github.com/m190/usefulapi-mcp | DECLARED | SRC-001 Official MCP Registry | 9h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 9h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 9h ago |
Change history
- VERSION16 Nov 20261.39.3 → 1.40.0
- VERSION16 Nov 20261.39.2 → 1.39.3
- VERSION14 Nov 20261.39.1 → 1.39.2
- VERSION13 Nov 20261.39.0 → 1.39.1
- VERSION13 Nov 20261.38.0 → 1.39.0
- VERSION11 Nov 20261.37.3 → 1.38.0
- VERSION11 Nov 20261.37.2 → 1.37.3
- VERSION10 Nov 20261.37.1 → 1.37.2
- VERSION10 Nov 20261.37.0 → 1.37.1
- VERSION10 Nov 20261.36.5 → 1.37.0
- VERSION07 Nov 20261.36.4 → 1.36.5
- VERSION07 Nov 20261.36.3 → 1.36.4
- VERSION07 Nov 20261.36.2 → 1.36.3
- VERSION06 Nov 20261.36.1 → 1.36.2
- VERSION06 Nov 20261.35.4 → 1.36.1
- VERSION06 Nov 20261.35.3 → 1.35.4
- VERSION05 Nov 20261.35.2 → 1.35.3
- VERSION05 Nov 20261.35.1 → 1.35.2
- VERSION03 Nov 20261.35.0 → 1.35.1
- VERSION03 Nov 20261.34.1 → 1.35.0
- VERSION03 Nov 20261.34.0 → 1.34.1
- VERSION02 Nov 20261.33.0 → 1.34.0
- VERSION31 Oct 20261.32.0 → 1.33.0
- VERSION31 Oct 20261.31.0 → 1.32.0
- VERSION31 Oct 20261.30.0 → 1.31.0
- VERSION31 Oct 20261.29.2 → 1.30.0
- VERSION30 Oct 20261.29.1 → 1.29.2
- VERSION30 Oct 20261.29.0 → 1.29.1
- VERSION29 Oct 20261.28.0 → 1.29.0
- VERSION29 Oct 20261.27.0 → 1.28.0
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Breeze ChMS MCP by usefulapi still online?
Free alerts · no account▲ 0Do you run Breeze ChMS MCP by usefulapi? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Breeze ChMS MCP by usefulapi
How do I connect Breeze ChMS MCP by usefulapi?
Use the hosted endpoint https://breeze-chms.usefulapi.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Breeze ChMS MCP by usefulapi offer?
When Electra Index connected on 17 Nov 2026, it listed 24 tools: breeze_get_account_summary, breeze_list_people, breeze_get_person, breeze_list_profile_fields, breeze_list_tags, breeze_list_events, breeze_get_event, breeze_list_calendars and more. The full list is in "Live check" above.
Is Breeze ChMS MCP by usefulapi online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 4h ago.