Vagaro MCP Server

Book customers, read the calendar and cancel appointments across locations.

Hosted MCP Server

npx add-mcp 'https://cotlet.dev/mcp/v1/vagaro'

Installs into Claude Code, Codex, Cursor and more

Documentation

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

Vagaro API and MCP server: Let your AI agent run your Vagaro calendar.

Vagaro has an official API, but you request it and it mostly reads. It has no endpoint to create a customer, create an appointment or cancel one, and Vagaro has no MCP server (checked 26 Oct 2026). Cotlet runs 11 Vagaro tools hosted, over MCP for agents and REST for scripts.

Connect your Vagaro customer directory and salon calendar to an AI agent or an HTTP workflow. Use MCP, n8n, Make, Zapier or your own script.

MCP setup REST API guide

Free 7-day trial, no card
Unofficial, not affiliated with Vagaro
Page: https://cotlet.dev/integrations/vagaro-api-mcp-server

What can you automate in Vagaro?

Add a new customer
Find a free time for a service
Book a customer
Summarize tomorrow and its gaps
Cancel an appointment
Compare your locations

Does Vagaro have an MCP server or an API?

The API is off by default. You ask in Settings, APIs & Webhooks, it costs from $10 a month, needs Vagaro Credit Card Processing and is granted in up to seven business days. A free trial does not qualify.
Its reference lists locations, employees, services, customers by ID, appointments and availability, plus working hours and personal tasks. It lists no create customer, no create appointment and no cancel.
Webhooks push events out of Vagaro. They cannot make a booking in it. We found no Vagaro MCP server on GitHub, only Apify scrapers of public marketplace listings.

What you need	Vagaro API	Apify scrapers	Cotlet
An owner can start today	After approval, up to 7 days	Yes	Yes, your own login
Read your calendar and free times	Yes	Public listings only	Yes
Find a customer by name, phone or email	By customer ID	No	Yes
Create a customer and book them	No	No	Yes, after your OK
Cancel an appointment	No	No	Yes, after your OK
Fixed for you when Vagaro changes	Yes	By the actor author	Yes, tested every 12 h

Checked 26 Oct 2026. Sources: Vagaro API reference: introduction, Vagaro APIs & Webhooks, Vagaro Help: Set Up Webhooks From Vagaro, Vagaro Customer Participation Agreement

How does Cotlet connect to Vagaro?

Sign in to Vagaro. Use your own account in its Cotlet Cloud Browser.
Choose MCP or REST. Connect your agent or create a Cotlet API key.
Run your workflow. Ask your agent or send an HTTP request.

We never save your Vagaro password, and new customers, bookings and cancellations wait for your OK.

Connect Vagaro to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

Turn on Vagaro for agents. Create a Cotlet account, sign in to Vagaro in its Cloud Browser as the owner and press Enable for agents.
Add the Cotlet address. Put https://cotlet.dev/mcp/v1 in the MCP or connector settings of your agent.
Sign in or use a key. Chat apps ask you to sign in to Cotlet. Editors and scripts use an API key from the console.

Sign in as the business owner, or as an employee whose access level reaches your locations. Vagaro accepts logins only from US, CA, UK and AU addresses, so your Cloud Browser runs with an exit in one of them. One connection carries every app you enable, Vagaro among them. If you enabled Vagaro after connecting, refresh the connector so your agent sees the new tools.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

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

ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Cursor:

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

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

n8n:

MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: vagaro_read

Make, Zapier:

Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: vagaro_write

How to use the Vagaro REST API

Create your Cotlet API key

Create a Cotlet API key with access to Vagaro and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Sign in to your Vagaro business account in its Cotlet Cloud Browser and enable the app for agents. Your login must have access to the locations you read.

Make your first Vagaro API request

REST:

curl "https://cotlet.dev/api/v1/vagaro/customers?limit=2" \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read customers and follow the cursor

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

{
  "status": "success",
  "app": "vagaro",
  "tool": "list_customers",
  "result": {
    "customers": [
      {
        "customer_id": "Hc3kPq9xLm2VbN7tRw4yZg==",
        "name": "Megan Brooks",
        "email": "megan.brooks@example.com",
        "phone": "6145550142"
      }
    ],
    "total": 1,
    "next_cursor": null
  }
}

