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

Source: https://elaichi.ai/connectors/vagaro/

## Facts

| | |
| --- | --- |
| Application | Vagaro |
| Category | Scheduling |
| AI tools | 19 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Vagaro is connected

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

## Connect Vagaro in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Vagaro.
2. Optionally set Share with, then press Connect.
3. Paste a Vagaro API key. One person generates a token in Vagaro and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Vagaro tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Vagaro MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Vagaro MCP connector for Microsoft Copilot

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

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

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

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Vagaro tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Vagaro through Elaichi

### Find the next open slot for a client

Front desk. 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.

### See who is booked across every location

Owners. Pull today's appointments for all Vagaro locations into one view before you walk in, without opening each calendar in turn.

### Change a stylist's hours before next week

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

### Assign a new hire to the right location

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

### Keep a to-do list beside the book

Providers. Add, update and clear personal tasks in Vagaro, such as reordering color supplies or calling back a regular, without leaving the chat.

### Pull up a client before they arrive

Front desk. 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.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Vagaro connection?

Yes. One person connects Vagaro with the API key in Elaichi and shares the connection with a team, so nobody else ever handles the key. Each person still signs in to Elaichi as themselves, which means every appointment lookup or employee update is logged under their own name.

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

## All 19 Vagaro tools

Every tool below is callable through https://api.elaichi.ai/mcp once Vagaro is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Vagaro access levels** (List). The Get Access Levels API is used to get the list of access levels of a business location in Vagaro. Access levels define what access a user has within that location. Needs the "read access" scope. Required: businessId.
- **Create a Vagaro access token** (Create). The Generate Access Token API is used to generate an access token using the client credentials found within your Vagaro Developer Settings. The connector calls it on connect and every 30 minutes with the saved client ID, client secret and scopes (no body needed); returns data.access_token and data.expires_in (3600).
- **List all Vagaro appointment availability** (List). The Search Availability API is used to search available appointment time slots for a service provider(s) at a Vagaro business location. bookingItems: an array of {serviceId, addOnIds, serviceProviderIds}; appointmentDate in yyyy-mm-dd. Needs the "read access" scope. Required: businessId, bookingItems.
- **List all Vagaro appointments** (List). The Retrieve Appointments API is used to retrieve a list of appointments. businessId is required, and customerId or appointmentId: all appointments of a customer, or the services of one appointment. orderBy sorts by start time (asc or desc). Needs the "read access" scope. Required: businessId. The connector pages through all results (pageNumber; limit sets pageSize, up to 100).
- **Delete a Vagaro customer by ID** (Delete). The Delete Customer API is used to delete a customer from a Vagaro business location. Needs the "write employee" scope. Required: id, businessId.
- **Get single Vagaro customer by ID** (Get). The Retrieve Customer API is used to retrieve information about a customer using the Customer ID and Business ID. Needs the "read access" scope. Required: id, businessId.
- **Create a Vagaro employee assignment** (Create). The Assign Employee API is used to assign an employee into one or multiple Vagaro business locations. Request must contain one of the following parameters: businessIds or groupName. Send businessIds (a list of location ids) or groupName (a multi-location group); accesslevelId comes from access_levels.list. Needs the "write employee" scope. Required: accesslevelId, emailId, calendar.
- **Create a Vagaro employee unassignment** (Create). The Unssign Employee API is used to deactivate an employee from one or multiple locations. Request must contain one of the following parameters: businessIds or groupName. Deactivates the employee at the locations; send businessIds or groupName. calendar true keeps the employee's calendar. Needs the "write employee" scope. Required: emailId, calendar.
- **Update a Vagaro employee working hour by ID** (Update). The Update Employee Working Hours API is used to update both the calendar working hours and regular working hours of an employee. You can use this API to set the working hour slots as well as what services the employee offers during these hours. Needs the "write employee" scope. Required: id, businessId, type, slots.
- **Delete a Vagaro employee by ID** (Delete). The Delete Employee API is used to delete an employee/service provider in a Vagaro business location. Needs the "write employee" scope. Required: id, businessId.
- **Get single Vagaro employee by ID** (Get). The Retrieve Employee API is used to retrieve information about a employee/service provider using the Service Provider ID and Business ID. Needs the "read access" scope. Required: id, businessId.
- **Update a Vagaro employee by ID** (Update). The Update Employee API is used to update information about an employee/service provider. Needs the "write employee" scope. Required: id, businessId.
- **List all Vagaro locations** (List). The Retrieve Business Locations API is used to retrieve the list of business locations. Additionally, if the businessId parameter is supplied in the request body, only details of that specific location will be returned in the response. Pass businessId to get only that location. Needs the "read access" scope. The connector pages through all results (pageNumber; limit sets pageSize, up to 100).
- **Update a Vagaro location by ID** (Update). The Update Business Location API is used to update information of a Vagaro business location. Needs the "write employee" scope. Required: id.
- **Create a Vagaro personal task** (Create). The Create Personal Task API is used to create a personal task for a service provider in a Vagaro business location. Returns data.personalTaskIds (single task) or data.recurringRuleIds (recurring series). Needs the "write employee" scope. Required: businessId, serviceProviderId, startTime, endTime.
- **Delete a Vagaro personal task by ID** (Delete). The Delete Personal Task API is used to delete a personal task for a service provider in a Vagaro business location. For a recurring series pass recurring true with the recurrence rule id as the id, appointmentDate for one occurrence, or editSeries true for the whole series. Needs the "write employee" scope. Required: id, businessId.
- **List all Vagaro personal tasks** (List). The Retrieve Personal Tasks API is used to retrieve personal tasks for a service provider in a Vagaro business location. Needs the "read access" scope. Required: businessId, serviceProviderId. The connector pages through all results (pageNumber; limit sets pageSize, up to 100).
- **Update a Vagaro personal task by ID** (Update). The Update Personal Task API is used to update a personal task for a service provider in a Vagaro business location. Needs the "write employee" scope. Required: id, businessId, serviceProviderId.
- **List all Vagaro services** (List). The Retrieve Services API is used to retrieve the list of services from a Vagaro business location. Needs the "read access" scope. Required: businessId. The connector pages through all results (pageNumber; limit sets pageSize, up to 100).
