Skip to directory

About Kalendis MCP Tool

A local MCP tool for generating TypeScript clients and API route handlers for the Kalendis scheduling API; generated outputs cover backend/frontend clients and several web frameworks.

What you can use it for

  • Generate typed API clients for Kalendis scheduling operations
  • Generate API route handlers for Next.js, Express, Fastify, or NestJS
Connection and setup
Hosting
Local
Transport
stdio
Endpoint
Local process; no hosted endpoint documented
Authentication
The current package says the MCP tool itself only generates code and does not use the API key; generated clients require KALENDIS_API_KEY. An introductory section elsewhere on the package page says an API key is required for MCP use, so this requirement is documented inconsistently.

Requirements

  • Node/npm or npx
  • Kalendis account/API key only for generated clients that call the Kalendis API

Setup steps

  1. Run `npx -y @kalendis/mcp` as a local stdio server.
  2. Use the generator tools to produce backend/frontend TypeScript clients or route handlers, or list API endpoints.
  3. Generated backend clients call https://api.kalendis.dev by default and require KALENDIS_API_KEY via x-api-key; configure secrets in the generated application environment.
Tools 4

Four exact generator tools are listed in package version 1.1.4. The README’s key requirement statements conflict: it says the MCP generator needs no key but generated API clients do; document KALENDIS_API_KEY for generated clients, not as a proven MCP server prerequisite.

  • generate-backend-client

    Generate a typed TypeScript client for server-side Kalendis API calls.

    01
  • generate-frontend-client

    Generate a typed TypeScript client for frontend integration with the Kalendis API.

    02
  • generate-api-routes

    Generate API route handlers for supported web frameworks.

    03
  • list-endpoints

    List Kalendis API endpoints available to generated clients.

    04
Limitations and notes
  • The MCP is a code generator; the generated code's API access is separate and requires a key.
  • Package page has contradictory wording about whether the MCP tool itself needs an API key; unresolved in source_conflicts.
  • The package description also mentions client/route generators; do not mistake those for the MCP server's tools.
Source discrepancies
  • Package quick start says an API key is needed before using the MCP tool, while its Authentication section says the MCP tool itself does not use a key and generated clients require one. Record follows the detailed Authentication section; verify against a future package release.
Original sources
  • official documentation

    The current @kalendis/mcp package page (v1.1.4) lists the same four MCP tools: generate-backend-client, generate-frontend-client, generate-api-routes and list-endpoints. These generate code or list API endpoints; the MCP generator itself does not call the user’s scheduling API. Generated application clients use KALENDIS_API_KEY. Package docs conflict on whether the MCP process itself requires a key, so retain that as an authentication documentation discrepancy.

Documentation checked 2026-10-28T13:26:33Z. Connection has not been runtime tested.