Read result.customers and pass result.next_cursor unchanged as cursor until null. Keep search, location_id and limit unchanged while paging.

Customer pages default to 25 records, with a maximum of 100. Upsert exports by customer_id and compare changed contact fields on later runs.

For calendar reports, list_appointments accepts at most 93 inclusive days and has no external cursor. Cancelled appointments disappear, so compare snapshots as well as IDs.

Vagaro workflows for agents and automations

Tool	Connect through	Example workflow
n8n	HTTP Request	Page through `list_customers` and upsert customer IDs and contact details into your chosen CRM sheet.
Make	HTTP > Make a request	Combine `list_locations`, `list_employees` and `list_appointments` into tomorrow's staff briefing.
Python or Node.js	REST API	Search customers, read `get_customer` and review their appointments to prepare a visit brief.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads Vagaro; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

Vagaro API endpoints and MCP tools

Locations and setup

Every other tool takes a location_id from list_locations and switches the session to it first. A location Vagaro marks as under maintenance shows locked: true.

List locations (list_locations, read): The Vagaro business locations this login reaches, and which one the session is on.
List services (list_services, read): Services of the location with category, price and duration.
List employees (list_employees, read): Employees of the location who take appointments.
Get business hours (get_business_hours, read): Opening hours of the location and each employee's working hours.

Calendar and free times

Times are the business's wall clock. A read covers at most 92 days. Cancelled appointments leave the calendar and are not listed.

Get availability (get_availability, read): Free start times for a service on one day, per employee.
List appointments (list_appointments, read): Appointments in the calendar between two dates, optionally for one customer or employee.

Customers

Vagaro allows duplicate customers, so search before you create. A customer with an email gets the business's welcome mail.

List customers (list_customers, read): Customers of the location, searchable by name, phone or email.
Get customer (get_customer, read): One customer's record: contact details, visit totals and notification settings.
Create customer (create_customer, write, asks first): Add a customer record to the location.

Book and cancel

Booking takes only a free time. Nothing is sent to the customer unless you set notify_customer.

Book appointment (book_appointment, write, asks first): Book a customer for a service with an employee at a free time.
Cancel appointment (cancel_appointment, write, asks first): Cancel one appointment in the calendar.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/vagaro-api-mcp-server#tools

Who can see my Vagaro session, and how do I revoke it?

What we store. Your signed-in Vagaro profile, encrypted with AES-256-GCM in Finland. No password.
What your agent gets. The 11 Vagaro tools. Never the cookie, the token or the login.
What the session sees. What your Vagaro login sees: customer names, emails and phones, appointments, prices.
What no tool touches. Payments, refunds, card details, your password and your billing.
If Vagaro signs you out. Your agent gets a link to sign in again. We never type your password. Vagaro asks a two-step code at sign-in and about every 30 days.
How to cut access. Disable Vagaro for agents, reset its browser or delete the key. The next call is refused.

A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). We have no SOC 2 report and no third-party pentest yet.

Is it against Vagaro's terms? Account safety

Use any data mining, robots, or similar data gathering or extraction methods designed to scrape or extract data from our Services except in accordance with instructions contained in our robot.txt file and only to compile for search results

Vagaro Customer Participation Agreement, section 3, 29 Jul 2026

The same section bans bypassing "measures employed to prevent or limit access". Our tools act in your signed-in business login, one request at a time, but these words still cover any Vagaro tool that has no partner access. We found no public case of a Vagaro account closed for automation (checked 26 Oct 2026).

What we do about it:

Your own owner or employee login, signed in by you
A Cloud Browser of its own, with its own IP in the US, CA, UK or AU
New customers, bookings and cancellations wait for your OK
Sign-in and 2FA stay with you; we never bypass MFA
Should Vagaro object, Vagaro tools pause for everyone within 24 h

Ask for the days you need, not a year of calendar every hour. Load is what a ban on extraction tools is really about.

What happens when Vagaro changes?

