# Pushpay ChMS MCP connector

The Pushpay ChMS connector brings campuses, service times, volunteer schedules, background checks and calendar events into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, with each person signed in as themselves and every call logged.

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

## Facts

| | |
| --- | --- |
| Application | Pushpay ChMS |
| Category | CRM |
| AI tools | 405 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | Yes |
| 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 Pushpay ChMS is connected

- Which Sunday services still need volunteers this week?
- List background checks that are missing or out of date.
- Show service times for every campus next weekend.

## Connect Pushpay ChMS in Elaichi

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

1. Open Connections, choose Add connection, and pick Pushpay ChMS.
2. Optionally set Share with, then press Connect.
3. Supply your own Pushpay ChMS app, then approve. Pushpay ChMS needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

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

## Pushpay ChMS 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.

## Pushpay ChMS 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`.

## Pushpay ChMS 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.

## Pushpay ChMS 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.

## Pushpay ChMS 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 Pushpay ChMS 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 Pushpay ChMS 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 Pushpay ChMS through Elaichi

### See which services still need volunteers

Serving. Ask which upcoming services in Pushpay ChMS still have unfilled volunteer spots, and let the auto schedule run so the gaps get filled before the weekend.

### Confirm background checks before anyone serves

Safety. Pull the list of background checks in Pushpay ChMS, spot the ones that are missing or out of date, and update a record once a new check comes back.

### Pull service times across every campus

Campus admin. Get the service times for each Pushpay ChMS campus in one answer, and push a change to several campuses at once when a schedule shifts.

### Draft the weekly events announcement from the calendar

Communications. List the calendar events in Pushpay ChMS for the coming week and turn them into a bulletin blurb or email in the words your congregation expects.

### Find care ministries by area of town

Care. Look up the homebound ministries and areas of town set up in Pushpay ChMS so a care visit or meal train goes to the right team.

### Review who holds which campus role

Leadership. List the campus leadership roles, admin groups and membership types in Pushpay ChMS before a staff meeting, without clicking through every settings page.

## Elaichi vs Zapier MCP vs Composio for Pushpay ChMS

All three can connect Pushpay ChMS 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 Pushpay ChMS tools | Allow or restrict single Pushpay ChMS 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 Pushpay ChMS 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 Pushpay ChMS to Claude?

Connect Pushpay ChMS in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Pushpay ChMS connects over OAuth, but it needs an OAuth application registered inside Pushpay ChMS, so one person brings a client ID and secret once and nobody else has to. After that, each person simply signs in to Pushpay ChMS as themselves.

### Does Pushpay ChMS work with ChatGPT and Cursor as well as Claude?

Yes. Once Pushpay ChMS 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 Pushpay ChMS once and every client picks it up.

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

With Pushpay ChMS connected, an agent can tell you which services still need volunteers, run the auto schedule, list and update background checks, pull calendar events and service times for every campus, and look up admin groups, leadership roles, membership types and homebound ministries. Short, concrete asks such as 'which Sunday services still need volunteers' work better than long paragraphs.

### Does connecting Pushpay ChMS give the AI access to the whole church database?

No. Every call to Pushpay ChMS runs as the person who signed in, so an agent sees only the campuses, groups and records that person can already see in Pushpay ChMS. Elaichi can narrow that access further with roles and restrictions, and it can never widen it.

### Can my team share one Pushpay ChMS connection?

Yes. One admin connects Pushpay ChMS in Elaichi and shares the connection with a team, and nobody else touches the client ID or secret. Each person still signs in as themselves, so the audit log names who ran the volunteer schedule or updated a background check.

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

Yes. Restrictions in Elaichi apply per action, on a role or on one person, so you can allow reading Pushpay ChMS service times while restricting deleting a background check or bulk updating campuses. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Pushpay ChMS connection when someone leaves?

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

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

Yes. Pushpay ChMS 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 Pushpay ChMS?

Yes. Both let Claude, ChatGPT or Cursor use Pushpay ChMS. 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 Pushpay ChMS call.

### How is Elaichi different from Composio for Pushpay ChMS?

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 Pushpay ChMS: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 405 Pushpay ChMS tools

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

- **List all Pushpay ChMS admin groups** (List). Get groups (GET /groups/admin). The connector pages with page / per_page (limit = page size: 25, 50, 75 or 100) and follows x-next-page.
- **List all Pushpay ChMS auto schedule needed volunteers** (List). Gets the number of needed volunteers for auto schedule (GET /scheduling/auto_schedule/needed_volunteers). Pushpay's reference also declares a request body for this GET; a GET can't carry one, so filters go in the query fields.
- **Pushpay ChMS auto schedules run** (Run). Creates as many assignments as possible for the given scheduling events (POST /scheduling/auto_schedule).
- **Delete a Pushpay ChMS background check by ID** (Delete). Remove background check (DELETE /individuals/background_checks/{id}). Required: id.
- **List all Pushpay ChMS background checks** (List). Get all background checks uploaded the vendor associated with that access token (GET /individuals/background_checks).
- **Update a Pushpay ChMS background check by ID** (Update). Update an existing background check (PUT /individuals/background_checks/{id}). Required: id.
- **List all Pushpay ChMS calendar events** (List). Get event calendar (GET /calendar). Required: campus_id.
- **List all Pushpay ChMS campus leadership roles** (List). Get campus leadership roles (GET /campuses/{id}/leadership_roles). Required: campus_id.
- **List all Pushpay ChMS campus service times** (List). Get campus service times (GET /campuses/{id}/service_times). Required: campus_id.
- **Pushpay ChMS campuses bulk update** (Update). Update campus information (PUT /campuses). One call on the collection, not a batch of records (the connector names writes without a trailing record id bulk_*).
- **List all Pushpay ChMS campuses** (List). Get campus list (GET /campuses).
- **Pushpay ChMS checkr integrations get current** (Get). Get all Checkr integrations for all campuses in an organization (GET /integrations/checkr).
- **Pushpay ChMS church get current** (Get). Get current church information (GET /church).
- **List all Pushpay ChMS church areas of town** (List). Get schools (GET /church/areas_of_town). The connector pages with page / per_page (limit = page size: 25, 50, 75 or 100) and follows x-next-page.
- **List all Pushpay ChMS church attendance groupings** (List). Get attendance groupings (GET /church/attendance_groupings).
- **List all Pushpay ChMS church countries** (List). Get countries (GET /church/countries).
- **List all Pushpay ChMS church custom fields** (List). Get custom fields (GET /church/custom_fields).
- **List all Pushpay ChMS church envelope user options** (List). Get envelope user options (GET /church/envelope_user_options).
- **List all Pushpay ChMS church ethnicities** (List). Get ethinicity options (GET /church/ethnicities).
- **List all Pushpay ChMS church homebound ministries** (List). Get homebound ministry options (GET /church/homebound_ministries).
- **List all Pushpay ChMS church membership types** (List). Get membership types (GET /church/membership_types).
- **List all Pushpay ChMS church mobile carriers** (List). Get mobile carriers (GET /church/mobile_carriers).
- **List all Pushpay ChMS church preferred languages** (List). Get preferred language options (GET /church/preferred_languages).
- **Create a Pushpay ChMS church privacy default** (Create). Update privacy defaults (POST /church/privacy_defaults).
- **List all Pushpay ChMS church privacy defaults** (List). Get privacy defaults (GET /church/privacy_defaults).
- **List all Pushpay ChMS church reasons left** (List). Get reasons left options (GET /church/reasons_left).
- **List all Pushpay ChMS church religions** (List). Get religion options (GET /church/religions).
- **List all Pushpay ChMS church school grades** (List). Get school grades (GET /church/school_grades).
- **List all Pushpay ChMS church schools** (List). Get schools (GET /church/schools).
- **List all Pushpay ChMS church services** (List). Get services (GET /church/services).
- **List all Pushpay ChMS church social networks** (List). Get social networks (GET /church/social_networks).
- **Pushpay ChMS data imports import individuals** (Import). Upload a CSV file for import with the following columns of data as families of individuals. Expected columns - First Name, Last Name, Email, Phone, (POST /data_import/individuals). Required: file.
- **Pushpay ChMS data imports import sacraments** (Import). Upload a CSV file for importing sacraments for an individual. Expected columns - individual id, Name, sacrament data columns (POST /data_import/sacraments). Required: file.
- **List all Pushpay ChMS departments** (List). Get Departments (GET /departments). The connector pages with page / per_page (limit = page size: 25, 50, 75 or 100) and follows x-next-page.
- **List all Pushpay ChMS duplicate individuals** (List). Get potential duplicates matching the giving query parameters (GET /individuals/duplicates). Matching Scores The following table shows how parameters are compared to individual fields, and what the resulting score is when they are considered a match. The soundex comparison is run on the first 4 characters of the two values. parameter | individual field | comparison | score --------- |...
- **Get single Pushpay ChMS event attendance by ID** (Get). Get event summary details (GET /events/{id}/attendance/{occurrence}). Required: id, event_id.
- **Pushpay ChMS event attendance record** (Action). Create/update event summary details (POST /events/{id}/attendance/{occurrence}). Required: event_id, occurrence.
- **Create a Pushpay ChMS event attendance attendee** (Create). Update event attendees (POST /events/{id}/attendance/{occurrence}/attendees). Required: event_id, occurrence, items.
- **List all Pushpay ChMS event attendance attendees** (List). Get event attendees list (GET /events/{id}/attendance/{occurrence}/attendees). The connector pages with page / per_page (limit = page size: 25, 50, 75 or 100) and follows x-next-page. Required: event_id, occurrence.
- **List all Pushpay ChMS event attendance candidates** (List). Get event candidate list (GET /events/{id}/attendance/candidates). The connector pages with page / per_page (limit = page size: 25, 50, 75 or 100) and follows x-next-page. Required: event_id.
- **List all Pushpay ChMS event calendars** (List). Get the event calendar (GET /events/{id}/calendar). Required: event_id.
- **List all Pushpay ChMS event guests** (List). Get event guest list (GET /events/{id}/guests). The connector pages with page / per_page (limit = page size: 25, 50, 75 or 100) and follows x-next-page. Required: event_id.
- **Delete a Pushpay ChMS event occurrence by ID** (Delete). Delete event occurrence (DELETE /events/{id}/{occurrence}). Required: id, event_id.
- **Get single Pushpay ChMS event occurrence by ID** (Get). Get a specific occurrence of an event (GET /events/{eventId}/occurrences/{occurrence}). Required: id, eventId.
- **Pushpay ChMS event photo bulk delete** (Delete). Remove the event photo (DELETE /events/{id}/photo). One call on the collection, not a batch of records (the connector names writes without a trailing record id bulk_*). Required: event_id.
- **Create a Pushpay ChMS event photo** (Create). Update the event photo (POST /events/{id}/photo). Required: event_id, uploaded_file.
- **List all Pushpay ChMS event resources** (List). Get event resource list (GET /events/{id}/resources). The connector pages with page / per_page (limit = page size: 25, 50, 75 or 100) and follows x-next-page. Required: event_id.
- **List all Pushpay ChMS event rooms** (List). Get event room list (GET /events/{id}/rooms). The connector pages with page / per_page (limit = page size: 25, 50, 75 or 100) and follows x-next-page. Required: event_id.
- **List all Pushpay ChMS event search results** (List). Search events (GET /events/search). The connector pages with page / per_page (limit = page size: 25, 50, 75 or 100) and follows x-next-page.
- **Create a Pushpay ChMS event shared campus** (Create). Share an event with other campuses (POST /events/{id}/shared_campuses). Required: event_id.
- ...and 355 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
