Nolizi Calendar
com.nolizi.calendar/calendar · v0.10.5
Free scheduling your agent can book through: live availability, booking, verification, cancel.
MCPremoteAPI keyCalendarEmail
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 5 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 88/100
What it does: 5 tools · 3 read, 2 write (incl. delete/pay) · Calendar, Email
Test call list_event_types: needs a key: tool error: This endpoint needs your Nolizi Calendar API key. Create one at https://calendar.nolizi.com/app/api-keys and configure y (955 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: +5
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://calendar.nolizi.com/mcpTools
5 tools listed at last check
list_event_typesList the bookable event types owned by the configured Nolizi Calendar account. Start here: the returned slug is what every other tool needs. Never guess a slug. Events with required custom questions or email verification cannot be booked through this API — send the person to the event’s public bookilist_available_slotsReturn the live available start/end pairs for one event type. These are real times on a real calendar: show them to the person and let them choose. Do not invent, extrapolate or round a time that is not in this response. Convert times for display only — pass the original values back to create_bookinlist_upcoming_bookingsList up to 100 upcoming confirmed bookings. This is the only way to verify that a booking exists. Use it after every create or cancel, and use it first whenever a write returned an uncertain outcome.create_bookingBook a real meeting. This sends invitations and writes to connected calendars, and it cannot be undone except by cancelling. Ask the person to confirm the event, the exact time and the attendee details before calling it, and use their real name and email — never a placeholder. The start and end mustcancel_bookingCancel a confirmed booking. This notifies the attendee and removes the meeting from connected calendars, and it cannot be undone. Use an exact booking_id taken from list_upcoming_bookings — never a guessed or reconstructed one. Cancelling one occurrence of a grouped or recurring booking can affect s
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/com.nolizi.calendar/calendar)