Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Breeze ChMS MCP by usefulapi

by m190version 1.35.4i★ –iRuns in the cloud
Registry nameio.usefulapi/breeze-chms

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 3 of 3 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • Can do 24 things (tools) breeze_get_account_summary, breeze_list_people, breeze_get_person, breeze_list_profile_fields …
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://breeze-chms.usefulapi.io/mcp

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://breeze-chms.usefulapi.io/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

  • 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 keyed by field_id (slower). Filter keys are

  • 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_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_perso

  • 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_ "}. 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 and may lag up to 15 minutes. Breeze: GET

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

  • 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: GET /api/funds/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

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

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

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

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • ✓ Pass

    Endpoint responds

    Responded in 18 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 24 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

  • More stars than 0% of the other 32558 servers in this category
  • Published to the registry more recently than 98% of the other 32558 servers in this category
  • Basic checks equal to or better than 100% of the other 32558 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Breeze ChMS MCP by usefulapi safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.35.4) reached the registry today.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, FactLot

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

FactLot

by 9mp96ygnbk-alt

Cited CRE facts and deterministic calculators for agents: rent, CAM, debt sizing, IRR, parcel IDs.

Computer or cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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:
{

"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)Unlimited*

\*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to support@usefulapi.io.

Pro covers this server only. Subscribe with breeze_chms_upgrade (it returns a Stripe Checkout link). Cancel any time with breeze_chms_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running breeze_chms_upgrade before then undoes the cancel. Or write to support@usefulapi.io.

License

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

Ask PopNx