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.
- Connects with an API key
- Free 14-day trial
- No credit card
Who attended Sunday's service and who was missing this week?
Working in Breeze with Elaichi
-
List all Breeze account logs
-
List all Breeze account summary
-
List all Breeze attendance
How to connect Breeze to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Breeze MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Breeze MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
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
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Breeze through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Breeze is logged.
-
Pastoral care
Know a family before you visit
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.
-
Events
Get next month's events onto the calendar
Create the events for the coming season with the right locations and calendars, and remove the ones that were cancelled.
-
Giving
Log a contribution the moment it arrives
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.
-
Front office
Turn form entries into people
Read this week's connect card and newcomer form entries, add each new person to Breeze, and clear the entries that have been handled.
-
Children's ministry
Take attendance without the clipboard
Mark who was in the room for each class and fix a mistaken entry, so check-in numbers are right by Monday morning.
-
Office
See what changed in the account
Ask for the account summary and recent activity logs to find out who added, removed or changed records this week.
Try asking
- “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.”
What connecting Breeze gets you
6 screens from Elaichi, each doing one job for your Breeze account.
Ask Elaichi to work across your apps.
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.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about people and events in plain words.
Three starter prompts, answered from live Breeze people, attendance and form entries.
Copy the endpoint
AI apps
One Breeze endpoint for Claude, ChatGPT and Cursor.
Connect Breeze once in Elaichi, then every MCP client uses it with no shared API key.
Tool catalog
42 Breeze tools, with no custom code.
People, families, events, attendance, contributions and forms, listed with their resources and methods.
Toolboxes
Each team gets its own Breeze toolbox.
Pastoral care works with people, the events team with calendars, each scoped in Elaichi.
Shared connections
Share one Breeze connection, keep the key private.
See who connected each Breeze account and which teams and members work through it.
Audit log
Every Breeze call is logged with a name.
When, who, what happened, type and resource, so you can answer who created that family.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Breeze digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch people
Breeze
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Breeze
Queued
Workflows
A schedule starts the weekly attendance digest.
Attendance is fetched, grouped by service, drafted, approved by a person, then posted to Breeze.
Breeze health
Refreshed 4 minutes ago · every 15 minutes · from the people collection
People
1,284 ↓ 12%
Families
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
People created
Last 14 days
By team
Share of activity
Pastoral care 34%
Giving 27%
Events 21%
Front office 18%
Collections and dashboards
Breeze numbers computed nightly without a model.
Four metrics, fourteen days of people created, and a breakdown by team, refreshed on schedule.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Breeze tools for your AI agents
42 tools are ready to call through Elaichi's MCP endpoint the moment you connect Breeze, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
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 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.
Put Breeze in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot