PushPress MCP connector
Connect PushPress to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot, and any MCP client can look up members, classes, checkins, enrollments, and events, with every person signed in as themselves and every call logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Who checked in to the 6am class this morning?
Working in PushPress with Elaichi
-
Get single PushPress appointment checkin by ID
-
List all PushPress appointment checkins
-
Get single PushPress appointment by ID
How to connect PushPress to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
PushPress 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.
PushPress 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.
PushPress 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.
PushPress 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.
PushPress 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 PushPress 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 PushPress through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in PushPress is logged.
-
Front desk
See who checked in this morning
Ask which members checked in to the 6am class or today's open gym and get the list from PushPress without opening the roster screen.
-
Membership
Add a new member after a tour
Create the customer in PushPress and note how they found the gym while the conversation is still fresh, so attribution is recorded on day one.
-
Coaching
Check enrollments before a class starts
Pull the enrollment list for a class or appointment, see the class type, and know who to expect before walking onto the floor.
-
Marketing
Learn which campaigns bring members in
List customer attributions in PushPress to see which referral, ad, or event brought each member through the door this quarter.
-
Owners
Compare attendance across class types
Ask for checkin counts by class type or by week and spot which sessions are filling up and which are going quiet.
-
Events
Follow up with everyone who attended
List the checkins for a workshop or open house in PushPress, then send an email message to the people who showed up.
Try asking
- “Who checked in to the 6am class this morning?”
- “Which class types had the most checkins last week?”
- “Add a new customer from today's tour and note the referral.”
What connecting PushPress gets you
6 screens from Elaichi, each doing one job for your PushPress account.
Ask Elaichi to work across your apps.
Who checked in to the 6am class this morning?
Which class types had the most checkins last week?
Add a new customer from today's tour and note the referral.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about members and classes in plain words.
Get checkins, enrollments, and events straight from live PushPress records.
Copy the endpoint
AI apps
Use PushPress from Claude, ChatGPT, or Cursor.
One governed endpoint for every client, no SDK and no shared API key.
Tool catalog
44 PushPress tools, no code to write.
Customers, classes, checkins, appointments, enrollments, and events, covered from day one.
Toolboxes
Every team gets its own PushPress toolbox.
Front desk, coaching, and marketing each see the tools their work needs.
Shared connections
Share PushPress without sharing the key.
One person connects, teammates work through it, nobody else sees a credential.
Audit log
Know who looked up which member, and when.
Every PushPress call lands in an append-only log with who, what, and which record.
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.
PushPress digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch customers
PushPress
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
PushPress
Queued
Workflows
A schedule starts work, a person approves it.
Checkins are fetched, grouped, drafted into a digest, approved, then emailed through PushPress.
PushPress health
Refreshed 4 minutes ago · every 15 minutes · from the customers collection
Customers
1,284 ↓ 12%
Classes
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Customers created
Last 14 days
By team
Share of activity
Front desk 34%
Membership 27%
Coaching 21%
Marketing 18%
Collections and dashboards
PushPress health, computed on a schedule, no model.
Four metrics, 14 days of customers created, and a split by team, refreshed automatically.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for PushPress
All three can connect PushPress 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 PushPress tools | Allow or restrict single PushPress 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 PushPress 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.
PushPress tools for your AI agents
44 tools are ready to call through Elaichi's MCP endpoint the moment you connect PushPress, 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 PushPress to Claude?
Two steps. In Elaichi, add PushPress and paste in your PushPress API key when asked, there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in to Elaichi from Claude and PushPress is ready.
Does PushPress work with ChatGPT and Cursor as well as Claude?
Yes. Once PushPress 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 PushPress once and every client you use picks it up.
What can an AI agent actually do with my PushPress data?
It can look up members, classes, class types, appointments, events, enrollments, and checkins in PushPress, and count checkins for you. It can also add a new customer, record where that customer came from, and send an email message. Short, concrete asks such as "who checked in to the noon class today" work better than long paragraphs.
Does connecting PushPress give the AI access to every member and class?
The AI only sees what the person who signed in can already see in PushPress, because every call runs inside that person's own access. Elaichi can narrow that further with roles and restrictions, but it can never widen it. Nobody gets more of PushPress through Elaichi than they would at the front desk.
Can I stop an agent from adding customers or sending emails in PushPress?
Yes. Restrictions in Elaichi work per action, so you can turn off creating customers or sending email messages in PushPress for a role or for one person while leaving lookups open. 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 PushPress connection when someone leaves?
Offboarding that person in Elaichi ends their access to PushPress at once, across every client they used. A shared PushPress connection keeps working for everyone else on the team. If you ever want PushPress gone entirely, disconnecting it once in Elaichi removes it from every client at the same time.
Does the PushPress MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. PushPress 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 PushPress?
Yes. Both let Claude, ChatGPT or Cursor use PushPress. 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 PushPress call.
How is Elaichi different from Composio for PushPress?
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 PushPress: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put PushPress 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