# Breeze MCP connector

The Breeze connector brings people, families, events, attendance, contributions and forms into Claude, ChatGPT, Cursor and Microsoft Copilot, so church staff can ask questions and record visits, giving and new members in plain language.

Source: https://elaichi.ai/connectors/breezechms/

## Facts

| | |
| --- | --- |
| Application | Breeze |
| Category | CRM |
| AI tools | 42 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Breeze is connected

- Who attended Sunday's service and who was missing this week?
- Add the Martinez family and their three kids to Breeze.
- Show me this week's new form entries and who submitted them.

## Connect Breeze in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Breeze.
2. Optionally set Share with, then press Connect.
3. Paste a Breeze API key. One person generates a token in Breeze and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Breeze tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Breeze MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Breeze MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Breeze MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Breeze MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Breeze MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Breeze to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Breeze tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Breeze through Elaichi

### Know a family before you visit

Pastoral care. Pull up a person, their household and recent attendance before a hospital call or a home visit. Add a new family and its members as soon as you meet them.

### Get next month's events onto the calendar

Events. Create the events for the coming season with the right locations and calendars, and remove the ones that were cancelled.

### Log a contribution the moment it arrives

Giving. Record a cheque or a cash gift against the right person without opening Breeze, and check who is eligible before a year-end statement goes out.

### Turn form entries into people

Front office. Read this week's connect card and newcomer form entries, add each new person to Breeze, and clear the entries that have been handled.

### Take attendance without the clipboard

Children's ministry. Mark who was in the room for each class and fix a mistaken entry, so check-in numbers are right by Monday morning.

### See what changed in the account

Office. Ask for the account summary and recent activity logs to find out who added, removed or changed records this week.

## Elaichi vs Zapier MCP vs Composio for Breeze

All three can connect Breeze to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Breeze tools | Allow or restrict single Breeze tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Breeze call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Breeze to Claude?

Connect Breeze in Elaichi by pasting the API key from your Breeze account settings. There is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Breeze is ready.

### Does Breeze work with ChatGPT and Cursor as well as Claude?

Yes. Once Breeze is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Breeze once and every client picks it up.

### What can an AI agent actually do with my Breeze data?

An agent can look up people and families, list events, calendars and locations, read form entries and account logs, and show the account summary. It can also add a person, a family or a family member, create an event, mark attendance and record a contribution. Short, concrete asks work best, such as who attended on Sunday or add the Reyes family to Breeze.

### Does connecting Breeze give the AI everything in my church database?

No. An agent only reaches what the Breeze account behind the connection can reach, and each person signs in to Elaichi as themselves, so every request is tied to a named person. Elaichi can narrow that access further by role or by person. It never widens what Breeze itself allows.

### Can my team share one Breeze connection?

Yes. One person connects Breeze in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in as themselves, so the audit log names the person who added the family or recorded the gift, not a shared account.

### Can I stop an agent from deleting or changing things in Breeze?

Yes. Restrictions in Elaichi apply per action, so you can allow reading people and events while restricting deleting a person, a family or an event, for a role or for one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Breeze connection when someone leaves?

Offboarding that person in Elaichi ends their access to Breeze at once. A shared Breeze connection keeps working for everyone else on the team. If you want Breeze gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

### Does the Breeze MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Breeze is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Breeze?

Yes. Both let Claude, ChatGPT or Cursor use Breeze. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Breeze call.

### How is Elaichi different from Composio for Breeze?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Breeze: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 42 Breeze tools

