Breeze ChMS MCP by usefulapi

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

• Conexión: Se ejecuta en la nube
• Transporte: Streamable HTTP
• Categoría: Otros

Instalación

Elige la app de IA que usas y copia la configuración.

Necesitas

• Se ejecuta en la nubeNo hay nada que instalar; se conecta por internet

¿Qué app usas?

https://breeze-chms.usefulapi.io/mcp

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

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

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

https://breeze-chms.usefulapi.io/mcp

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Nombres y descripciones de las herramientas tal como los informó el servidor el 6 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.

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

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026

• ✓ Superada

  El creador coincide con el repo

  El nombre en el registro se verificó con el dominio usefulapi.io (el registro comprueba quién es dueño del dominio)

• … Aún sin revisar

  Sigue en mantenimiento

  Todavía no hemos leído este repo en GitHub

• … Aún sin revisar

  Tiene licencia

  Todavía no hemos leído este repo en GitHub

• ✓ Superada

  El endpoint responde

  Respondió en 18 ms (HTTP 200)

• – No aplica

  Inicio de sesión con OAuth

  No hace falta iniciar sesión

• ✓ Superada

  Sin instrucciones ocultas en las descripciones de herramientas

  Leímos 24 descripciones de herramientas y no encontramos instrucciones ocultas para la IA

Comparado con otros en Otrosi

• Más estrellas que el 0% de los otros 32435 servidores de esta categoría
• Publicado en el registro más recientemente que el 97% de los otros 32435 servidores de esta categoría
• Revisiones básicas iguales o mejores que el 100% de los otros 32435 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

README del creador

{