Index / MCP servers / Breeze ChMS MCP by usefulapi

Breeze ChMS MCP by usefulapi MCP server

Breeze ChMS MCP by usefulapi is an MCP server with 24 tools an agent can call, among them breeze_add_event, breeze_add_person, breeze_add_tag. It answers at https://breeze-chms.usefulapi.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 29 September 2026; the last check, on 15 November 2026, succeeded.

Status
Answering
Tools
24
Official
yes, served from usefulapi.io
Reliability
4 of 4 checks
Response time
169 ms
Transport
streamable HTTP
Last checked
15 November 2026

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

Description as the publisher wrote it.

The 24 tools Breeze ChMS MCP by usefulapi offers

ToolWhat it does
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. Breeze: GET
Inputs: name, starts_on, ends_on, all_day, description, category_id
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 includ
Inputs: first, last, fields
breeze_add_tagWRITE: 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.
Inputs: name, folder_id
breeze_assign_tagWRITE: 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.
Inputs: person_id, tag_id
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. Breeze: GET /api/account/summary.
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. Breeze: GET /api/events/list_event.
Inputs: instance_id, schedule, schedule_direction, schedule_limit, eligible, details
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. Breeze: GET /api/people/{person_id}.
Inputs: person_id, details
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. Breeze: GET /api/account/list_log.
Inputs: action, start, end, user_id, details, limit
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. Breeze: GET /api/events/attendance/list.
Inputs: instance_id, details, type
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. Breeze: GET /api/events/calendars/list.
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 endpoi
Inputs: start, end, person_id, include_family, amount_min, amount_max
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 an
Inputs: start, end, category_id, eligible, details, limit
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). Breeze: GET /api/forms/list_form_entries.
Inputs: form_id, details
breeze_list_form_fieldsThe 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.
Inputs: form_id
breeze_list_formsList the church's online forms (id, name, url_slug, is_archived) — active ones by default, or archived ones. Breeze: GET /api/forms/list_forms.
Inputs: archived
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. Breeze: GET
Inputs: include_totals
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 keye
Inputs: details, filter, limit, offset
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_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>"}. Breeze: GET /api/tags/list_tags.
Inputs: folder_id
breeze_list_volunteersVolunteers scheduled for one event instance: person_id, response, comment, rsvped_on and role_ids. Breeze: GET /api/volunteers/list.
Inputs: instance_id
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). Breeze: GET /api/events/att
Inputs: person_id, instance_id, direction
breeze_schedule_volunteerWRITE: schedule one person as a volunteer for one event instance. Breeze: GET /api/volunteers/add.
Inputs: instance_id, person_id
breeze_unassign_tagWRITE: remove a tag from one person. The person and the tag both remain; re-assign with breeze_assign_tag. Breeze: GET /api/tags/unassign.
Inputs: person_id, tag_id
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_p
Inputs: person_id, fields

Add Breeze ChMS MCP by usefulapi to your AI client

Every block below points at https://breeze-chms.usefulapi.io/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http breeze-chms-mcp-by-usefulapi https://breeze-chms.usefulapi.io/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "breeze-chms-mcp-by-usefulapi": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://breeze-chms.usefulapi.io/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "breeze-chms-mcp-by-usefulapi": {
      "url": "https://breeze-chms.usefulapi.io/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "breeze-chms-mcp-by-usefulapi": {
      "type": "http",
      "url": "https://breeze-chms.usefulapi.io/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "breeze-chms-mcp-by-usefulapi": {
      "url": "https://breeze-chms.usefulapi.io/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "breeze-chms-mcp-by-usefulapi": {
      "serverUrl": "https://breeze-chms.usefulapi.io/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "breeze-chms-mcp-by-usefulapi": {
      "url": "https://breeze-chms.usefulapi.io/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Breeze ChMS MCP by usefulapi
version: 0.0.1
schema: v1
mcpServers:
  - name: Breeze ChMS MCP by usefulapi
    type: streamable-http
    url: https://breeze-chms.usefulapi.io/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "breeze-chms-mcp-by-usefulapi": {
      "httpUrl": "https://breeze-chms.usefulapi.io/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "breeze-chms-mcp-by-usefulapi": {
      "type": "http",
      "url": "https://breeze-chms.usefulapi.io/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "breeze-chms-mcp-by-usefulapi": {
      "url": "https://breeze-chms.usefulapi.io/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fbreeze-chms.usefulapi.io%2Fmcp&type=streamable_http&id=breeze-chms-mcp-by-usefulapi&name=Breeze%20ChMS%20MCP%20by%20usefulapi

Is Breeze ChMS MCP by usefulapi up right now?

It answered our last check on 15 November 2026 in 169 ms. Over 4 checks since 29 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Breeze ChMS MCP by usefulapi

Questions about Breeze ChMS MCP by usefulapi

Is there an official Breeze ChMS MCP by usefulapi MCP server?

Yes. It is published by usefulapi.io and served from breeze-chms.usefulapi.io, the vendor's own domain: https://breeze-chms.usefulapi.io/mcp.

How many tools does Breeze ChMS MCP by usefulapi have?

24, as returned by the server's own tools/list on 18 November 2026: breeze_add_event, breeze_add_person, breeze_add_tag, breeze_assign_tag, breeze_get_account_summary, breeze_get_event, breeze_get_person, breeze_list_account_log, and 16 more.

Is Breeze ChMS MCP by usefulapi down?

It answered our last check on 15 November 2026 in 169 ms. Over 4 checks since 29 September 2026 it answered 4.

How do I add Breeze ChMS MCP by usefulapi to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://breeze-chms.usefulapi.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Breeze ChMS MCP by usefulapi need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.usefulapi. Endpoint host: breeze-chms.usefulapi.io. ARD identifier: urn:air:io.usefulapi:mcp:breeze-chms. First indexed 29 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.