Breeze ChMS MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Breeze ChMS MCP by usefulapi is answering right now. Last checked 8 min ago. It exposes 24 tools. Last commit 10 Oct 2026.

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

Uptime history 13 days of history

13 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

107 ms

Response time

average over 24h

Stars

last commit 10 Oct 2026

What changed 8

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 September 2026. No other catalogue keeps this.

9 Oct a tool changed version4 times that day

7 Oct a tool changed version

30 Sep a tool changed version3 times that day

and 5 more, back to 30 September 2026

What the code does

We read the source, 5 h ago · tools taken from the live server · rules ccca72095570

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Page executes code built at runtime portal/index.html:239

        results.innerHTML = order.map(function (g) {

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add breeze-chms --transport http https://breeze-chms.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "breeze-chms": {
      "url": "https://breeze-chms.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.breeze-chms]
url = "https://breeze-chms.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "breeze-chms": {
      "url": "https://breeze-chms.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "breeze-chms": {
      "url": "https://breeze-chms.usefulapi.io/mcp"
    }
  }
}

Available tools 24

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

breeze

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: GET /api/events/add.

breeze_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 including its id. Breeze: GET /api/people/add.

breeze_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_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_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_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_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_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_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_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.

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 and may lag up to 15 minutes. Breeze: GET /api/events.

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.

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_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_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.

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 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.

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 with breeze_add_person / breeze_update_person. Breeze: GET /api/profile.

breeze_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_volunteers

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

breeze_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/attendance/add.

breeze_schedule_volunteer

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

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_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_person if you may need to restore them). field_id and option ids come from breeze_list_profile_fields. Breeze: GET /api/people/update.

Endpoints

URL	Transport	State	Latency	Checked
https://breeze-chms.usefulapi.io/mcp	streamable-http	answering	75 ms	8 min ago

Alternatives to Breeze ChMS MCP by usefulapi

same job, measured the same way

Encharge MCP by usefulapi

by usefulapi

Manage Encharge people, tags, segments and fields, and track events for email automation.

10 tools answering

Humanitix MCP by usefulapi

by usefulapi

Read Humanitix events, orders, tickets and live check-in counts, and check tickets in or out.

15 tools answering

Loops MCP by usefulapi

by usefulapi

Manage Loops contacts, mailing lists, and transactional/event emails.

10 tools answering

Pipeline CRM MCP by usefulapi

by usefulapi

Manage Pipeline CRM deals, people, companies, notes and calendar entries.

30 tools answering

Re:amaze MCP by usefulapi

by usefulapi

Manage Re:amaze conversations, messages, contacts and help articles.

17 tools answering

Wild Apricot MCP by usefulapi

by usefulapi

Look up members, events, registrations, invoices and payments, and add contacts or check in guests.

21 tools answering

Bookeo MCP by usefulapi

by usefulapi

Check Bookeo availability and manage bookings, holds and customers; read payments.

21 tools answering

Groove MCP by usefulapi

by usefulapi

Read Groove shared-inbox conversations, contacts, agents and tags; close, assign, snooze and tag.

16 tools answering

Breeze ChMS MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Breeze ChMS MCP by usefulapi do?

It exposes 24 tools, read directly from the server on our last check. Among them: breeze_add_event, breeze_add_person, breeze_add_tag, breeze_assign_tag, breeze_get_account_summary, breeze_get_event and 18 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Breeze ChMS MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 107 ms. The bar chart above shows every period we have measured.

How do I connect Breeze ChMS MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Breeze ChMS MCP by usefulapi need an API key?

No. Breeze ChMS MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 24 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Breeze ChMS MCP by usefulapi?

It answers our handshake in 107 ms on average, which is faster than 82% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Breeze ChMS MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.