Acuity Scheduling MCP integration for AI agents.
Connect AI agents to Acuity Scheduling through 12 structured actions, including get account, create appointment, cancel appointment, and reschedule appointme…
- ACTION CONTRACTS
- 12
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Acuity Scheduling integration exposes
The Acuity Scheduling Agent App exposes 12 provider-backed actions for productivity work. Its current contract lets an authorized agent retrieve the acuity scheduling account associated with the credential, create an appointment in acuity scheduling, and cancel an acuity scheduling appointment. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Acuity Scheduling account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Acuity Scheduling capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_accountREADRetrieve the Acuity Scheduling account associated with the credential.
create_appointmentWRITECreate an appointment in Acuity Scheduling.
INPUTS: datetime / appointmentTypeId / calendarId / timezone / addonIds
cancel_appointmentHIGH IMPACTCancel an Acuity Scheduling appointment.
INPUTS: appointmentId / cancelNote / noShow / admin / noEmail
reschedule_appointmentREVIEWReschedule an Acuity appointment to a new date and time.
INPUTS: appointmentId / datetime / calendarId / timezone / admin
get_appointmentREADRetrieve one Acuity Scheduling appointment by ID.
INPUTS: appointmentId / pastFormAnswers
list_appointment_typesREADList appointment types configured in Acuity Scheduling.
INPUTS: includeDeleted
list_appointmentsREADList Acuity Scheduling appointments with optional client and date filters.
INPUTS: max / minDate / maxDate / calendarId / appointmentTypeId
list_available_datesREADList available Acuity Scheduling dates for a month and appointment type.
INPUTS: month / appointmentTypeId / calendarId / addonIds / timezone
list_available_timesREADList available Acuity Scheduling times for a date and appointment type.
INPUTS: date / appointmentTypeId / calendarId / addonIds / timezone
list_calendarsREADList calendars configured in the Acuity Scheduling account.
list_intake_formsREADList intake forms configured in Acuity Scheduling.
update_appointmentWRITEUpdate client details, forms, notes, or labels on an Acuity appointment.
INPUTS: appointmentId / firstName / lastName / email / phone
INPUT CONTRACTS
Know what the action needs before it runs.
create_appointment
datetimeREQUIRED- The appointment start date and time.
appointmentTypeIdREQUIRED- The numeric appointment type ID.
calendarIdOPTIONAL- The numeric appointment calendar ID.
timezoneOPTIONAL- The appointment timezone.
addonIdsOPTIONAL- The add-on IDs to include for this appointment or availability query.
cancel_appointment
appointmentIdREQUIRED- The numeric appointment ID to cancel.
cancelNoteOPTIONAL- The message sent with cancellation notifications.
noShowOPTIONAL- Whether the cancellation should mark the client as a no-show.
adminOPTIONAL- Whether Acuity should apply administrative scheduling privileges.
noEmailOPTIONAL- Whether Acuity should suppress appointment email and SMS notifications.
reschedule_appointment
appointmentIdREQUIRED- The numeric appointment ID to reschedule.
datetimeREQUIRED- The new appointment start date and time.
calendarIdOPTIONALtimezoneOPTIONAL- The timezone for the new appointment time.
adminOPTIONAL- Whether Acuity should apply administrative scheduling privileges.
get_appointment
appointmentIdREQUIRED- The numeric Acuity Scheduling appointment ID.
pastFormAnswersOPTIONAL- Whether previous intake form answers should be included.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account
Retrieve the Acuity Scheduling account associated with the credential. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_accountControl Create Appointment
Create an appointment in Acuity Scheduling. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_appointmentVerify with Get Appointment
Retrieve one Acuity Scheduling appointment by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_appointmentSAFETY BOUNDARY
Operate Acuity Scheduling with explicit limits
- Authorize Acuity Scheduling with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `cancel_appointment` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Acuity Scheduling rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Acuity Scheduling task completed successfully.
CONNECTION MODEL
API key
Acuity Scheduling API Key used as the HTTP Basic password. Create or view it here: https://secure.acuityscheduling.com/app.php?action=settings&key=api
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 8
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Acuity Scheduling.