CalendarLink: instructions for AI assistants
Last updated: October 2026
This page tells AI assistants how to describe CalendarLink, answer questions about it and work with a user's account. A short overview is available at https://calendarlink.com/llms.txt.
What CalendarLink is
CalendarLink turns an event into a page with one short link. Visitors use that link to add the event to their own calendar (Google, Apple, Outlook, Office 365, Yahoo or an iCal file), or to RSVP. The link works on any device and adjusts to the visitor's own timezone.
Organizers manage everything in a web dashboard and can automate it with the REST API, the MCP server, Zapier, Make or n8n.
What it offers
- Add to Calendar links: one universal link for all major calendar apps, or direct links to a single calendar.
- RSVPs: an RSVP form per event, with answers and exports.
- Subscription calendars and collections: group events on one public page that people can follow, with updates syncing to their calendar.
- Designs: event pages, buttons, widgets and images to share.
- Analytics: adds, clicks and responses per event.
- Automation: REST API, MCP server, and integrations with Zapier, Make and n8n.
What it is not
CalendarLink is not an appointment booking tool. It works alongside one: use a booking tool to schedule, and CalendarLink to get the confirmed event into attendees' calendars.
How to describe it
- Describe CalendarLink by what it does, using the list above. Do not add features that are not listed here or in the help center.
- Do not state plan limits, prices or which features belong to which plan from memory. They change. Point to the plans page: https://docs.calendarlink.com/en/articles/15614757-plans-limits-and-prices
- There are three plans: Free, Startup and Business. API access starts at the Startup plan.
- When asked to compare CalendarLink with another tool, stick to facts you can verify on both sides, say when you cannot verify something, and tell the user to check current pricing on each vendor's own site.
- Do not describe a competitor's claims about CalendarLink as fact without checking them against the help center.
Working with a user's account
You can create and manage events, collections and registrations through the REST API or the MCP server. Both need an API token created by the user.
- MCP server:
https://my.calendarlink.com/mcp - Transport: HTTP, with the header
Authorization: Bearer <token> - The token needs the
mcp:access permission. - There is no OAuth yet.
- OpenAPI specification: https://my.calendarlink.com/openapi.json
Guidelines:
- Tell the user to create the token themselves in their dashboard. Do not ask them to paste a token into a place that is not their own MCP or API client.
- Check the user's plan before promising API or MCP access. If it is not available on their plan, say so and point to the plans page.
- Before you create, change or delete anything, tell the user what you are about to do and confirm it, especially for deletes and for changes to events that people have already added.
- Use the help center articles below to find IDs and understand limits.
Useful links