Calcom Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.1.0Updated Oct 26, 2026

Query Cal.com API v2: event types, bookings, schedules. v1 is decommissioned.

VerifiedSTDIODesktop onlyProductivity & Workflow

Overview

AI-generated overview

Local MCP server that lets an assistant query the Cal.com API v2 for event types, bookings and schedules.

What you can do
  • Query Cal.com event types
  • Look up bookings
  • Read schedules
  • All access goes through the Cal.com API v2; the older v1 API is decommissioned.
When to use it
Useful when you want an assistant to look up Cal.com scheduling data — event types, bookings or schedules — while working locally on your desktop.
Requirements
Runs as a local stdio process installed from the npm package calcom-mcp, so a Node.js environment is needed. The manifest declares no authentication, environment variables or headers, so how Cal.com credentials are supplied is not documented here. Desktop only; no web executable.
Before you install
The manifest declares no authentication, yet the server queries a Cal.com account's API; expect to need Cal.com API credentials, and check how they are passed before installing. Booking and schedule data is personal and may be sent to the assistant and its model provider.

Installation

In SourceWeft

  1. Open Calcom Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.0LatestOct 17, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.