EMAIL & COMMUNICATION · FOR AI AGENTS
Cronofy
Coordinate availability and scheduling across authorized calendars.
Use Cronofy’s calendar APIs for synchronized calendar access and availability, or its MCP server to create scheduling links and suggest meeting times through Cronofy Scheduler.
Your integration checklist
- Capabilities
- What you need from your owner
- For MCP, create a Scheduler account and developer application in the correct data center. Connect the calendars and select an internal or multi-tenant authorization model.
- Authentication
- Single-tenant MCP uses the internal application client secret as a bearer token. Multi-tenant clients use OAuth through a registered application; dynamic client registration is not supported.
- Your first task
- Read availability for the intended participants and generate a scheduling proposal before sending a link or changing a calendar.
- Billing & payment
- API/OEM plans include allowances for synchronized accounts, application calendars and invitations, with additional-unit charges. Direct Scheduler licensing is separate; confirm which plan covers your MCP or embedded workflow.
- Agent payment support
- Not verified. Programmatic usage does not establish autonomous checkout support.
- Operational limits
- Internal applications can access all members of their organizational unit. Use the matching regional API host. Application calendars cannot send or receive invitations like connected user calendars.
ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK
Resolve participants and authorization before proposing a time
Editorial recommendation · Reviewed 2026-10-18
When to choose this service
Choose Cronofy for coordinated availability and calendar connectivity, especially when scheduling rules span several people. Check the intended Scheduler or API licensing route before integration.
Live calendar state and authorized provider connections are external dependencies. Reasoning about an ideal meeting time cannot reveal a participant’s current availability or reserve their calendar.
Suggested workflow
- Resolve participant identities, calendar access and the event’s time zone. Separate working-hour preferences from actual busy periods.
- Request availability and prepare a bounded proposal. Recheck the selected slot immediately before the approved scheduling action.
- Retain the link or event identifier and inspect the resulting state. Report a proposed time, an invitation and a confirmed booking as distinct outcomes.
Acceptance checks before real work
- Check daylight-saving offsets for the meeting date.
- Confirm which organizational unit an internal application can act for.
- Verify notification behavior before changing an event with attendees.
If the workflow fails
If a calendar authorization expires, reconnect the intended account. After an ambiguous write, retrieve the event or scheduling request before creating another invitation.