A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
Breeze Chms is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
24
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Manage Breeze ChMS people, tags, events, check-ins, volunteers and contributions.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http breeze-chms-mcp https://breeze-chms.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# breeze_get_account_summary, breeze_list_people, breeze_get_person and 21 more
Breeze Chms costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http breeze-chms-mcp https://breeze-chms.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
24 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| details | boolean | no | true = every profile field (slower); false/omitted = id and name only. |
| filter | object | no | Filter object, sent as Breeze's filter_json, e.g. {"tag_contains":"y_16681"}. |
| limit | integer | no | Number of people to return. Omit to return everyone (can be large). |
| offset | integer | no | People to skip, for pagination with limit. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| person_id | string | yes | Numeric Breeze id of the person. |
| details | boolean | no | Defaults to true (all information). false = only id and name. |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| folder_id | string | no | Numeric Breeze id of the tag folder. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | no | Events on or after (YYYY-MM-DD). |
| end | string | no | Events on or before (YYYY-MM-DD). |
| category_id | string | no | Numeric Breeze id of the calendar (from breeze_list_calendars). |
| eligible | boolean | no | Include who is eligible to check in (everyone / tags / forms / none). |
| details | boolean | no | Include description, check-in settings, etc. |
| limit | integer | no | Max events, 1-1000 (Breeze default 500). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instance_id | string | yes | Numeric Breeze id of the event instance. |
| schedule | boolean | no | Also return other instances in the same series. |
| schedule_direction | string | no | With schedule: instances before (default) or after this one. |
| schedule_limit | integer | no | With schedule: how many series instances, 1-100 (default 10). |
| eligible | boolean | no | Include check-in eligibility details. |
| details | boolean | no | Include description, check-in settings, etc. |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instance_id | string | yes | Numeric Breeze id of the event instance. |
| details | boolean | no | Include each attendee's profile details. |
| type | string | no | person (default) = named check-ins; anonymous = head count. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| archived | boolean | no | true = list archived forms instead of active ones. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| form_id | string | yes | Numeric Breeze id of the form. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| form_id | string | yes | Numeric Breeze id of the form. |
| details | boolean | no | Include each entry's field responses. |
Volunteers scheduled for one event instance: person_id, response, comment, rsvped_on and role_ids. Breeze: GET /api/volunteers/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instance_id | string | yes | Numeric Breeze id of the event instance. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | Which logged action to return (required by Breeze). |
| start | string | no | Actions on or after (YYYY-MM-DD). |
| end | string | no | Actions on or before (YYYY-MM-DD). |
| user_id | string | no | Numeric Breeze id of the Breeze user who made the change. |
| details | boolean | no | Include a free-form description of each action (not standardized). |
| limit | integer | no | Max rows, 1-3000 (Breeze default 500). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_totals | boolean | no | Include the amount given to each fund. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | yes | Contributions given on or after (YYYY-MM-DD). |
| end | string | yes | Contributions given on or before (YYYY-MM-DD). |
| person_id | string | no | Numeric Breeze id of the giver. |
| include_family | boolean | no | With person_id: include gifts from the giver's family members. |
| amount_min | number | no | Only gifts of at least this amount. |
| amount_max | number | no | Only gifts of at most this amount. |
| method_ids | array | no | Only these payment method ids. |
| fund_ids | array | no | Only these fund (from breeze_list_funds) ids. |
| envelope_number | string | no | Only gifts with this envelope number. |
| batches | array | no | Only these batch number ids. |
| forms | array | no | Only these form ids. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| first | string | yes | First name. |
| last | string | yes | Last name. |
| fields | array | no | Profile fields to set (sent as fields_json). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| person_id | string | yes | Numeric Breeze id of the person. |
| fields | array | yes | Profile fields to set (sent as fields_json). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Tag name, e.g. "Small Groups". |
| folder_id | string | no | Numeric Breeze id of the folder to place the tag in (default: top level). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| person_id | string | yes | Numeric Breeze id of the person. |
| tag_id | string | yes | Numeric Breeze id of the 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| person_id | string | yes | Numeric Breeze id of the person. |
| tag_id | string | yes | Numeric Breeze id of the tag. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Event name. |
| starts_on | integer | yes | Start time, Unix timestamp in seconds. |
| ends_on | integer | no | End time, Unix timestamp in seconds (default: one hour after start). |
| all_day | boolean | no | All-day event; only the date of starts_on is used. |
| description | string | no | Event description (HTML allowed). |
| category_id | string | no | Numeric Breeze id of the calendar to place the event on (default: main). |
| event_id | string | no | Numeric Breeze id of the existing event series to add this instance to. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| person_id | string | yes | Numeric Breeze id of the person. |
| instance_id | string | yes | Numeric Breeze id of the event instance. |
| direction | string | no | in (default) or out. |
WRITE: schedule one person as a volunteer for one event instance. Breeze: GET /api/volunteers/add.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instance_id | string | yes | Numeric Breeze id of the event instance. |
| person_id | string | yes | Numeric Breeze id of the person. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Breeze Chms or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Breeze Chms can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.