Breeze MCP integration for AI agents.
Connect AI agents to Breeze through 5 structured actions, including get person, list people, and list profile fields. Review authentication, inputs, workflow…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Breeze integration exposes
The Breeze Agent App exposes 5 provider-backed actions for productivity and communication work. Its current contract lets an authorized agent get one breeze person by breeze person id, list people from breeze with optional details, pagination, and filter_json criteria, and list breeze profile sections and fields used to construct breeze people filters. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Breeze account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Breeze capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_personREADGet one Breeze person by Breeze person ID.
INPUTS: subdomain / person_id / details
list_peopleREADList people from Breeze with optional details, pagination, and filter_json criteria.
INPUTS: subdomain / details / limit / offset / filter_json
list_profile_fieldsREADList Breeze profile sections and fields used to construct Breeze people filters.
INPUTS: subdomain
list_tag_foldersREADList Breeze tag folders.
INPUTS: subdomain
list_tagsREADList Breeze tags, optionally narrowed to one Breeze tag folder.
INPUTS: subdomain / folder_id
INPUT CONTRACTS
Know what the action needs before it runs.
get_person
subdomainOPTIONAL- Breeze church subdomain without the .breezechms.com suffix.
person_idREQUIRED- Breeze person identifier to read.
detailsOPTIONAL- Whether to request the full Breeze person details payload.
list_people
subdomainOPTIONAL- Breeze church subdomain without the .breezechms.com suffix.
detailsOPTIONAL- Whether to request the full Breeze person details payload.
limitOPTIONAL- Maximum number of Breeze people to return. Use 0 to request all records.
offsetOPTIONAL- Number of Breeze people to skip before returning results.
filter_jsonOPTIONAL- Breeze filter_json object keyed by official Breeze profile field or filter names.
list_profile_fields
subdomainOPTIONAL- Breeze church subdomain without the .breezechms.com suffix.
list_tag_folders
subdomainOPTIONAL- Breeze church subdomain without the .breezechms.com suffix.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Person
Get one Breeze person by Breeze person ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_personVerify with List People
List people from Breeze with optional details, pagination, and filter_json criteria. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_peopleSAFETY BOUNDARY
Operate Breeze with explicit limits
- Authorize Breeze with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Breeze data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Breeze rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Breeze task completed successfully.
CONNECTION MODEL
API key
Breeze API key sent with the Api-key header. Generate or copy it from your Breeze account's API page: https://app.breezechms.com/api.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Breeze.