---
title: "Acuity Scheduling MCP server for AI agents - actionlake"
description: "Give Claude 33 Acuity Scheduling actions through one MCP server: appointments, availability. Your agent never holds the credential. 100,000 calls a month free."
canonical: https://actionlake.com/connectors/acuity-scheduling
updated: 2026-10-23
---

Connectors · Work & projects

# Acuity Scheduling MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Acuity Scheduling and the rest of your systems. It gives your agent 33 Acuity Scheduling actions (22 reads, 7 writes and 4 that wait for a confirmation) and holds the Acuity Scheduling credential itself, so the agent never does. It paces Acuity Scheduling's limits and records every call.

[Connect Acuity Scheduling free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

`claude mcp add --transport http actionlake https://connect.actionlake.com/mcp`

the first call

```
do {
  action: "acuity_scheduling.appointments.list",
  intent: "check which Acuity Scheduling account is connected"
}
# List appointments · read · 1 upstream call
```

- 33 actions in one signed file
- 22 read look, never change
- 7 write create and update
- 4 wait for a yes destructive, confirmed first

Set up

## Connect Acuity Scheduling in three steps.

1. 01
   ### Add actionlake to Claude.
   Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
   `https://connect.actionlake.com/mcp`
2. 02
   ### Connect Acuity Scheduling.
   Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.
   - `user_id` Acuity numeric User ID (Integrations > API > View credentials)
   - `api_key` Acuity API key (Integrations > API > View credentials)
   ```
   account { op: "connections.requirements", service: "acuity_scheduling" }
   # free: exactly what to paste, and what is found for you
   ```
3. 03
   ### Make the first call. Check before a write.
   Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free.
   ```
   do    { action: "acuity_scheduling.appointments.list" }
   # list appointments · read · 1 upstream call
   check { action: "acuity_scheduling.appointments.create", input: { … } }
   # free: inputs, permissions, cost and confirmations, nothing sent
   ```

Acuity Scheduling at a glance

**Sign-in**

Username and secret. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.

**You provide**

`user_id` `api_key`

**Limits we pace to**

10 calls a second, per connection

**API covered**

Acuity Scheduling API v1 (reference v1.1)`acuityscheduling.com/api/v1`

**Built from**

Acuity Scheduling's documentation, read 23 October 2026[developers.acuityscheduling.com](https://developers.acuityscheduling.com/reference)

**Service file**

Version 1.0.0, signed (Ed25519)

**Cached reads**

21 of 22 reads, for up to 10 minutes; a write clears what it affects

**Shared entities**

6, so ask can line Acuity Scheduling up with your other systems

**Data**

Processed and stored in Sydney, Australia. No US region yet

Capabilities

## What an AI agent can do in Acuity Scheduling.

33 actions in 15 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

- **22** read look, never change
- **7** write create and update
- **4** destructive wait for a confirmation

1. ### Appointments
   6
   2 read · 3 write · 1 destructive
   List appointments · Book an appointment · Get an appointment · Update an appointment
2. ### Availability
   4
   4 read · 0 write · 0 destructive
   Validate an appointment time · Get available classes · Get available dates · Get available times
3. ### Blocks
   4
   2 read · 1 write · 1 destructive
   Block off time · List blocked-off time · Get a block · Delete a block
4. ### Certificates
   4
   2 read · 1 write · 1 destructive
   Check a certificate code · Create a certificate · List package and coupon certificates · Delete a certificate
5. ### Clients
   4
   1 read · 2 write · 1 destructive
   List clients · Create a client · Update a client · Delete a client
6. ### Orders
   2
   2 read · 0 write · 0 destructive
   List store orders · Get a store order
7. ### Appointment addons
   1
   1 read · 0 write · 0 destructive
   List appointment add-ons
8. ### Appointment payments
   1
   1 read · 0 write · 0 destructive
   List an appointment's payments

**7 more areas · 7 actions**

- Appointment types **1**
- Calendars **1**
- Forms **1**
- Labels **1**
- Me **1**
- Meta **1**
- Products **1**

Top actions

## The Acuity Scheduling API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 14 of Acuity Scheduling's 14 action names are shared with at least one other connector, so an agent learns them once.

| Action | What it does | Effect | Same name in |
| --- | --- | --- | --- |
| `acuity_scheduling.appointments.list` List appointments | List appointments. | read | `comm.event.list` 61 connectors |
| `acuity_scheduling.clients.list` List clients | List clients. | read | `crm.contact.list` 177 connectors |
| `acuity_scheduling.calendars.list` List calendars | List calendars. | read | `comm.calendar.list` 14 connectors |
| `acuity_scheduling.appointments.create` Book an appointment | Book an appointment. | write | `comm.event.create` 52 connectors |
| `acuity_scheduling.me.get` Get the account | Get the account. | read | `identity.current_user.get` 307 connectors |
| `acuity_scheduling.products.list` List products and packages | List products and packages. | read | `commerce.product.list` 112 connectors |
| `acuity_scheduling.clients.create` Create a client | Create a client. | write | `crm.contact.create` 161 connectors |
| `acuity_scheduling.orders.list` List store orders | List store orders. | read | `commerce.order.list` 82 connectors |
| `acuity_scheduling.appointments.update` Update an appointment | Update an appointment. | write | `comm.event.update` 53 connectors |
| `acuity_scheduling.clients.delete` Delete a client | Delete a client. | destructive | `crm.contact.delete` 147 connectors |
| `acuity_scheduling.orders.get` Get a store order | Get a store order. | read | `commerce.order.get` 87 connectors |
| `acuity_scheduling.forms.list` List intake forms | List intake forms. | read | this connector |

Try it

## Prompts to paste into Claude.

Each one names the Acuity Scheduling actions it will call, so you know what it reads and what it changes before you send it.

1. Read read
   Which Acuity Scheduling orders from the last seven days are still unfulfilled?
   calls `acuity_scheduling.orders.list`
2. Write write
   Book an appointment in Acuity Scheduling. Show me exactly what you will send before you save it.
   calls `acuity_scheduling.appointments.create`
3. Across systems read
   Which contacts are in both Acuity Scheduling and HaloPSA, and how many are in only one of them?
   calls `acuity_scheduling.clients.list` `halopsa.users.list`

Across your systems

## Acuity Scheduling, joined to the rest of your business.

One `ask` fetches from Acuity Scheduling and another system, joins the rows on the same customer on our side, and hands your agent the answer, not every row.

- Which contacts are in both Acuity Scheduling and HaloPSA, and how many are in only one of them?
  `acuity_scheduling.clients.list` + `halopsa.users.list`, on `crm.contact` · [HaloPSA](https://actionlake.com/connectors/halopsa)
- Which contacts are in both Acuity Scheduling and NetSuite, and how many are in only one of them?
  `acuity_scheduling.clients.list` + `netsuite.views.contacts`, on `crm.contact` · [NetSuite](https://actionlake.com/connectors/netsuite)

Also mapped by other connectors `crm.contact` **192** `identity.current_user` **142** `commerce.product` **109** `commerce.order` **86** `comm.event` **47** `comm.calendar` **8**

ask

```
ask {
  intent: "which contacts are in both Acuity Scheduling and HaloPSA, and how many are in only one of them",
  steps: [
    { action: "acuity_scheduling.clients.list", as: "people", input: {}, limit: 100, max_pages: 5 },
    { action: "halopsa.users.list", as: "people2", input: {}, limit: 100, max_pages: 5 },
    { join: {
        left: "people",
        right: "people2",
        on: "crm.contact",
        group_by: "people.email",
        select: ["people.email", "count(people2.id) as in_halopsa"]
    } }
  ]
}
```

Example. Run it through check first: it validates the steps and prices them, and it is free.

Governance for Acuity Scheduling

## Destructive actions wait for a yes.

4 Acuity Scheduling actions are destructive. These are all of them:

- Delete a client `acuity_scheduling.clients.delete`
- Cancel an appointment `acuity_scheduling.appointments.cancel`
- Delete a block `acuity_scheduling.blocks.delete`
- Delete a certificate `acuity_scheduling.certificates.delete`

A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

do acuity_scheduling.clients.delete confirm_policy: **human**

Delete a client?

**intent:** the user asked me to delete a client

run suspended · waiting for a named person · key _acuity-scheduling-agent_ cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

```
account {
  op: "keys.create", name: "acuity-scheduling-agent",
  allowed_actions: ["acuity_scheduling.*"], cap_calls: 2000,
  confirm_policy: "human_for_writes",
  approval_rules: [
    { match: "acuity_scheduling.clients.delete", approver: "lead@example.com" },
    { match: "acuity_scheduling.appointments.cancel", approver: "lead@example.com" },
    { match: "acuity_scheduling.blocks.delete", approver: "lead@example.com" }
  ]
}
```

Illustrative. Scoped to Acuity Scheduling only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

## What Acuity Scheduling costs on actionlake.

Every Acuity Scheduling action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Acuity Scheduling refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

- 1 upstream call per action all 33 Acuity Scheduling actions
- 33 actions page each page of a long list is one call
- 21 reads can be cached a cache hit costs nothing
- 100,000 calls a month, free paid plans from US$49 a month for 250,000

[See pricing](https://actionlake.com/pricing)

Action index

## Every Acuity Scheduling action.

33 actions by area: the id your agent calls, what it does, and its effect.

**Appointments 6**

- `acuity_scheduling.appointments.cancel` Cancel an appointment destructive
- `acuity_scheduling.appointments.create` Book an appointment write
- `acuity_scheduling.appointments.get` Get an appointment read
- `acuity_scheduling.appointments.list` List appointments read
- `acuity_scheduling.appointments.reschedule` Reschedule an appointment write
- `acuity_scheduling.appointments.update` Update an appointment write

**Availability 4**

- `acuity_scheduling.availability.check_times` Validate an appointment time read
- `acuity_scheduling.availability.classes` Get available classes read
- `acuity_scheduling.availability.dates` Get available dates read
- `acuity_scheduling.availability.times` Get available times read

**Blocks 4**

- `acuity_scheduling.blocks.create` Block off time write
- `acuity_scheduling.blocks.delete` Delete a block destructive
- `acuity_scheduling.blocks.get` Get a block read
- `acuity_scheduling.blocks.list` List blocked-off time read

**Certificates 4**

- `acuity_scheduling.certificates.check` Check a certificate code read
- `acuity_scheduling.certificates.create` Create a certificate write
- `acuity_scheduling.certificates.delete` Delete a certificate destructive
- `acuity_scheduling.certificates.list` List package and coupon certificates read

**Clients 4**

- `acuity_scheduling.clients.create` Create a client write
- `acuity_scheduling.clients.delete` Delete a client destructive
- `acuity_scheduling.clients.list` List clients read
- `acuity_scheduling.clients.update` Update a client write

**Orders 2**

- `acuity_scheduling.orders.get` Get a store order read
- `acuity_scheduling.orders.list` List store orders read

**Appointment addons 1**

- `acuity_scheduling.appointment_addons.list` List appointment add-ons read

**Appointment payments 1**

- `acuity_scheduling.appointment_payments.list` List an appointment's payments read

**Appointment types 1**

- `acuity_scheduling.appointment_types.list` List appointment types read

**Calendars 1**

- `acuity_scheduling.calendars.list` List calendars read

**Forms 1**

- `acuity_scheduling.forms.list` List intake forms read

**Labels 1**

- `acuity_scheduling.labels.list` List appointment labels read

**Me 1**

- `acuity_scheduling.me.get` Get the account read

**Meta 1**

- `acuity_scheduling.meta.get` Get API metadata read

**Products 1**

- `acuity_scheduling.products.list` List products and packages read

Questions

## The Acuity Scheduling MCP server, answered.

**Is there an Acuity Scheduling MCP server for Claude?**

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 33 Acuity Scheduling actions across appointments, availability, blocks and certificates, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Acuity Scheduling.

**What do I need to connect Acuity Scheduling?**

Acuity numeric User ID (Integrations > API > View credentials) and Acuity API key (Integrations > API > View credentials). The free call account { op: "connections.requirements", service: "acuity_scheduling" } lists exactly what to paste.

**Can an AI agent delete or change things in Acuity Scheduling?**

Only if its key allows it, and only with an explicit confirmation. 4 Acuity Scheduling actions are destructive, including delete a client, cancel an appointment and delete a block. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

**Will an AI agent use up my Acuity Scheduling API limit?**

actionlake paces every call to the limits in the Acuity Scheduling service file: 10 calls a second per connection. Repeated reads are answered from cache (21 Acuity Scheduling actions can be), which never reaches Acuity Scheduling.

**What does an Acuity Scheduling action cost?**

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (33 Acuity Scheduling actions page). Cache hits, searches, dry runs and calls Acuity Scheduling refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

**Which Acuity Scheduling API does it cover?**

The Acuity Scheduling API v1 (reference v1.1) at acuityscheduling.com/api/v1. It is built from Acuity Scheduling's documentation as read on 23 October 2026. 33 actions in 15 areas, each one in the signed service file (version 1.0.0).

**Can I combine Acuity Scheduling with my other systems?**

Yes. ask joins Acuity Scheduling to HaloPSA or NetSuite on the same customer and returns the answer rather than every row. Acuity Scheduling maps crm.contact, which 192 other connectors also map.

**Does actionlake keep my Acuity Scheduling data, and where?**

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 10 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Acuity Scheduling credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

**Which AI clients can use it?**

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

## More connectors like Acuity Scheduling

Shares the most action names with

- [Cliniko 10](https://actionlake.com/connectors/cliniko)
- [Cal.com 5](https://actionlake.com/connectors/cal-com)
- [Microsoft Bookings 4](https://actionlake.com/connectors/microsoft-bookings)
- [Elation Health 4](https://actionlake.com/connectors/elation-health)
- [Vitally 4](https://actionlake.com/connectors/vitally)
- [Halaxy 3](https://actionlake.com/connectors/halaxy)

Joins with, on shared entities

- [HaloPSA 4](https://actionlake.com/connectors/halopsa)
- [Salesforce Sales Cloud 4](https://actionlake.com/connectors/salesforce-sales-cloud)
- [Odoo 4](https://actionlake.com/connectors/odoo)
- [ERPNext (Frappe) 4](https://actionlake.com/connectors/erpnext-frappe)
- [Tripletex 4](https://actionlake.com/connectors/tripletex)
- [Microsoft Dynamics 365 4](https://actionlake.com/connectors/microsoft-dynamics-365)

Browse

- [All Work & projects connectors](https://actionlake.com/connectors/category/work-and-projects)
- [All connectors](https://actionlake.com/connectors)
- [How actionlake compares](https://actionlake.com/compare)

actionlake is independent. It is not made or endorsed by Acuity Scheduling; the name is the vendor's own. Counts are from the Acuity Scheduling service file, version 1.0.0.

## Give your agent Acuity Scheduling today.

[Connect Acuity Scheduling free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

---

Source: https://actionlake.com/connectors/acuity-scheduling
More: https://actionlake.com/llms.txt