Calendly vs Acuity Scheduling for AI agents
Calendly is more ready for AI agents than Acuity Scheduling: 90 vs 67 out of 100. Calendly is ahead on JSON-LD, semantic HTML and a remote MCP server.
What an agent finds
| Calendly | Acuity Scheduling | |
|---|---|---|
| Score | 90/100 | 67/100 |
| Blocks AI agents | No | No |
| robots.txt disallows | CCBot | No AI bots |
| llms.txt | At the root | On the docs host |
| Remote MCP server | mcp.calendly.com/ | none found |
| Docs MCP server | developer.calendly.com/mcp | none found |
| OpenAPI spec | none found | none found |
| Developer docs | developer.calendly.com/docs/getting-started/overview | developers.acuityscheduling.com/?nav-ref=navbar&dropdown-ref=resources |
| Public pricing | calendly.com/pricing | acuityscheduling.com/pricing?entry_point=acuity&btn=nav |
| Self-serve sign-up | Yes, opens for agents | No self-serve page we could open |
Check by check
60 core points every site needs, plus 40 split between letting an agent sign a team up and connecting through the API. Sign-up and API checks count half each.
| Check | Points | Calendly | Acuity Scheduling |
|---|---|---|---|
| Core | 58 | 49 | |
| Agents get the real page, not a bot wall | 12 | ✓ | ✓ |
| robots.txt lets user-triggered agents in | 6 | ✓ | ✓ |
| Answer-engine crawlers are allowed | 4 | ✓ | ✓ |
| Content is in the raw HTML | 6 | ✓ | ✓ |
| Semantic HTML (main, nav, header) | 4 | ✓ | · |
| Icon buttons and links have names | 3 | ✓ | ✓ |
| Form fields have labels | 3 | ✓ | ✓ |
| Images have alt text | 3 | ✓ | ✓ |
| The page has an H1 | 2 | ✓ | ✓ |
| Structured data (JSON-LD) | 5 | ✓ | · |
| Meta description and Open Graph tags | 3 | ✓ | ✓ |
| sitemap.xml | 3 | ✓ | ✓ |
| llms.txt | 4 | ✓ | ✓ |
| Dates show the content is fresh | 2 | · | · |
| Sign-up | 17 | 14 | |
| Public pricing page | 5 | ✓ | ✓ |
| A self-serve sign-up link | 4 | ✓ | ✓ |
| Sign-up page opens for agents | 3 | ✓ | · |
| A free plan or trial | 3 | ✓ | ✓ |
| No card needed to start | 2 | ✓ | ✓ |
| SoftwareApplication data | 3 | · | · |
| API | 15 | 4 | |
| OpenAPI spec | 3.5 | · | · |
| Remote MCP server | 4 | ✓ | · |
| Docs as markdown | 2.5 | ✓ | ✓ |
| Self-serve API keys | 3 | ✓ | · |
| OAuth client self-registration | 2.5 | ✓ | · |
| OAuth discovery metadata | 1.5 | ✓ | · |
| SDKs and a CLI | 1.5 | · | · |
| Free tier or test keys | 1.5 | ✓ | ✓ |
Automated, read-only scan of each homepage, robots.txt, llms.txt, docs, OpenAPI paths and MCP endpoints on 3 Nov 2026. How scoring works.
Check them again today
Sites change. Run the live scan for the current result, or check your own site.
Questions
Is Calendly or Acuity Scheduling better for AI agents?
Calendly is more ready for AI agents than Acuity Scheduling: 90 vs 67 out of 100. Calendly is ahead on JSON-LD, semantic HTML and a remote MCP server. Scores are from our scan on 3 Nov 2026.
Does Calendly have an MCP server?
Yes. Our scan reached a remote MCP server at https://mcp.calendly.com/ on 3 Nov 2026.
Does Acuity Scheduling have an MCP server?
Not one we could find. On 3 Nov 2026 our scan found no remote MCP server for Acuity Scheduling at the usual addresses (mcp.acuityscheduling.com/mcp, api.acuityscheduling.com/mcp, the docs host, or any MCP URL linked from its homepage or llms.txt).
Does Calendly block AI agents?
Not outright: its homepage loads for an AI user-agent, but its robots.txt disallows CCBot.
Does Acuity Scheduling block AI agents?
No. Acuity Scheduling served its homepage to an AI user-agent and its robots.txt doesn't disallow any of the AI crawlers we check.