Can I use Acuity Scheduling as a CLI?

Yes. KosmoKrator exposes a Acuity Scheduling CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Acuity Scheduling through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Acuity Scheduling tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Acuity Scheduling credentials stored?

Acuity Scheduling credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Acuity Scheduling MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

other

Acuity Scheduling CLI for Shell Scripts

Use the Acuity Scheduling CLI for shell scripts with headless JSON commands, schema discovery, credentials, and permission controls.

8 functions 7 read 1 write Manual OAuth token auth

Submit Acuity Scheduling feedback View package source

Acuity Scheduling CLI for Shell Scripts

Call integration functions from shell scripts with stable JSON input and output.

Use shell scripts for small local automations that need one or more integration calls. The Acuity Scheduling CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Acuity Scheduling CLI for Shell Scripts
kosmokrator integrations:configure acuity-scheduling --set access_token="$ACUITY_SCHEDULING_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmo integrations:call acuity-scheduling.acuity_list_appointments '{"minDate":"example_minDate","maxDate":"example_maxDate","calendarID":1,"appointmentTypeID":1,"max":1,"direction":"example_direction"}' --json

Discovery Before Execution

Agents and scripts can inspect Acuity Scheduling docs and schemas before choosing a function.

kosmo integrations:docs acuity-scheduling --json
kosmo integrations:docs acuity-scheduling.acuity_list_appointments --json
kosmo integrations:schema acuity-scheduling.acuity_list_appointments --json
kosmo integrations:search "Acuity Scheduling" --json
kosmo integrations:list --json

Useful Acuity Scheduling CLI Functions

Function	Type	Parameters	Description
`acuity-scheduling.acuity_list_appointments`	Read	minDate, maxDate, calendarID, appointmentTypeID, max, direction	List appointments from Acuity Scheduling. Returns upcoming and past appointments with client details, date/time, and status. Use filters to narrow results by date range, calendar, or appointment type.
`acuity-scheduling.acuity_get_appointment`	Read	id	Get full details of a specific appointment in Acuity Scheduling by its ID. Returns client info, date/time, location, forms, and status.
`acuity-scheduling.acuity_list_clients`	Read	search, email, max	List clients from Acuity Scheduling. Search by name, email, or phone. Returns client contact information and history.
`acuity-scheduling.acuity_list_calendars`	Read	none	List all calendars in Acuity Scheduling. Returns calendar IDs, names, and timezone info. Use calendar IDs to filter appointments.
`acuity-scheduling.acuity_list_appointment_types`	Read	none	List all appointment types (services) in Acuity Scheduling. Returns type IDs, names, duration, price, and category. Use type IDs to filter appointments or check availability.
`acuity-scheduling.acuity_cancel_appointment`	Write	id	Cancel an existing appointment in Acuity Scheduling. Requires the appointment ID. The appointment will be marked as cancelled and the client will be notified according to notification settings.
`acuity-scheduling.acuity_get_availability`	Read	appointmentTypeID, date, calendarID, timezone	Get available time slots for booking in Acuity Scheduling. Returns open times for a given appointment type, date, and optional calendar.
`acuity-scheduling.acuity_get_current_user`	Read	none	Get the currently authenticated Acuity Scheduling user profile. Returns user name, email, timezone, and account details.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Acuity Scheduling CLI Pages

CI Acuity Scheduling CLI for CI. Cron Jobs Acuity Scheduling CLI for cron jobs. Headless Automation Acuity Scheduling CLI for headless automation. Coding Agents Acuity Scheduling CLI for coding agents.