Nolizi Calendar

com.nolizi.calendarPublished by calendar.nolizi.comOfficial publisherv0.10.5Updated Oct 24, 2026

Free scheduling your agent can book through: live availability, booking, verification, cancel.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

A remote scheduling server that lets an assistant list bookable event types, check live availability, create real bookings, verify them, and cancel them.

What you can do
List the account's bookable event types and their slugs, which every other tool needs. Check live available start and end times for one event type. List up to 100 upcoming confirmed bookings to verify that a booking exists. Create a real booking, sending invitations and writing to connected calendars. Cancel a confirmed booking by its exact booking ID.
When to use it
Use it when you want an assistant to schedule meetings on a Nolizi Calendar account: finding open slots, booking a confirmed time with a real attendee, checking that a booking went through, or cancelling one.
Requirements
A remote endpoint at calendar.nolizi.com over streamable HTTP. A Nolizi Calendar account and an API key, sent as an Authorization bearer header. Network access to the service.
Before you install
The API key carries full owner permissions, so treat it as a sensitive secret. Creating a booking sends invitations and writes to connected calendars and cannot be undone except by cancelling; cancelling notifies the attendee, removes the meeting from calendars, and cannot be undone. Cancelling one occurrence of a grouped or recurring booking can affect others. Events with required custom questions or email verification cannot be booked through this API.

Installation

In SourceWeft

  1. Open Nolizi Calendar in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.nolizi.calendar%2Fcalendar/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "nolizi-calendar": {
      "type": "http",
      "url": "https://calendar.nolizi.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

5

list_event_types

List event types

List 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 booking page instead.

Takes no parameters.

list_available_slots

List available times

Return 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_booking unchanged.

Parametersevent_typerequired

list_upcoming_bookings

List upcoming bookings

List 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.

Takes no parameters.

create_booking

Create a booking

Book 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 must be copied verbatim from a recent list_available_slots response; this server re-checks them against live availability and refuses times it cannot find. There is no idempotency key: if this call returns an uncertain outcome, do not call it again — call list_upcoming_bookings and read what actually happened.

Parametersendrequirednamerequirednoteemailrequiredstartrequiredbooker_tzevent_typerequired

cancel_booking

Cancel a booking

Cancel 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 several meetings, so confirm with the person which meetings they mean.

Parametersbooking_idrequired

Version history

1
  1. v0.10.5LatestSep 21, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.