Kalendis MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate-backend-clientB | Generate a TypeScript client that calls Kalendis API directly with x-api-key authentication |
| generate-frontend-clientC | Generate a TypeScript client for frontend apps that calls your backend API endpoints |
| generate-api-routesC | Generate API route handlers for Next.js or Express that use the Kalendis backend client |
| list-endpointsB | List all available Kalendis API endpoints with descriptions |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: generate-api-routes creates backend route handlers, generate-backend-client builds a direct API client, generate-frontend-client creates a client for frontend apps, and list-endpoints provides API documentation. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with 'generate-' or 'list-' prefixes, using kebab-case throughout. This predictability enhances readability and reduces cognitive load for agents when scanning the toolset.
Four tools is reasonable for a code generation and API documentation server, though it feels slightly minimal. The tools cover key workflows (client generation, route handling, endpoint listing), but additional utilities like validation or testing helpers could enhance completeness without overloading the set.
The toolset covers core aspects of integrating with the Kalendis API: generating clients for both backend and frontend, creating API routes, and listing endpoints. A minor gap exists in tools for managing API keys or handling errors, but agents can work around this with the provided tools for most common tasks.