Meevo MCP connector
Connect Meevo to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot, or any MCP client can search appointment openings, book and update services, check guests in, and look up gift cards, with every action logged under whoever signed in.
- App credentials
- Free 14-day trial
- No credit card
Find the next opening for a color and cut this Saturday
Working in Meevo with Elaichi
-
Get single Meevo appointment cancellation reason by ID
-
List all Meevo appointment cancellation reasons
-
Get single Meevo appointment category by ID
How to connect Meevo to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Meevo 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.
Meevo 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.
Meevo 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.
Meevo 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.
Meevo 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 Meevo 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 Meevo through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Meevo is logged.
-
Front desk
Find the next opening for a guest
Ask for the next available slot for a cut and color with a specific stylist and book the appointment service while the guest is still on the phone.
-
Front desk
Check a guest in on arrival
Mark the guest's service as checked in the moment they walk through the door, so the stylist and the schedule stay in step.
-
Guest services
Chase unconfirmed appointments before tomorrow
Pull tomorrow's appointments, record each contact attempt as you make it, and log confirmations or opt outs as guests reply.
-
Scheduling
Move a service without breaking the book
Update an appointment service when a stylist calls in sick, and bypass a conflict on purpose when the manager approves a double booking.
-
Marketing
See which services bring guests back
Review a client's past appointment services and client counts by location to find who is due for a visit and what they usually book.
-
Owners
Read cancellation reasons by location
List cancellation reasons and appointment categories across locations and ask for a plain summary of why guests are not showing up.
Try asking
- “Find the next opening for a color and cut this Saturday”
- “Check in Maria Lopez for her 2pm appointment”
- “Which gift cards does Daniel Reyes have on file?”
What connecting Meevo gets you
6 screens from Elaichi, each doing one job for your Meevo account.
Ask Elaichi to work across your apps.
Find the next opening for a color and cut this Saturday
Check in Maria Lopez for her 2pm appointment
Which gift cards does Daniel Reyes have on file?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Meevo questions, get answers from live appointments.
Type the question as you would say it and the agent reads today's book.
Copy the endpoint
AI apps
One endpoint puts Meevo in every MCP client.
Claude, ChatGPT, and Cursor share one governed endpoint, with no SDK and no shared API key.
Tool catalog
83 Meevo tools, ready without writing code.
Appointments, services, openings, confirmations, and gift cards, every one callable the day you connect.
Toolboxes
Every team gets its own Meevo toolbox.
Front desk books, marketing reads client history, and each team sees only its scope.
Shared connections
Share one Meevo connection, keep the credential private.
Teammates book and check in through the shared account and never see the app credentials.
Audit log
Every Meevo change is logged with a name.
See who moved, canceled, or checked in each appointment, and when it happened.
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.
Meevo digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch appointments
Meevo
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
Meevo
Queued
Workflows
A schedule drafts tomorrow's Meevo digest for approval.
Appointments are fetched and grouped, an agent drafts the digest, you approve, it posts to Meevo.
Meevo health
Refreshed 4 minutes ago · every 15 minutes · from the appointments collection
Appointments
1,284 ↓ 12%
Services
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Appointments created
Last 14 days
By team
Share of activity
Downtown salon 34%
Westside spa 27%
Front desk 21%
Guest services 18%
Collections and dashboards
Meevo health numbers refresh without anyone asking.
Four metrics, fourteen days of appointments created, and a split by team, computed with no model.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Meevo
All three can connect Meevo 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 Meevo tools | Allow or restrict single Meevo 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 Meevo 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.
Meevo tools for your AI agents
83 tools are ready to call through Elaichi's MCP endpoint the moment you connect Meevo, 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 Meevo to Claude?
Connect Meevo in Elaichi first: Meevo uses app credentials, so you paste the credentials Meevo gives you into the connection form, and 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 as the endpoint. Claude asks you to sign in to Elaichi as yourself, and Meevo is ready to use. The whole thing takes a few minutes, not an afternoon.
Does Meevo work with ChatGPT and Cursor as well as Claude?
Yes. Once Meevo 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 Meevo once and every client sees it, with nothing to repeat per client.
What can an AI agent actually do with my Meevo data?
It can search Meevo for appointment openings, book or update an appointment service, check a guest in, log a contact attempt or a confirmation, and look up a client's gift cards or past services. It can also read your business information, appointment categories, and cancellation reasons to answer questions in plain language. Short, specific asks such as find the next opening for a blowout on Friday work better than long paragraphs.
Does connecting Meevo give the AI access to every location and every guest?
No. Every call into Meevo runs under the person who signed in, so an agent sees only the locations, appointments, and clients that person could already see in Meevo. Elaichi can narrow that further with roles and restrictions, but it can never widen it beyond what Meevo itself allows.
Can I stop an agent from deleting or changing things in Meevo?
Yes. Restrictions in Elaichi apply per action, so you can stop deleting appointment services or bypassing conflicts in Meevo for a role or for one person while leaving search and booking 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 Meevo connection when someone leaves?
Offboarding that person in Elaichi ends their access to Meevo at once, in every client they used. A shared Meevo connection keeps working for everyone else on the team. If you want Meevo gone entirely, disconnect it once in Elaichi and it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client.
Does the Meevo MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Meevo 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 Meevo?
Yes. Both let Claude, ChatGPT or Cursor use Meevo. 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 Meevo call.
How is Elaichi different from Composio for Meevo?
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 Meevo: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Meevo 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