# Vagaro API and MCP server

> Vagaro has an official public API, but it is limited and off by default (checked 11 Oct 2026). You request access with a form, Vagaro says activation can take up to seven business days, and it is only for businesses that use Vagaro Credit Card Processing and are not on the free trial. The reference covers locations, employees, customers and appointments, and appointments can only be retrieved: no booking, rescheduling, cancelling, waitlist, Connect messages or review replies.

Booking, payments and client management software for salons, spas, barbershops and fitness studios, with an online marketplace where clients book.

## What is the Vagaro API?

Cotlet's Vagaro API exposes 15 endpoints for your own Vagaro account: list locations, list services, list appointments, search availability, find client, list waitlist, list conversations, list reviews, book appointment, reschedule appointment, cancel appointment, add to waitlist, notify waitlist, reply to client and reply to review. The list_locations endpoint returns your business locations with address, time zone and phone. Each endpoint takes simple JSON inputs like location_id, provider_id or service_id and works both as an MCP tool for agents and as a REST call for scripts.

- **Category:** [Local services & SaaS](https://cotlet.dev/integrations/category/local-services-saas)
- **Endpoints:** 15 (8 read, 7 write)
- **Updated:** 2026-10-11

Vagaro has an official public API, but it is limited and off by default (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Vagaro with 15 endpoints (8 read, 7 write): your AI agent signs in as you and does the work.

## Does Vagaro have an official API?

Vagaro has an official public API, but it is limited and off by default (checked 11 Oct 2026). You request access with a form, Vagaro says activation can take up to seven business days, and it is only for businesses that use Vagaro Credit Card Processing and are not on the free trial. The reference covers locations, employees, customers and appointments, and appointments can only be retrieved: no booking, rescheduling, cancelling, waitlist, Connect messages or review replies.

| Task | Vagaro official | Cotlet |
|---|---|---|
| List locations | Yes: Locations section, after approval | Yes |
| List appointments | Partly: Retrieve Appointments needs an appointmentId or a customerId, after approval | Yes |
| Find a client | Partly: Retrieve Customer needs a customerId, after approval | Yes |
| Book, reschedule or cancel an appointment | No | Yes |
| Manage the waitlist | No | Yes |
| Reply to clients in Connect | No | Yes |
| Reply to reviews | No | Yes |

Sources: [Vagaro API reference: introduction](https://docs.vagaro.com/public/reference/api-introduction), [Vagaro API reference: Retrieve Appointments](https://docs.vagaro.com/public/reference/retrieve-appointments), [Vagaro APIs & Webhooks](https://www.vagaro.com/pro/updates/webhooks), [Vagaro Help: Set Up Webhooks From Vagaro](https://support.vagaro.com/hc/en-us/articles/29521637950875-Set-Up-Webhooks-From-Vagaro), [Vagaro Help: Respond to Customer Reviews](https://support.vagaro.com/hc/en-us/articles/4405382006299-Respond-to-Customer-Reviews), [Vagaro Help: Set Up the Waitlist Feature](https://support.vagaro.com/hc/en-us/articles/360010609213-Set-Up-the-Waitlist-Feature), [Vagaro Help: Vera Receptionist chatbot in Connect](https://support.vagaro.com/hc/en-us/articles/31806231306779-Set-Up-A-Chatbot-for-Your-Business-with-Vera-Receptionist)

## For AI agents

```text
Vagaro has an official public API, but it is limited and off by default (checked 11 Oct 2026). You request access with a form, Vagaro says activation can take up to seven business days, and it is only for businesses that use Vagaro Credit Card Processing and are not on the free trial. The reference covers locations, employees, customers and appointments, and appointments can only be retrieved: no booking, rescheduling, cancelling, waitlist, Connect messages or review replies.
Cotlet provides a hosted MCP server and REST API for Vagaro: 15 tools (8 read, 7 write).
Access       Request access at https://cotlet.dev/app/signup?app=vagaro; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/vagaro
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_locations, list_services, list_appointments, search_availability, find_client, list_waitlist, list_conversations, list_reviews, book_appointment, reschedule_appointment, cancel_appointment, add_to_waitlist, notify_waitlist, reply_to_client, reply_to_review
Confirm      book_appointment, reschedule_appointment, cancel_appointment, add_to_waitlist, notify_waitlist, reply_to_client, reply_to_review (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/vagaro-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=vagaro (Vagaro is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Vagaro once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Vagaro server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Vagaro in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Vagaro's terms; Cotlet is not affiliated with Vagaro.
```

## What can an AI agent do in Vagaro?

Cotlet is best for salon, spa and studio owners who want their AI agent to handle bookings, the waitlist, Connect messages and review replies without running or fixing a server.

- **Daily schedule and gap summary** (runs: daily): "What does tomorrow look like at the Main Street location? Flag any gaps longer than an hour." → `list_locations`, `list_appointments`
- **Fill a cancelled slot from the waitlist** (runs: daily): "A 2pm slot with Alex just opened tomorrow. Offer it to the first person on the waitlist who wants a haircut." → `list_waitlist`, `notify_waitlist`
- **[Reschedule appointments when a stylist is out](https://cotlet.dev/integrations/vagaro-api-mcp-server/reschedule-appointments-when-staff-is-out)**: "Alex is out sick today. Move each of her appointments to another stylist who offers the same service today, or to Alex's next free slot this week if nobody can take it. Show me the plan first and list anyone you could not place." → `list_appointments`, `list_services`, `search_availability`, `reschedule_appointment`
- **[Reply to customer reviews](https://cotlet.dev/integrations/vagaro-api-mcp-server/reply-to-customer-reviews)** (runs: weekly): "Every Monday, reply to last week's unanswered Vagaro reviews at both locations: thank 4 and 5 star reviewers by name and mention the service they had, and only draft replies to anything below 4 stars for me to read first." → `list_locations`, `list_reviews`, `reply_to_review`
- **Answer client messages in Connect** (runs: daily): "Answer every unread client message in Connect that asks about prices, using our service menu." → `list_conversations`, `list_services`, `reply_to_client`

## Can Vagaro automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Vagaro connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to daily schedule and gap summary, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/vagaro/{tool}. | Schedule Trigger node. |
| Make | HTTP module: POST https://cotlet.dev/api/v1/vagaro/{tool} with an Authorization: Bearer header and a JSON body. | Scenario schedule. |
| Zapier | Webhooks by Zapier: POST https://cotlet.dev/api/v1/vagaro/{tool} with the same header and body. | Schedule by Zapier trigger. |
| Your own script | POST https://cotlet.dev/api/v1/vagaro/{tool} with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 15 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 403 until the account has an API key with access to Vagaro.

### list_locations

Your business locations with address, time zone and phone. Access: read. REST: `POST /api/v1/vagaro/list_locations`.

No parameters.

Returns every location of your Vagaro business. Use location_id from each item in the other calls. Multi-location businesses read one location per call.

Example response:

```json
{
  "locations": [
    {
      "location_id": "loc_21",
      "name": "Main Street",
      "address": "120 Main St, Portland, OR",
      "time_zone": "America/Los_Angeles",
      "phone": "+1 555 0100"
    },
    {
      "location_id": "loc_22",
      "name": "Riverside",
      "address": "8 River Rd, Portland, OR",
      "time_zone": "America/Los_Angeles",
      "phone": "+1 555 0101"
    }
  ]
}
```

### list_services

Service menu of a location with duration, price and who performs each service. Access: read. REST: `POST /api/v1/vagaro/list_services`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location_id` | string | no | Location ID from list_locations. Default: your main location. |

Returns the services of one location with duration, price and the providers who perform them. Use service_id in search_availability and book_appointment. Prices are the menu prices shown in Vagaro.

Example response:

```json
{
  "services": [
    {
      "service_id": "svc_1172",
      "name": "Balayage",
      "duration_min": 150,
      "price": {
        "amount": 185,
        "currency": "USD"
      },
      "provider_ids": [
        "emp_309"
      ]
    },
    {
      "service_id": "svc_1180",
      "name": "Women's cut",
      "duration_min": 45,
      "price": {
        "amount": 65,
        "currency": "USD"
      },
      "provider_ids": [
        "emp_309",
        "emp_311"
      ]
    }
  ]
}
```

### list_appointments

Appointments in a date range with client, service, provider and status. Access: read. REST: `POST /api/v1/vagaro/list_appointments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location_id` | string | no | Location ID from list_locations. Default: your main location. |
| `from` | date | yes | First day, inclusive. |
| `to` | date | no | Last day, inclusive. Default: same as from. |
| `provider_id` | string | no | Only this service provider. |
| `status` | string | no | Only appointments with this status, as Vagaro shows it. Default: all. |

Returns appointments of one location between two days, ordered by start time. Filter by provider to read one person's day. Each item has the client, service, provider, status and price shown on the calendar. This reads the calendar by date, which the official API cannot do.

Example response:

```json
{
  "appointments": [
    {
      "appointment_id": "apt_7730301",
      "client": "Maya Brooks",
      "service": "Women's cut",
      "provider": "Alex",
      "start": "2026-10-14T09:00:00-07:00",
      "end": "2026-10-14T09:45:00-07:00",
      "status": "Booked"
    },
    {
      "appointment_id": "apt_7730415",
      "client": "Jamie Cole",
      "service": "Balayage",
      "provider": "Alex",
      "start": "2026-10-14T11:30:00-07:00",
      "end": "2026-10-14T14:00:00-07:00",
      "status": "Booked"
    }
  ]
}
```

### search_availability

Open slots for a service, optionally with one provider, in a date range. Access: read. REST: `POST /api/v1/vagaro/search_availability`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location_id` | string | no | Location ID from list_locations. Default: your main location. |
| `service_id` | string | yes | Service ID from list_services. |
| `from` | date | yes | First day to search. |
| `to` | date | no | Last day to search. Default: from + 7 days. |
| `provider_id` | string | no | Only slots with this provider. |

Returns open start times for one service in a date range, per provider. Use a start from the result in book_appointment or reschedule_appointment so the booking lands on a free slot.

Example response:

```json
{
  "slots": [
    {
      "provider_id": "emp_309",
      "provider": "Alex",
      "start": "2026-10-15T10:00:00-07:00"
    },
    {
      "provider_id": "emp_309",
      "provider": "Alex",
      "start": "2026-10-15T14:30:00-07:00"
    }
  ]
}
```

### find_client

Search clients by name, email or phone; returns contact details, tags and last visit. Access: read. REST: `POST /api/v1/vagaro/find_client`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | yes | Name, email or phone number. |
| `limit` | integer | no | 1 to 50. Default: 10. |

Searches your customers by name, email or phone and returns contact details and tags. Use client_id in book_appointment and add_to_waitlist. The official API needs a customer ID up front; this finds the ID from what you know.

Example response:

```json
{
  "clients": [
    {
      "client_id": "cl_48213",
      "name": "Jamie Cole",
      "email": "jamie@example.com",
      "phone": "+1 555 0142",
      "tags": [
        "color"
      ]
    }
  ]
}
```

### list_waitlist

Clients on the waitlist with the service, provider and day they want. Access: read. REST: `POST /api/v1/vagaro/list_waitlist`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location_id` | string | no | Location ID from list_locations. Default: your main location. |
| `date` | date | no | Only entries for this day. |

Returns the waitlist of one location. Each entry has the client, the service and provider they asked for and the day. Use entry IDs in notify_waitlist. Which alerts Vagaro sends on its own depends on your waitlist mode under Online Appointment Rules.

Example response:

```json
{
  "entries": [
    {
      "waitlist_entry_id": "wl_2041",
      "client": "Maya Brooks",
      "service": "Women's cut",
      "provider": "Alex",
      "date": "2026-10-14"
    },
    {
      "waitlist_entry_id": "wl_2044",
      "client": "Sam Ortiz",
      "service": "Beard trim",
      "provider": "any",
      "date": "2026-10-14"
    }
  ]
}
```

### list_conversations

Client chats in Connect by Vagaro with the last message and unread status. Access: read. REST: `POST /api/v1/vagaro/list_conversations`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `unread_only` | boolean | no | Only conversations with unread client messages. |
| `limit` | integer | no | 1 to 50. Default: 20. |

Returns your Connect chats with clients, most recent first, with the last message and whether it is unread. Set unread_only to see what needs an answer. Replies to appointment notifications do not appear here.

Example response:

```json
{
  "conversations": [
    {
      "conversation_id": "cv_2290",
      "client": "Maya Brooks",
      "unread": true,
      "last_message": "How much is a cut with Alex?",
      "updated_at": "2026-10-13T16:02:00-07:00"
    }
  ]
}
```

### list_reviews

Client reviews from your listing page with rating, text and whether you replied. Access: read. REST: `POST /api/v1/vagaro/list_reviews`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location_id` | string | no | Location ID from list_locations. Default: your main location. |
| `since` | date | no | Only reviews posted on or after this date. |
| `unanswered_only` | boolean | no | Skip reviews you already replied to. |

Returns the reviews posted on your Vagaro listing page, newest first, with rating, text and whether you replied. Use unanswered_only to skip reviews you already answered. You cannot remove a customer review in Vagaro, so this tool only reads them.

Example response:

```json
{
  "reviews": [
    {
      "review_id": "rv_5521",
      "client": "Maya B.",
      "rating": 5,
      "text": "Best balayage I have had.",
      "posted_at": "2026-10-12",
      "replied": false
    }
  ]
}
```

### book_appointment

Book a client into an open slot. Access: write, asks the user first. REST: `POST /api/v1/vagaro/book_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `client_id` | string | yes | Client ID from find_client. |
| `service_id` | string | yes | Service ID from list_services. |
| `provider_id` | string | yes | Service provider ID. |
| `start` | datetime | yes | Slot start from search_availability, ISO 8601 with time zone. |
| `notes` | string | no | Appointment note visible to staff. |

Books one client for one service with one provider at a start time from search_availability. Returns the appointment, its end time and price. The booking appears on the Vagaro calendar like one made by staff. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "appointment_id": "apt_7730415",
  "status": "Booked",
  "client_id": "cl_48213",
  "service": "Balayage",
  "provider": "Alex",
  "start": "2026-10-16T14:00:00-07:00",
  "end": "2026-10-16T16:30:00-07:00",
  "price": {
    "amount": 185,
    "currency": "USD"
  }
}
```

### reschedule_appointment

Move an appointment to a new time or provider. Access: write, asks the user first. REST: `POST /api/v1/vagaro/reschedule_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `appointment_id` | string | yes | Appointment ID from list_appointments. |
| `start` | datetime | yes | New start, ISO 8601 with time zone. |
| `provider_id` | string | no | New provider. Default: unchanged. |

Moves one appointment to a new start time and optionally a new provider, the same change as dragging it on the calendar. Returns the old and new times. Pick the new start from search_availability. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "appointment_id": "apt_7730415",
  "status": "Booked",
  "previous_start": "2026-10-14T11:30:00-07:00",
  "start": "2026-10-15T10:00:00-07:00",
  "end": "2026-10-15T12:30:00-07:00",
  "provider": "Alex"
}
```

### cancel_appointment

Cancel a client's appointment from the calendar, optionally notifying the client. Access: write, asks the user first. REST: `POST /api/v1/vagaro/cancel_appointment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `appointment_id` | string | yes | Appointment ID from list_appointments. |
| `notify_client` | boolean | no | Tell the client about the cancellation. Default: true. |

Cancels one appointment, as Change Status then Cancel does on the Vagaro calendar. Set notify_client to tell the client. Refunds of prepayments and cancellation fees are not part of this tool; handle those in Vagaro. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "appointment_id": "apt_7730415",
  "status": "Cancelled",
  "client_notified": true
}
```

### add_to_waitlist

Put a client on the waitlist for a service, provider and day. Access: write, asks the user first. REST: `POST /api/v1/vagaro/add_to_waitlist`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location_id` | string | no | Location ID from list_locations. Default: your main location. |
| `client_id` | string | yes | Client ID from find_client. |
| `service_id` | string | yes | Service ID from list_services. |
| `date` | date | yes | Day the client wants. |
| `provider_id` | string | no | Preferred provider. Default: any. |

Adds a client to the waitlist of a location for one service and day, as Vagaro lets staff do by hand. The date tells Vagaro when to notify the client. Returns the entry ID for list_waitlist. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "waitlist_entry_id": "wl_2052",
  "client": "Jamie Cole",
  "service": "Women's cut",
  "date": "2026-10-17",
  "provider": "any"
}
```

### notify_waitlist

Alert chosen waitlisted clients about an opening. Access: write, asks the user first. REST: `POST /api/v1/vagaro/notify_waitlist`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `waitlist_entry_ids` | string[] | yes | Entries from list_waitlist. |
| `start` | datetime | yes | Start of the open slot. |
| `provider_id` | string | no | Provider of the open slot. |

Offers an open slot to the waitlist entries you pick, like choosing a client by hand in the You Pick mode. Returns how many clients were alerted. Clients receive the alert, so it reaches people outside your account. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "alerted": 1,
  "waitlist_entry_ids": [
    "wl_2041"
  ],
  "start": "2026-10-14T14:00:00-07:00",
  "provider": "Alex"
}
```

### reply_to_client

Send a message to a client in Connect by Vagaro, optionally with your booking link. Access: write, asks the user first. REST: `POST /api/v1/vagaro/reply_to_client`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | string | yes | Conversation ID from list_conversations. |
| `body` | string | yes | Message text. |
| `include_booking_link` | boolean | no | Attach your appointment booking link. Default: false. |

Sends a message in an existing Connect chat. Set include_booking_link to add your appointment booking link. Once a client has closed a chat, Vagaro needs a messaging plan on your side before you can keep replying. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "conversation_id": "cv_2290",
  "message_id": "msg_8814",
  "status": "sent",
  "sent_at": "2026-10-13T16:10:00-07:00"
}
```

### reply_to_review

Post a public business reply under a customer review. Access: write, asks the user first. REST: `POST /api/v1/vagaro/reply_to_review`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `review_id` | string | yes | Review ID from list_reviews. |
| `body` | string | yes | Reply text. |

Posts your reply under one review. The reply is public to other Vagaro users, the customer is notified, and the customer cannot comment again. There is no edit tool; edit or delete a reply in Vagaro on the web, tablet, Pay Desk or PayPro. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "review_id": "rv_5521",
  "status": "published",
  "replied_at": "2026-10-13T16:20:00-07:00"
}
```

## How do I connect Vagaro to Claude Code, Codex or Cursor?

Connecting Vagaro takes three steps: request access, sign in to Vagaro once, then add one MCP server or call the REST API with the same key.

### Connect Vagaro to your agent.

1. **Create an account** Sign up and add Vagaro in the console. Your API key is there too.

2. **Sign in to Vagaro once** Open the connect page from the console and sign in to Vagaro the way you always do. We keep the session, never your password, and you can revoke it anytime.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Vagaro tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
What does tomorrow look like at the Main Street location? Flag any gaps longer than an hour.
```

### Call Vagaro from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is a POST endpoint at /api/v1/vagaro/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

```
curl https://cotlet.dev/api/v1/vagaro/book_appointment \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"client_id":"cl_48213","service_id":"svc_1172","provider_id":"emp_309","start":"2026-10-16T14:00:00-07:00","notes":"Booked by agent from a Connect request"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "appointment_id": "apt_7730415",
  "status": "Booked",
  "client_id": "cl_48213",
  "service": "Balayage",
  "provider": "Alex",
  "start": "2026-10-16T14:00:00-07:00",
  "end": "2026-10-16T16:30:00-07:00",
  "price": {
    "amount": 185,
    "currency": "USD"
  }
}
```

## Why use Cotlet for Vagaro?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Vagaro yourself. We keep only the session, encrypted with AES-256.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Pick read only, or read and write.
- Anything that reaches other people waits for your OK, unless you switch it off per tool.
- Revoke access in one click.

**Kept working for you**

- We test every integration daily.
- When Vagaro changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is there a Vagaro MCP server on GitHub?

We found no open-source Vagaro MCP server on GitHub. What exists besides Cotlet is the official API, which you must request and which only reads, and webhooks that push events out to tools like Zapier or Make. Hosted scrapers read public listings, not your account.

|  | Official API | Cotlet |
|---|---|---|
| Setup | Send the access form, wait up to seven business days, then build an OAuth client and your own code | Request access, sign in to Vagaro once in your browser, add one MCP server or API key |
| Who can use it | Businesses on Vagaro Credit Card Processing, not in the free trial | Any Vagaro business login you can sign in with |
| Booking and rescheduling | Not possible: appointments are retrieve only | Book, reschedule and cancel; each one asks for your OK by default |
| Waitlist, Connect and reviews | Not in the API reference | Waitlist, Connect replies and review replies |
| When Vagaro changes | You update your code | Our team tests it daily and fixes it for you; failed calls are free |
| Your Vagaro session | API credentials you store and rotate | Encrypted in an EU vault, limited to the actions you allow, revoked in one click |
| Price | Set by Vagaro, check your account | Free 7-day trial with 5,000 credits, then credits per call |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Vagaro changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want the session to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Vagaro API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Vagaro API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

| Size | Price | Credits / month | Per credit |
|---|---|---|---|
| Solo | $29/mo | 3,000 | about $0.0097 |
| Pro | $99/mo | 12,000 | about $0.0083 |
| Agency | $299/mo | 40,000 | $0.0075 |

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Vagaro account.

- **Company details:** The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. [Terms](https://cotlet.dev/terms)
- **Your session:** You sign in to Vagaro yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Vagaro tool you allowed. When it expires, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security)
- **Revoking access:** Disconnect Vagaro in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Vagaro's terms:** You use your own Vagaro account and stay responsible for following Vagaro's terms. Cotlet is independent and not affiliated with Vagaro. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Request access and pick Vagaro. Cotlet reviews each request and emails you your API key.

**Do I need to be technical?**

No. You sign in to Vagaro once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is a hosted server safe? My Vagaro session would leave my computer.**

Cotlet keeps your Vagaro session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

**Do I need Vagaro API access to use Cotlet?**

No. Cotlet works in your own Vagaro business login and does not use the official API. Vagaro's API needs a request form, up to seven business days, Credit Card Processing and a business that is not in the free trial (checked 11 Oct 2026).

**Can my agent message clients without a messaging plan?**

Only in chats clients start. Vagaro says that once the client closes the chat, you need a messaging plan to keep replying, so reply_to_client can fail on closed chats without one.

**Can my agent post or send messages in Vagaro without asking me?**

No. Every call to book_appointment, reschedule_appointment, cancel_appointment, add_to_waitlist, notify_waitlist, reply_to_client or reply_to_review waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the Vagaro API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/vagaro/{tool} from the HTTP Request node.