12 h between tests of the Vagaro tools
0/14 checks passed on Nov 6, 2026
$0 for a call to a tool paused for a fix

A request Vagaro refuses fails the call, and a failed call costs no credits. status.cotlet.dev checks the site, console and API every 3 minutes.

Approvals, undo and mistakes

Finds the customer. Searches by name, phone or email before it adds anyone.
Finds a free time. Asks for the service and day, per employee, with price and length.
Waits for your OK. Each write is a request in your Cotlet console.
Books it. Only at a free time. Nothing goes to the customer unless you said so.

Action	Undo
Create a customer	Delete the card in Vagaro; no tool deletes customers
Book an appointment	cancel_appointment
Cancel an appointment	Book the time again, if it is still free
A message to the customer	No. Only with notify_customer, or the welcome mail of a new customer with an email

3 of 11 tools ask first: book_appointment, cancel_appointment, create_customer. The other 8 only read. Turn the wait off per tool for runs at night.

cancel_appointment refuses repeating, paid and deposit appointments. Those you cancel in Vagaro.

MCP call:

{
  "name": "book_appointment",
  "arguments": {
    "customer_id": "Hc3kPq9xLm2VbN7tRw4yZg==",
    "service_id": "4PlnhTfvPOSG7q6HrPuDmQ==",
    "employee_id": "qt2FZaLftlFvrbkTi3rKmw==",
    "start_at": "2026-10-29T10:00",
    "note": "First visit"
  }
}

REST:

curl -X POST https://cotlet.dev/api/v1/vagaro/customers/Hc3kPq9xLm2VbN7tRw4yZg%3D%3D/appointments \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"service_id":"4PlnhTfvPOSG7q6HrPuDmQ==","employee_id":"qt2FZaLftlFvrbkTi3rKmw==","start_at":"2026-10-29T10:00","note":"First visit"}'

Tool output:

{
  "appointment_id": "pT0l2iDq8xYbW5nKcR3vMg==",
  "start_at": "2026-10-29T10:00",
  "duration_minutes": 45,
  "customer_id": "Hc3kPq9xLm2VbN7tRw4yZg==",
  "service_id": "4PlnhTfvPOSG7q6HrPuDmQ==",
  "service": "Women's Haircut",
  "employee_id": "qt2FZaLftlFvrbkTi3rKmw==",
  "employee": "Jessica Hall",
  "price": 40,
  "customer_notified": false
}

REST under /api/v1/vagaro takes the same tools from scripts and cron jobs, with the same key and price. The tools table lists the REST path of each tool.

How much does the Vagaro MCP server cost?

About $28 a month for a small salon with about 40 booking requests, 4,770 credits.

Job	Calls	Credits
Look at tomorrow and its gaps	3 × 26	780
Book a returning customer	4 × 25	1,000
Add a new customer and book	7 × 15	1,050
Cancel an appointment	3 × 8	240
Weekly count for two locations	5 × 4	200
Cloud Browser, 30 days		1,500
Total		4,770

Free 7-day trial, no card
10 credits per successful call, MCP or REST
50 credits a day for the Cloud Browser
Packs valid 12 months, no subscription

Vagaro publishes no figure for requests per salon, so the month is our example: a daily look at tomorrow, 40 booking requests of which 15 are new customers, 8 cancellations and a weekly count over two locations. The browser is most of the bill. Vagaro itself is billed by Vagaro per location. Dollars at the $29 pack rate.

Vagaro MCP server on GitHub, the official API or hosted: which to use

Option	What it does	Where it stops
Vagaro API	Official. Reads locations, employees, services, customers by ID, appointments and availability.	Request-only, from $10 a month, no create customer, no create or cancel appointment.
Vagaro webhooks	Vagaro posts events to a URL you run, with a response due within 20 seconds.	One way out of Vagaro. Nothing can write back.
Apify Vagaro scrapers	Lead lists and reviews from public marketplace pages.	Public data only, nothing from your own calendar or customers.
GitHub	We found no Vagaro MCP server.	Nothing to run.

