Vagaro MCP connector
The Vagaro connector brings appointments, availability, customers, employees, locations, services and personal tasks into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, with every request running under the signed-in person's own Vagaro access.
- Connects with an API key
- Free 14-day trial
- No credit card
Show Thursday's open slots for a 60 minute massage at Downtown.
Working in Vagaro with Elaichi
-
List all Vagaro access levels
-
List all Vagaro appointment availability
-
List all Vagaro appointments
How to connect Vagaro to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Vagaro 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.
Vagaro 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.
Vagaro 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.
Vagaro 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.
Vagaro 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 Vagaro 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 Vagaro through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Vagaro is logged.
-
Front desk
Find the next open slot for a client
Ask for Thursday openings for a 60 minute massage and get the available times straight from the Vagaro book, then confirm with the client on the phone.
-
Owners
See who is booked across every location
Pull today's appointments for all Vagaro locations into one view before you walk in, without opening each calendar in turn.
-
Managers
Change a stylist's hours before next week
Update an employee's working hours in Vagaro when someone swaps a shift, so the online booking page stops offering times they can no longer cover.
-
Operations
Assign a new hire to the right location
Add a new provider to the Uptown location in Vagaro, or unassign someone who moved, and check their access level while you are at it.
-
Providers
Keep a to-do list beside the book
Add, update and clear personal tasks in Vagaro, such as reordering color supplies or calling back a regular, without leaving the chat.
-
Front desk
Pull up a client before they arrive
Look up a customer's Vagaro record ahead of their appointment and check the service menu so you can answer questions about what they booked.
Try asking
- “Show Thursday's open slots for a 60 minute massage at Downtown.”
- “Who is booked with Maria tomorrow afternoon?”
- “Add a personal task to reorder color supplies before Friday.”
What connecting Vagaro gets you
6 screens from Elaichi, each doing one job for your Vagaro account.
Ask Elaichi to work across your apps.
Show Thursday's open slots for a 60 minute massage at Downtown.
Who is booked with Maria tomorrow afternoon?
Add a personal task to reorder color supplies before Friday.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about today's appointments in plain language.
Open availability, customer records and employee hours answered from live Vagaro, not a stale export.
Copy the endpoint
AI apps
Vagaro works in every client you already use.
Claude, ChatGPT and Cursor share one governed endpoint, with no SDK and no shared API key.
Tool catalog
19 Vagaro tools and no code to write.
Appointments, availability, customers, employees, locations, services and personal tasks, ready the moment you connect.
Toolboxes
Each team gets its own Vagaro toolbox.
Front desk books, managers set hours, owners review locations, each from a toolbox scoped to them.
Shared connections
Share one Vagaro connection, never the key.
See who connected each Vagaro account and which teams and members work through it.
Audit log
Every Vagaro change is logged with a name.
When, who, what happened, type and resource, so you can answer who updated an employee's hours.
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.
Vagaro digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch appointments
Vagaro
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
Vagaro
Queued
Workflows
A schedule starts real Vagaro work on time.
Appointments are fetched, grouped and drafted into a digest, a person approves, and it posts back.
Vagaro health
Refreshed 4 minutes ago · every 15 minutes · from the appointments collection
Appointments
1,284 ↓ 12%
Customers
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Appointments created
Last 14 days
By team
Share of activity
Downtown salon 34%
Uptown spa 27%
Front desk 21%
Management 18%
Collections and dashboards
Vagaro numbers refresh without anyone asking.
Four metrics, 14 days of appointments created and a team breakdown, computed with no model.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Vagaro
All three can connect Vagaro 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 Vagaro tools | Allow or restrict single Vagaro 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 Vagaro 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.
Vagaro tools for your AI agents
19 tools are ready to call through Elaichi's MCP endpoint the moment you connect Vagaro, 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 Vagaro to Claude?
Connect Vagaro in Elaichi by pasting the API key from your Vagaro account; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks, and Vagaro appointments, customers and services are available in the chat.
Does Vagaro work with ChatGPT and Cursor as well as Claude?
Yes. Once Vagaro 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 Vagaro once and every client you use picks it up.
What can an AI agent actually do with my Vagaro data?
An agent can look up the day's Vagaro appointments across your locations, check open availability for a service, pull up a customer's record, review an employee's details and working hours, and keep personal tasks up to date. It can also assign or unassign employees, update location details and list your service menu. Short, concrete asks such as "show Thursday's openings for a facial" work better than long paragraphs.
Does connecting Vagaro give the AI access to every location and employee?
No. Every call to Vagaro runs as the person who signed in, so an agent sees only the appointments, customers, employees and locations that person can already see in Vagaro. Elaichi can narrow that access further with roles and restrictions, but it can never widen it.
Can I stop an agent from deleting or changing things in Vagaro?
Yes. In Elaichi you can restrict any single Vagaro action, such as deleting a customer or deleting an employee, for a role or for one person. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Vagaro connection when someone leaves?
Offboarding someone in Elaichi ends their access to Vagaro through every client at once. A Vagaro connection shared with the team keeps working for everyone else. If you want it gone entirely, disconnect Vagaro once in Elaichi and it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent.
Does the Vagaro MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Vagaro 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 Vagaro?
Yes. Both let Claude, ChatGPT or Cursor use Vagaro. 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 Vagaro call.
How is Elaichi different from Composio for Vagaro?
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 Vagaro: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Vagaro 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