[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Acuity Scheduling MCP tools

> The Acuity Scheduling MCP tools on the Cotlet server: every operation with its input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/acuity-scheduling

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Acuity Scheduling has 10 operations on the Cotlet MCP server, in acuity_scheduling_read and acuity_scheduling_write. Your agent picks one in `operation`; the tool carries each operation's input schema. Open an operation for its schema and an example call.

- MCP server: `https://cotlet.dev/mcp/v1`
- MCP tools: `acuity_scheduling_read`, `acuity_scheduling_write`
- Connects with: Your own Acuity Scheduling admin login (the account owner, or staff with View & Edit access). What your agent can do follows your access level. You sign in in your own browser and keep your 2-step verification.
- Integration page: https://cotlet.dev/integrations/acuity-scheduling-api-mcp-server

## Read

Return data and change nothing in the account.

| Operation | Description |
|---|---|
| [`list_appointments`](https://cotlet.dev/docs/mcp/acuity-scheduling/list_appointments.md) | Appointments with client, type, calendar, time and payment status, filtered by date, calendar, type or client. |
| [`get_appointment`](https://cotlet.dev/docs/mcp/acuity-scheduling/get_appointment.md) | One appointment with its intake form answers, notes, label and payment fields. |
| [`list_appointment_types`](https://cotlet.dev/docs/mcp/acuity-scheduling/list_appointment_types.md) | Your appointment types with duration, price and the calendars that offer each one. |
| [`check_availability_dates`](https://cotlet.dev/docs/mcp/acuity-scheduling/check_availability_dates.md) | Days in one month that have openings for an appointment type. |
| [`check_availability_times`](https://cotlet.dev/docs/mcp/acuity-scheduling/check_availability_times.md) | Open times on one date for an appointment type. |

## Write

Change the account. Calls marked Confirm wait for the user to approve them.

| Operation | Description |
|---|---|
| [`book_appointment`](https://cotlet.dev/docs/mcp/acuity-scheduling/book_appointment.md) (Confirm) | Book a client into an open time for an appointment type. |
| [`reschedule_appointment`](https://cotlet.dev/docs/mcp/acuity-scheduling/reschedule_appointment.md) (Confirm) | Move an appointment to a new date and time, or to another calendar. |
| [`cancel_appointment`](https://cotlet.dev/docs/mcp/acuity-scheduling/cancel_appointment.md) (Confirm) | Cancel an appointment, optionally marking a no-show. |
| [`update_appointment`](https://cotlet.dev/docs/mcp/acuity-scheduling/update_appointment.md) (Confirm) | Edit client name, phone, email, notes or label on an appointment. |
| [`block_off_time`](https://cotlet.dev/docs/mcp/acuity-scheduling/block_off_time.md) (Confirm) | Block a time range on a calendar so no new client can book it. |

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

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.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.