AI agent for Acuity Scheduling
Connect Acuity Scheduling to your AI agent through the WorkAist MCP server.
The WorkAist Acuity Scheduling connector is a production-grade Model Context Protocol (MCP) server. AI agents can read and write Acuity Scheduling data — booking — through one consistent interface. Open-source under AGPL-3.0, self-hosted, with reversible PII redaction at the LLM boundary.
Authentication & setup
The Acuity Scheduling connector authenticates via API key.
Generate an API key in the service dashboard and paste it at install time. WorkAist encrypts it at rest.
Frequently paired with Acuity Scheduling
FAQ
Can a WorkAist AI agent really automate Acuity Scheduling end-to-end?▼
Yes. The connector exposes read and write tools through Model Context Protocol. AI agents call them through plain-language instructions in a CLAUDE.md file — no glue code.
How does this differ from using the Acuity Scheduling API directly?▼
The connector adds permission isolation, audit logging, cost tracking per agent, and reversible PII redaction at the LLM boundary. It also presents Acuity Scheduling as part of a unified Knowledge Graph alongside your other tools.
What does it cost?▼
WorkAist is open-source under AGPL-3.0 and self-hosted, so the connector itself is free. You pay only for Acuity Scheduling's own API costs (if any) and the LLM tokens your agent consumes.
Is my Acuity Scheduling data sent to a third party?▼
No. WorkAist runs in your own infrastructure. Data flows from Acuity Scheduling → your WorkAist instance → the LLM you choose. Sensitive fields can be tokenized before reaching the LLM.
What if Acuity Scheduling changes its API?▼
The connector is versioned and published openly. When Acuity Scheduling ships breaking changes, we bump the connector version and the marketplace UI surfaces the upgrade as a one-click apply.