Skip to main content
Glama
Sign In
kalender.digital MCP Server

kalender.digital MCP Server

by Movm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

kalender.digital MCP Server

Ein kleiner MCP-Server für die offizielle kalender.digital API. Er stellt Termine und Unterkalender als klar getrennte MCP-Tools bereit.

Funktionen

  • Termine auflisten und einzeln abrufen

  • Termine erstellen, vollständig ändern und löschen

  • Unterkalender erstellen, umbenennen und löschen

  • Lokal über stdio oder als Streamable-HTTP-Server nutzbar

  • API-Key ausschließlich über eine Umgebungsvariable

Die kalender.digital API ist laut Anbieter Teil der Premium-Version.

Related MCP server: Google-Calendar Universal MCP

Voraussetzungen

  • Node.js 20 oder neuer

  • pnpm

  • Ein kalender.digital API-Key aus Admin-Einstellungen → API

Installation

pnpm install
pnpm build

Lokal starten (stdio)

KALENDER_DIGITAL_API_KEY="dein-api-key" pnpm start

Beispiel für eine MCP-Client-Konfiguration:

{
  "mcpServers": {
    "kalender-digital": {
      "command": "node",
      "args": ["/ABSOLUTER/PFAD/kalender-digital-mcp/dist/index.js"],
      "env": {
        "KALENDER_DIGITAL_API_KEY": "dein-api-key"
      }
    }
  }
}

HTTP-Modus

KALENDER_DIGITAL_API_KEY="dein-api-key" \
MCP_TRANSPORT=http \
MCP_ALLOWED_ORIGINS="https://claude.ai,https://chatgpt.com" \
PORT=3000 \
pnpm start

Der MCP-Endpunkt liegt unter http://localhost:3000/mcp, der Health-Check unter /health. Requests ohne Origin (typische Server-zu-Server-MCP-Clients) sind erlaubt. Browser-Origins müssen explizit in MCP_ALLOWED_ORIGINS stehen.

Der HTTP-Modus verwendet einen gemeinsamen kalender.digital API-Key für alle Nutzer. Für einen öffentlichen Mehrnutzer-Dienst sollte davor eine eigene Authentifizierung ergänzt werden.

Tools

Tool

Wirkung

list_events

Termine in einem Zeitraum abrufen

get_event

Einzelnen Termin abrufen

create_event

Termin erstellen

update_event

Termin vollständig ändern

delete_event

Termin löschen

create_subcalendar

Unterkalender erstellen

update_subcalendar

Unterkalender umbenennen

delete_subcalendar

Unterkalender löschen

Webhooks werden in kalender.digital selbst eingerichtet und sind deshalb kein MCP-Tool.

Entwicklung

pnpm test
pnpm check
pnpm build

Lizenz

MIT

Available Tools

8 tools
create_eventCreate calendar eventA

Create an event in one or more kalender.digital subcalendars. API documentation: https://kalender.digital/c/documentation/api?lang=de

Inputs: title (required), endDate (required), startDate (required), subCalendars (required), +6 more.

create_subcalendarCreate subcalendarA

Create a kalender.digital subcalendar. API documentation: https://kalender.digital/c/documentation/api?lang=de

Inputs: name (required).

delete_eventDelete calendar eventA
DestructiveIdempotent

Permanently delete a kalender.digital event by ID. API documentation: https://kalender.digital/c/documentation/api?lang=de

Inputs: eventId (required).

delete_subcalendarDelete subcalendarA
DestructiveIdempotent

Permanently delete a kalender.digital subcalendar. API documentation: https://kalender.digital/c/documentation/api?lang=de

Inputs: subcalendarId (required).

get_eventGet calendar eventA
Read-onlyIdempotent

Fetch one kalender.digital event by its event ID. Use list_events if the ID is unknown. API documentation: https://kalender.digital/c/documentation/api?lang=de

Inputs: eventId (required), timeZone.

list_eventsList calendar eventsA
Read-onlyIdempotent

List kalender.digital events within an inclusive date range, optionally filtered by a search query. API documentation: https://kalender.digital/c/documentation/api?lang=de

Inputs: endDate (required), startDate (required), query, timeZone.

update_eventUpdate calendar eventA
DestructiveIdempotent

Replace the editable fields of an existing kalender.digital event. All event fields are required. API documentation: https://kalender.digital/c/documentation/api?lang=de

Inputs: title (required), endDate (required), eventId (required), startDate (required), +7 more.

update_subcalendarUpdate subcalendarB
DestructiveIdempotent

Rename an existing kalender.digital subcalendar. API documentation: https://kalender.digital/c/documentation/api?lang=de

Inputs: name (required), subcalendarId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets either an event or a subcalendar resource with a unique action. No two tools could be confused, as event tools handle event lifecycle and subcalendar tools handle subcalendar lifecycle.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case (create_, update_, delete_, list_events, get_event). The naming is uniform and predictable across both resource types.

    Tool Count5/5

    Eight tools is well-scoped for a calendar server, covering events and subcalendars without unnecessary bloat. Each tool serves a clear purpose within the domain.

    Completeness3/5

    Events have full CRUD plus list coverage, but subcalendars lack list and get operations. This is a notable gap because agents cannot discover existing subcalendars to assign events to, limiting workflow completion.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers