Skip to content

CRM

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.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

Which Sunday services still need volunteers this week?

Working in Pushpay ChMS with Elaichi

  • List all Pushpay ChMS admin groups
  • List all Pushpay ChMS auto schedule needed volunteers
  • List all Pushpay ChMS background checks
Ask anything…
Governance / Audit log Last 24 hours
Pushpay ChMS List all Pushpay ChMS background checks Emily Carter · Claude · 9:41 AM Done
Pushpay ChMS List all Pushpay ChMS auto schedule needed volunteers Emily Carter · Claude · 9:41 AM Done
Pushpay ChMS List all Pushpay ChMS admin groups Emily Carter · Claude · 9:41 AM Done
Pushpay ChMS Pushpay ChMS auto schedules run Megan Brooks · ChatGPT · 9:38 AM Done
Pushpay ChMS Update a Pushpay ChMS background check by ID Ryan Hayes · Cursor · 9:35 AM Done

How to connect Pushpay ChMS to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Pushpay ChMS MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

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

Pushpay ChMS MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

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

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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.

Pushpay ChMS MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 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 Pushpay ChMS to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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 Pushpay ChMS through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Pushpay ChMS is logged.

  • Serving

    See which services still need volunteers

    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.

  • Safety

    Confirm background checks before anyone serves

    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.

  • Campus admin

    Pull service times across every campus

    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.

  • Communications

    Draft the weekly events announcement from the calendar

    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.

  • Care

    Find care ministries by area of town

    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.

  • Leadership

    Review who holds which campus role

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

Try asking

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

See all 405 Pushpay ChMS tools →

What connecting Pushpay ChMS gets you

6 screens from Elaichi, each doing one job for your Pushpay ChMS account.

Elaichi Agent

Ask Elaichi to work across your apps.

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.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about volunteers and get live answers.

Plain questions return current service times, volunteer gaps and background checks from Pushpay ChMS.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

Pushpay ChMS works in every client, one endpoint.

Claude, ChatGPT and Cursor reach Pushpay ChMS through one governed endpoint, no SDK, no shared key.

ElaichiTools
Tool Action Description
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).

Tool catalog

405 Pushpay ChMS tools, ready without code.

Campuses, volunteers, background checks and calendar events, covered without writing a line of code.

ElaichiToolboxes
Name Source template Tools Created

Serving toolbox

Pushpay ChMS · volunteer schedules and needs

Pushpay ChMS starter 18 Mar 4, 2026

Safety toolbox

Pushpay ChMS · background checks

— 9 Mar 2, 2026

Campus admin toolbox

Pushpay ChMS · campuses and service times

— 24 Feb 27, 2026

Communications toolbox

Pushpay ChMS · calendar events

Pushpay ChMS starter 6 Feb 19, 2026

Care toolbox

Pushpay ChMS · homebound ministries and areas of town

— 31 Jan 30, 2026

Leadership toolbox

Pushpay ChMS · admin groups and campus roles

— 12 Jan 22, 2026

Toolboxes

Every ministry team gets its own toolbox.

Serving sees volunteer schedules, Safety sees background checks, each team scoped to its work.

ElaichiConnections
Connection Scope Status Access
PU

Pushpay ChMS (Volunteer teams)

Connected by Emily Carter

Personal • Active 1 team · 6 members
PU

Pushpay ChMS (Kids ministry)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
PU

Pushpay ChMS (North campus)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
PU

Pushpay ChMS (Communications)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
PU

Pushpay ChMS (Care team)

Connected by Ryan Hayes

Personal • Active Not shared
PU

Pushpay ChMS (Central office)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share Pushpay ChMS without sharing a secret.

One admin connects, teams work through it, and nobody else ever sees a credential.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Pushpay ChMS Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Pushpay ChMS Volunteers Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Pushpay ChMS Volunteers List Toolbox

Audit log

Know who changed which background check.

Every Pushpay ChMS call logs who, when, what happened and which record it touched.

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.

Pushpay ChMS digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch volunteers

    Pushpay ChMS

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Pushpay ChMS

    Queued

Workflows

Volunteer gaps become a digest, approved and posted.

A schedule fetches unfilled services, drafts the digest, a person approves it, then it posts back.

Pushpay ChMS health

Refreshed 4 minutes ago · every 15 minutes · from the volunteers collection

Live

Volunteers

1,284 ↓ 12%

Background checks

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Volunteers created

Last 14 days

By team

Share of activity

Volunteer teams 34%

Kids ministry 27%

North campus 21%

Communications 18%

Collections and dashboards

Pushpay ChMS health, refreshed on a schedule.

Background checks, volunteer needs and calendar events computed from live records, no model involved.

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Pushpay ChMS, by what to check
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 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Pushpay ChMS tools for your AI agents

405 tools are ready to call through Elaichi's MCP endpoint the moment you connect Pushpay ChMS, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Showing 348 of 405 Pushpay ChMS tools here. Connect Pushpay ChMS and call search_tools or tools/list over the MCP endpoint for the complete set.

Questions, answered

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.

Put Pushpay ChMS 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