Wodify MCP connector
The Wodify connector brings your members, leads, classes, reservations and coaches into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, with every call made as the person who signed in and recorded in an audit log.
- Connects with an API key
- Free 14-day trial
- No credit card
Reserve Maya Chen into tomorrow's 6am class
Working in Wodify with Elaichi
-
List all Wodify appointments bookings clients
-
List all Wodify appointments bookings clients search
-
List all Wodify appointments bookings leads
How to connect Wodify to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Wodify 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.
Wodify 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.
Wodify 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.
Wodify 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.
Wodify 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 Wodify 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 Wodify through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Wodify is logged.
-
Front desk
Book a member into tonight's class
A member calls to say they are coming in. Reserve their spot in the 6pm class, or cancel the reservation if they ring back, without leaving the conversation.
-
Membership sales
Follow up every lead from this week
Pull the leads that came in since Monday, see where each one sits, and update the status after a call so nobody gets contacted twice.
-
Coaches
Check who is signed in before class
Ask who has reserved and who has signed in to the 5:30am class, then sign in the regular who forgot to tap the screen.
-
Operations
Cancel a class and reinstate it later
A coach is sick, so cancel the noon class and let everyone know. When cover is found, reinstate it with the same roster.
-
Marketing
Find leads who never booked a session
Search the leads list for people who were added last month and still have no appointment booked, then draft the follow-up.
-
Head coach
Put a coach on the Saturday schedule
Add a coach to the Saturday open gym class, or remove one who is on holiday, and check the rest of the week's classes still have cover.
Try asking
- “Reserve Maya Chen into tomorrow's 6am class”
- “List leads added this week who still have no booking”
- “Who is signed in to the 5:30pm class right now?”
What connecting Wodify gets you
6 screens from Elaichi, each doing one job for your Wodify account.
Ask Elaichi to work across your apps.
Reserve Maya Chen into tomorrow's 6am class
List leads added this week who still have no booking
Who is signed in to the 5:30pm class right now?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about members and classes in plain language.
Ask who is booked into the 6am class and get an answer from live Wodify records.
Copy the endpoint
AI apps
One endpoint puts Wodify in every client.
Claude, ChatGPT and Cursor reach Wodify through one endpoint, no SDK and no shared API key.
Tool catalog
267 Wodify tools, ready without any code.
Clients, leads, classes, reservations, coaches and appointment services, cataloged and ready to use.
Toolboxes
Every team gets its own Wodify toolbox.
Front desk, coaches and membership sales each see only the Wodify tools their work needs.
Shared connections
Share a Wodify connection, never the key.
One person connects Wodify, teammates book and update through it without ever seeing the API key.
Audit log
Every Wodify change names who made it.
When, who, what happened, and which class or member, in an append-only log.
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.
Wodify digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch clients
Wodify
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
Wodify
Queued
Workflows
A schedule drafts the weekly leads digest.
New Wodify leads are fetched, grouped, drafted into a digest, approved, then posted back.
Wodify health
Refreshed 4 minutes ago · every 15 minutes · from the clients collection
Clients
1,284 ↓ 12%
Leads
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Clients created
Last 14 days
By team
Share of activity
Front desk 34%
Membership sales 27%
Coaching staff 21%
Downtown gym 18%
Collections and dashboards
Wodify numbers refresh without anyone asking.
Reservations by team, classes created over 14 days, computed from Wodify records with no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Wodify
All three can connect Wodify 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 Wodify tools | Allow or restrict single Wodify 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 Wodify 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.
Wodify tools for your AI agents
267 tools are ready to call through Elaichi's MCP endpoint the moment you connect Wodify, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 259 of 267 Wodify tools here. Connect Wodify and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
How do I connect Wodify to Claude?
Open Elaichi, choose Wodify and paste in your Wodify API key, which is the only sign-in step Wodify asks for. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and Wodify is ready in Claude.
Does Wodify work with ChatGPT and Cursor as well as Claude?
Yes. Once Wodify is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Wodify once and every client can use it.
What can an AI agent actually do with my Wodify data?
With Wodify connected, an agent can look up members and leads, add new ones and update their details, reserve or cancel a member's spot in a class, sign them in, and create, cancel or reinstate classes. It can also add or remove coaches from classes and look up the appointment services your gym offers. Short, concrete asks such as reserve Maya into the 6am class work better than long sentences.
Does connecting Wodify give the AI everything in my gym's account?
No. Every call to Wodify runs under the person who signed in to Elaichi, so an agent can only reach the members, classes and leads that person's Wodify account already allows. Elaichi can narrow that access further with restrictions, and it never widens it.
Can I stop an agent from deleting or changing things in Wodify?
Yes. Restrictions in Elaichi work per action, so you can allow looking up Wodify classes and members while restricting deleting a class or removing a coach, on a role or on 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 Wodify connection when someone leaves?
Offboarding a person in Elaichi ends their access to Wodify at once, in every client they used. A Wodify connection shared with the team keeps working for everyone else. If you want to remove Wodify entirely, disconnecting it once in Elaichi removes it from every client.
Does the Wodify MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Wodify 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 Wodify?
Yes. Both let Claude, ChatGPT or Cursor use Wodify. 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 Wodify call.
How is Elaichi different from Composio for Wodify?
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 Wodify: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Wodify 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