Kalendis

You can use the Kalendis MCP Tool to generate a typed TypeScript client, API routes, and utilities that connect your applications to the Kalendis scheduling API. This MCP server configuration streamlines authentication, code generation, and route handling so you can build backend and frontend integrations quickly and safely.

How to use

Set up your MCP server so your AI or automation can generate clients and routes for Kalendis endpoints. You will instantiate generated clients with your API key, then call endpoints like getting users, creating bookings, or updating availability. The MCP tool provides generated backend and frontend clients, plus API routes for common frameworks, so you can integrate Kalendis without writing boilerplate requests by hand.

How to install

Prerequisites: you need Node.js and npm installed on your system. If you don’t have them, install Node.js from the official site and npm comes bundled with it.

Install the MCP package in your project:

npm install @kalendis/mcp

Configuration and usage notes

Configure the MCP server in your project settings to run the Kalendis MCP tool client. Use the following inline configuration to register the server under the name kalendis.

{
  "mcpServers": {
    "kalendis": {
      "command": "npx",
      "args": ["-y", "@kalendis/mcp"]
    }
  }
}

Start and run

Start the MCP server using the registered stdio configuration. In typical setups, you run the command provided in the configuration to launch the MCP server process that generates the Kalendis API tools for your environment.

Environment and authentication

All Kalendis API calls require authentication via the x-api-key header. Generate and securely store your API key from your Kalendis account, then provide it to generated clients when you initialize them.

Example usage for a generated backend client: create a client instance with your API key sourced from your environment or config, for example via an environment variable named KALENDIS_API_KEY.

Security notes

Keep API keys secret and rotate them if you suspect exposure. Do not commit keys to source control. Use environment variables or a secrets manager to supply keys at runtime.

Error handling

Generated clients return clear error information for authentication failures (401), permission issues (403), network errors, and API-specific errors to help you diagnose problems quickly.

Development and contributing

If you contribute to the MCP tool, ensure your changes are compatible with the existing interface for generating clients, routes, and endpoint helpers. Build and test locally before submitting a PR.

Notes on endpoints and environments

The Kalendis MCP tool can generate access to all supported Kalendis API endpoints, and you can target development (sandbox) or production environments as configured in your Kalendis account. Use the development URL for testing and the production URL for live data.

Tools provided

The MCP tool offers the following capabilities to teams integrating Kalendis: generate-backend-client, generate-frontend-client, generate-api-routes, and list-endpoints. These tools help you produce TypeScript clients, frontend utilities, and route handlers tailored to your stack.

Available tools

generate-backend-client

Generates a TypeScript client for direct Kalendis API calls from your backend code.

generate-frontend-client

Generates a TypeScript client for frontend applications to call backend endpoints.

generate-api-routes

Generates API route handlers compatible with Next.js, Express, Fastify, or NestJS.

list-endpoints

Lists all available Kalendis API endpoints exposed by the MCP configuration.