usefulapiBreeze ChMS MCP server
Manage Breeze ChMS people, tags, events, check-ins, volunteers and contributions. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
What can I ask?
Turn on the Breeze ChMS connector, then ask in plain words. The AI picks the tools.
- How many people attended last Sunday's service?
- Show the total giving for the past month by fund.
- Who is scheduled to volunteer at this Sunday's service?
- Add a new person named John Brown to the church database.
What you can do with Breeze ChMS in Claude and ChatGPT
For church staff and volunteer coordinators who manage their congregation in Breeze ChMS.
Find people by tag, status or profile field
The AI lists people filtered by tag, status, gender or other profile fields and opens a profile with address and family members. You get a list for a group or mailing.
Review who checked in to an event
The AI finds event instances in a date range and reads who checked in, with check-in time, or only the head count.
See who is scheduled to volunteer for an event
The AI reads the volunteers scheduled for one event instance with their response, comment and roles, so you can see who still has to answer.
Review gifts given in a date range
The AI lists recorded contributions in a date range, narrowed by giver, amount, payment method, fund or batch, and sums them per fund. It does not change gifts.
Add or update a person and tag them
The AI checks for duplicates, adds a person or changes profile fields such as email, phone and address, and assigns a tag such as a small group.
Changes dataAdd an event, record attendance or schedule a volunteer
The AI adds an event to a church calendar, checks a person in or out at an event instance, or schedules a person as a volunteer for it.
Changes dataHow do I connect Breeze ChMS?
Before you connect
The login page asks for your Breeze subdomain and Breeze API key.
The subdomain is the part before .breezechms.com in your Breeze web address. Find the API key in Breeze → Extensions → API (API access comes with a paid Breeze subscription). Your key is used only to call the Breeze API on your behalf and to derive a private account id; it is never shown to anyone.
Claude claude.ai · Desktop
- Open Customize → Connectors, then click + Add → Add custom connector.
- Enter the name Breeze ChMS and this URL, then click Add:https://
breeze-chms. usefulapi. io/ mcp - Claude opens the login page: enter your Breeze subdomain and Breeze API key.
- In a chat, click + → Connectors and turn on Breeze ChMS.
Team and Enterprise: an Owner adds the connector for the organization first.
ChatGPT chatgpt.com
- Open Plugins, click +, then Add custom MCP server.
- Enter the name Breeze ChMS and this URL, choose OAuth as the authentication, confirm the warning and create it:https://
breeze-chms. usefulapi. io/ mcp - ChatGPT opens the login page: enter your Breeze subdomain and Breeze API key.
- In Plugins, install Breeze ChMS, then choose it in a chat.
No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Claude Code
Run this command, then run /mcp in Claude Code to log in:
Cursor
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"breeze-chms": {
"url": "https://breeze-chms.usefulapi.io/mcp"
}
}
} VS Code
Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"breeze-chms": {
"type": "http",
"url": "https://breeze-chms.usefulapi.io/mcp"
}
}
} Codex
Run these commands. The second one opens the login page:
Other clients
Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.
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: the login page asks for your Breeze subdomain and Breeze API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Pricing
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | 10,000 tool calls / month |
| Pro+per user | $39/mo · $390/yr | 100,000 tool calls / month |
Each paid plan covers this Breeze ChMS 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 support@usefulapi.io.
Tools 28
Show all 28 tools (the AI picks them for you)
Read only · 16
- Get the account summary
breeze_get_account_summaryThe 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. - List people
breeze_list_peopleList 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. - Get a person
breeze_get_personFetch 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. - List profile fields
breeze_list_profile_fieldsThe 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. - List tags
breeze_list_tagsList 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>"}. - List events
breeze_list_eventsList 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. - Get an event instance
breeze_get_eventFetch 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. - List calendars
breeze_list_calendarsList 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. - List attendance
breeze_list_attendanceWho 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. - List forms
breeze_list_formsList the church's online forms (id, name, url_slug, is_archived) — active ones by default, or archived ones. - List form fields
breeze_list_form_fieldsThe fields of one form (field_id, field_type, name, options). Form entry responses are keyed by these field_ids. - List form entries
breeze_list_form_entriesSubmissions 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). - List volunteers
breeze_list_volunteersVolunteers scheduled for one event instance: person_id, response, comment, rsvped_on and role_ids. - List the account log
breeze_list_account_logThe 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. - List funds
breeze_list_fundsList 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. - List contributions
breeze_list_contributionsList 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.
Changes data · 8
- Add a person
breeze_add_personWRITE: 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. - Update a person
breeze_update_personWRITE: 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. - Create a tag
breeze_add_tagWRITE: create a new tag, at the top level or inside a folder. Returns the new tag with its id. - Assign a tag to a person
breeze_assign_tagWRITE: add a tag to one person (e.g. put them in a small group or list). Undo with breeze_unassign_tag. - Remove a tag from a person
breeze_unassign_tagWRITE: remove a tag from one person. The person and the tag both remain; re-assign with breeze_assign_tag. - Add an event
breeze_add_eventWRITE: 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. - Check a person in or out
breeze_record_attendanceWRITE: 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). - Schedule a volunteer
breeze_schedule_volunteerWRITE: schedule one person as a volunteer for one event instance.
Your usefulapi plan · 4
- Usage status (free-tier meter)
breeze_chms_usage_statusReport the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. - Request a missing feature
breeze_chms_request_featureTell usefulapi that the user needs something the Breeze ChMS tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. - Upgrade to Pro or Pro+
breeze_chms_upgradeGet a paid plan for Breeze ChMS (the free tier caps monthly usage). Pro: 10,000 tool calls a month, for normal use — plan "monthly" ($9/month) or "yearly" ($90/year, 2 months free). Pro+: 100,000 tool calls a month, for automations and heavy use — plan "plus" ($39/month) or "plus_yearly" ($390/year). Without a plan it returns both Pro and Pro+, each with a payment link, for the user to choose; with a plan, one link. An existing Pro subscription changes to Pro+ in place: call without confirm first, as the reply states the exact charge for this account (the price difference for the rest of the period, or in a free Pro trial the full Pro+ price, as the trial ends); then call with confirm: true. Cancel any time: the plan then runs to the end of the paid period, so it also suits a one-time job. A link opens Stripe Checkout in the browser; after payment the account upgrades automatically. Does not count against the meter. - Cancel the Pro subscription
breeze_chms_cancel_subscriptionCancel the caller's Breeze ChMS Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run breeze_chms_upgrade later to undo the cancel before the period ends. Does not count against the meter.
FAQ
What can I do with Breeze ChMS in Claude or ChatGPT?
Find people by tag, status or profile field. Review who checked in to an event. See who is scheduled to volunteer for an event. Review gifts given in a date range. Add or update a person and tag them. Add an event, record attendance or schedule a volunteer. See what you can do for the details.
Is this an official Breeze ChMS product?
No. usefulapi is an independent service. It is not affiliated with or endorsed by Breeze ChMS. The server calls the Breeze ChMS API with your own Breeze ChMS access, so it sees only the data that your account can see.
Can I connect Breeze ChMS to Claude or ChatGPT?
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
What do I need to connect?
The login page asks for your Breeze subdomain and Breeze API key. See Before you connect for where to find them.
Do I put my Breeze ChMS key or an Authorization header in the client config?
No. 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: the login page asks for your Breeze subdomain and Breeze API key. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
How do you keep my Breeze ChMS credentials?
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Breeze ChMS API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Breeze ChMS.
Can the AI change my Breeze ChMS data?
Yes, if you approve it. 8 of the 24 Breeze ChMS tools can create or change data. The other 16 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
What does it cost?
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this Breeze ChMS server only. Cancel any time: your paid plan then runs to the end of the paid period. Run breeze_chms_usage_status to see how many calls you used.
How do I subscribe or cancel?
Ask the 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+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run breeze_chms_cancel_subscription. Your paid plan continues to the end of the paid period.
What if a Breeze ChMS tool that I need is missing?
Tell the AI what you wanted to do. It can send the request with breeze_chms_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Which AI clients can I use?
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.