Pick the official API if you only read, you have Credit Card Processing and you can wait for approval. Pick webhooks if another system just needs to hear about new bookings. Pick Cotlet if an agent should add customers, book and cancel, or if you want to search customers by name.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), and has worked since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Write to contact@cotlet.dev with questions about the Vagaro tools.

Vagaro API and MCP: questions

Can I use the Vagaro API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.

How do I get access?

Sign up free at https://cotlet.dev, open Vagaro under Integrations in the console and sign in to Vagaro in its Cloud Browser. The free trial starts when you sign up and needs no card.

How do I connect Vagaro to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Vagaro once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Vagaro account through Cotlet, in their phone apps too.

What can ChatGPT do in Vagaro?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Vagaro: book a customer who asks by message; daily schedule and gap summary; cancel a customer. You ask in plain words, and anything that reaches other people waits for your OK first.

Is there an official ChatGPT or Claude app for Vagaro?

No. Vagaro has no ChatGPT or Claude connector of its own (checked 8 Nov 2026). Cotlet is an independent one that works in ChatGPT, Claude, Cursor and any MCP client, on your signed-in account.

Can ChatGPT book an appointment in Vagaro?

Yes, with Cotlet. ChatGPT checks the free times for the service and the employee and books the customer into one. Booking waits for your OK by default, and the customer gets no message unless you ask.

Can ChatGPT show my Vagaro schedule for the day?

Yes, with Cotlet. ChatGPT lists the day's appointments for each employee and points out the gaps, in your own Vagaro login. Reading sends nothing to anyone.

Do I need Vagaro API access to use Cotlet?

No. Cotlet works in your own Vagaro login and does not use the official API. Vagaro's API needs a request form, up to seven business days, Credit Card Processing and from $10 a month, and it cannot create customers or appointments (checked 26 Oct 2026).

Who can sign in, and from where?

Sign in to Vagaro in your Cloud Browser as the business owner, or as an employee whose access level reaches the locations you want. Vagaro accepts logins only from US, CA, UK and AU addresses, so the browser runs with an exit in one of those countries. A two-step code comes by SMS or email at sign-in and about every 30 days.

How do I work with more than one location?

Call list_locations and pass a location_id to any other tool. The session switches to that location first. Locations must be linked under the same login in Multi-Location. list_locations also shows locked: true when Vagaro marks a location as under scheduled maintenance, which only Vagaro support can lift.

Which tools ask for my OK?

create_customer, book_appointment and cancel_appointment wait in the Cotlet console by default. Turn the wait off per tool for runs at night. The other eight tools only read.

Does the customer get a message?

Not unless you ask. book_appointment and cancel_appointment send nothing to the customer unless notify_customer is true. create_customer turns appointment reminders off, but a customer with an email still gets Vagaro's welcome mail when the business has "Send Welcome Email to New Customers" on, the Vagaro default.

What can it not do yet?

It does not reschedule, confirm, mark no-show or check out an appointment, and it does not take payments. It does not edit or delete customers, reply to reviews, send Connect messages, or manage the waitlist, services or employees. cancel_appointment refuses repeating, paid and deposit appointments, which you cancel in Vagaro. list_appointments does not show cancelled appointments, because the calendar drops them.

Can it book any time I ask for?

Only a free time. book_appointment takes a start_at from get_availability for that service and employee, and says which times are free when the one you asked for is not. Vagaro also checks overlaps itself.

Can I get a Vagaro API key for my own salon?

Yes, on request. Settings, APIs & Webhooks, from $10 a month, with Vagaro Credit Card Processing, in up to seven business days. It will not create customers or appointments. A Cotlet API key reaches your own Vagaro login through the same tools as MCP.

Is the MCP server different from the REST API?

Only in how you call it. Both have the same 11 tools, inputs and answers, under one API key and one price. Agents use MCP; scripts, cron jobs and HTTP steps use REST.

What happens to my data if I leave?

Reset browser deletes your Vagaro profile on our side, and closing your Cotlet account deletes the browser too. Unused credits stay valid for 12 months from purchase.

Is Cotlet affiliated with Vagaro?

No. Cotlet is independent and not affiliated with Vagaro.

Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.