Every tool below is callable through https://api.elaichi.ai/mcp once Breeze is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Breeze account logs** (List). Breeze: List Account Log. Required: action. limit caps the number returned (the connector passes it on); Breeze doesn't page this list.
- **List all Breeze account summary** (List). Breeze: Account Summary.
- **Create a Breeze attendance** (Create). Breeze: Add Attendance Record. Required: person_id, instance_id. Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it).
- **Delete a Breeze attendance by ID** (Delete). Breeze: Remove Attendance Record. Required: person_id, instance_id. Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it). There is no single record id: pass the named fields (an id given to the connector isn't used).
- **List all Breeze attendance** (List). Breeze: List Attendance. List attendance from a given event. Required: instance_id.
- **List all Breeze calendars** (List). Breeze: List Calendars.
- **Create a Breeze contribution** (Create). Breeze: Add a contribution, as a third-party payment processor stores a processed payment (the reference's Payment Integration example). Contributions with the same group go into one batch; person_json and uid help Breeze match the giver to a profile. Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it).
- **List all Breeze eligible people** (List). Breeze: List Eligible People. Required: instance_id.
- **List all Breeze event locations** (List). Breeze: List Locations.
- **List all Breeze events** (List). Breeze: List Events. limit caps the number returned (the connector passes it on); Breeze doesn't page this list.
- **Get single Breeze event by ID** (Get). Breeze: List Event. Required: id (the event instance's id).
- **Create a Breeze event** (Create). Breeze: Add Event. Add a new event. Required: name, starts_on. Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it).
- **Delete a Breeze event by ID** (Delete). Breeze: Delete Event. Delete an Event. Required: id (the event instance's id). Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it).
- **Create a Breeze family** (Create). Breeze: Create Family. Creates a new family from a set of people. Required: people_ids_json. Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it).
- **Delete a Breeze family by ID** (Delete). Breeze: Destroy Family. Removes the family association of the given person's whole family (no people are deleted). Required: people_ids_json. Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it). There is no single record id: pass the named fields (an id given to the connector isn't used).
- **Create a Breeze family member** (Create). Breeze: Add Person to Existing Family. Adds the people to the family of target_person_id. Required: people_ids_json, target_person_id. Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it).
- **Delete a Breeze family member by ID** (Delete). Breeze: Remove Person from Existing Family. Removes the people from the family they are in. Required: people_ids_json. Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it). There is no single record id: pass the named fields (an id given to the connector isn't used).
- **List all Breeze form entries** (List). Breeze: List Form Entries. Lists the entries submitted to a form. Required: form_id.
- **Delete a Breeze form entry by ID** (Delete). Breeze: Remove Form Entry. Remove an entry from a form. Required: id (the form entry's id). Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it).
- **List all Breeze form fields** (List). Breeze: List Form Fields. List the fields for a given form. Required: form_id.
- **List all Breeze forms** (List). Breeze: List Forms. Returns a list of forms.
- **List all Breeze people** (List). Breeze: List People. List people from your database. Filter with filter_json (profile field ids and values, e.g. {"tag_contains": "y_16681"} for people with a tag: Tags &gt; List People in the reference). With a limit the connector pages through all results (limit + offset); without one Breeze returns everyone in one response.
- **Get single Breeze person by ID** (Get). Breeze: Show Person. Retrieve the details for a specific person by their ID. Required: id (the person's id).
- **Create a Breeze person** (Create). Breeze: Add Person. Add a new person. Required: first, last. Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it). fields_json: a JSON array of {field_id, field_type, response, details} entries; field ids from profile_fields.list.
- **Update a Breeze person by ID** (Update). Breeze: Update Person. Update a person. Required: id (the person's id). Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it). fields_json: a JSON array of {field_id, field_type, response, details} entries; field ids from profile_fields.list.
- **Delete a Breeze person by ID** (Delete). Breeze: Delete Person. Delete a person. Required: id (the person's id). Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it).
- **List all Breeze profile fields** (List). Breeze: List Profile Fields.
- **Create a Breeze tag assignment** (Create). Breeze: Assign Tag. Assign a tag to a person. Required: person_id, tag_id. Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it).
- **Delete a Breeze tag assignment by ID** (Delete). Breeze: Unassign Tag. Removes a tag from a person. Required: person_id, tag_id. Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it). There is no single record id: pass the named fields (an id given to the connector isn't used).
- **List all Breeze tag folders** (List). Breeze: List Folders.
- **Create a Breeze tag folder** (Create). Breeze: Add Folder. Add a new tag folder. Required: name. Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it).
- **Delete a Breeze tag folder by ID** (Delete). Breeze: Delete Folder. Required: id (the tag folder's id). Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it).
- **List all Breeze tags** (List). Breeze: List Tags. Lists the tags, optionally only those in one folder (folder_id).
- **Create a Breeze tag** (Create). Breeze: Add Tag. Add a new tag. Required: name. Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it).
- **Delete a Breeze tag by ID** (Delete). Breeze: Delete Tag. Required: id (the tag's id). Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it).
- **List all Breeze volunteer roles** (List). Breeze: List Volunteer Roles. List the volunteer roles for a specific event. Required: instance_id.
- **Create a Breeze volunteer role** (Create). Breeze: Add Volunteer Role. Add a role to an event. Required: instance_id, name. Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it).
- **Delete a Breeze volunteer role by ID** (Delete). Breeze: Remove Volunteer Role. Remove a role from an event. Required: instance_id, role_id. Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it). There is no single record id: pass the named fields (an id given to the connector isn't used).
- **List all Breeze volunteers** (List). Breeze: List Volunteers. List volunteers from a specific event. Required: instance_id.
- **Create a Breeze volunteer** (Create). Breeze: Add Volunteer. Schedule a volunteer for a specific event. Required: instance_id, person_id. Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it).
- **Delete a Breeze volunteer by ID** (Delete). Breeze: Remove Volunteer. Unschedule a volunteer from a specific event. Required: instance_id, person_id. Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it). There is no single record id: pass the named fields (an id given to the connector isn't used).
- **Update a Breeze volunteer by ID** (Update). Breeze: Update Volunteer. Update the volunteer role(s) for a person in a given event. Required: instance_id, person_id, role_ids_json. Breeze takes the arguments in the query string (a GET, as Breeze's own wrapper sends it). There is no single record id: pass the named fields (an id given to the connector isn't used).
