Acuity Scheduling MCP server for your AI

No. You copy a User ID and an API Key from Acuity's Bizz Settings > Integrations > API screen and paste both into the connect form. There is no OAuth popup, no redirect URL to register and no token refresh to maintain; authentication happens server-side over HTTPS using HTTP Basic. The key is scoped to a single Acuity account, so the connection is locked to that account.

Yes, but Acuity splits the job across three calls, and that is the thing people trip on. acuity_update_appointment handles client details and intake-form answers only, against a white-list of fields; moving a booking to a new day or time is acuity_reschedule_appointment; calling it off is acuity_cancel_appointment. Asking one generic update to do all three will not work.

Availability is exposed as separate reads: acuity_list_availability_dates for the bookable dates in a month, acuity_list_availability_times for the slots on a given date, and acuity_list_availability_classes for group class instances and their remaining spots. Before writing, acuity_check_times re-validates specific slots. Have the agent check times immediately before acuity_create_appointment, since availability moves between the read and the write.

All of them. acuity_list_appointment_types returns both services and classes, acuity_list_products covers packages, subscriptions and gift certificates offered for sale, and acuity_list_orders with acuity_get_order covers what clients actually bought. Redeemable codes have their own calls for issuing, validating, listing and deleting.

The write side includes cancelling appointments, deleting clients, deleting blocked-off time, deleting issued certificates and removing webhook subscriptions. Read-only mode keeps all of those out of reach entirely. Full access with approval-required-for-writes leaves them available but holds each call for your confirmation, while reads such as listing appointments or clients run untouched.

Fourteen. Six come through Acuity's own webhooks: appointment booked, rescheduled, cancelled and details changed, plus order completed and gift certificate issued. The other eight are change detection over the account - new client added, order placed, time blocked off, appointment type added, product added, calendar added, intake form changed and certificate code added. The agent can also manage subscriptions directly with acuity_create_webhook, acuity_list_webhooks and acuity_delete_webhook.

No. PopMCP hosts it and gives you a Streamable HTTP MCP URL. There is nothing to deploy, no callback URL to register, and no infrastructure to keep running or patch.

Any client that supports a remote Streamable HTTP MCP server — Claude Desktop, Claude Web, ChatGPT custom connectors, Codex and the Codex CLI, OpenCode and Z.ai's ZCode, as well as editors such as Cursor, Windsurf and Zed. Your client signs in to PopMCP with OAuth; the provider credential never leaves the server.

Loading 36 tool definitions into every conversation burns context before the work starts. PopMCP loads a curated 29-tool set covering the everyday workflows and keeps the rest searchable, so your AI pulls a specialist tool only when a task needs it. You can switch a connection to the full catalog at any time.

A tool is something your AI calls — there are 36 here. A trigger is something PopMCP watches for you: 14 Acuity Scheduling events that can start work on the PopMCP side. Triggers never enter your AI client's context, and none of them ask you to paste a callback URL into Acuity Scheduling.