All MCP Servers
ProductivityMCP Registryremote5 toolsC · 40

Nolizi Calendar MCP server

com.nolizi.calendar · Updated

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

At a glance

Nolizi Calendar is an MCP server in the Productivity category. It is hosted remotely and connects over HTTP, and needs Authorization. It exposes 5 tools, including list_event_types, list_available_slots and list_upcoming_bookings. It scores C (40/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install Nolizi Calendar in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install Nolizi Calendar in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add --transport http calendar https://calendar.nolizi.com/mcp --header 'Authorization: Bearer <YOUR_TOKEN>'
  2. Fill in your credentials

    Replace Bearer <YOUR_TOKEN> with your real value. Keep secrets out of any config file you commit.

  3. Verify it's connected

    bash
    claude mcp list
  4. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  5. Use it in a session

    Ask Claude to use the tools this server exposes (e.g. list_event_types, list_available_slots, list_upcoming_bookings). It discovers them automatically.

What does Nolizi Calendar need from you?

Bearer token — Bearer followed by your API key from https://calendar.nolizi.com/app/api-keys. Keys carry full owner permissions.

  • AuthorizationrequiredsecretHTTP header

    Bearer followed by your API key from https://calendar.nolizi.com/app/api-keys. Keys carry full owner permissions.

What tools does Nolizi Calendar expose? (5)

Read from the live server. Click any tool for its input schema.

  • 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 booking page instead.
  • list_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_booking unchanged.
  • list_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 must be copied verbatim from a recent list_available_slots response; this server re-checks them against
  • cancel_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 several meetings, so confirm with the person which meetings they mean.

What the code can do

This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Third-party hosted service — Your requests and any data in them are sent to calendar.nolizi.com.
  • No local execution — Nothing is installed or run on your machine.
  • No source repository — This registry entry does not link to a public repo, so its code cannot be reviewed before you install it.

Client compatibility

Claude Code: NativeClaude Desktop: Via mcp-remoteCursor: NativeCodex CLI: Via mcp-remoteWindsurf: NativeCline: NativeVS Code: Native

Health score

C · 40

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%not measurable

    No commit history available.

  • Adoption20%not measurable

    No usage data available.

  • Transparency20%25%

    1/4: ✗ public source repo, ✗ declared license, ✗ documentation, ✓ discoverable tool list.

  • Provenance15%0%

    No source repository to trace the code back to.

  • Packaging15%100%

    Remote endpoint with documented authentication.

Maintain Nolizi Calendar? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![Nolizi Calendar on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/com-nolizi-calendar-calendar)](https://mcp-skills-hub.vercel.app/mcps/com-nolizi-calendar-calendar)

Catalog data refreshed . Something wrong? Report it.