kanpla-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KANPLA_BASE | No | Base URL for Kanpla (might differ for regional accounts). | https://app.kanpla.io |
| KANPLA_EMAIL | Yes | Your Kanpla login email. | |
| KANPLA_LANGUAGE | No | Language code for menu text (e.g. en, da, nb). | en |
| KANPLA_PASSWORD | Yes | Your Kanpla password. | |
| KANPLA_MODULE_ID | No | Canteen/module ID. Optional if you use list_modules to discover it first. | |
| KANPLA_FIREBASE_API_KEY | Yes | Public Firebase client key (AIza...) from app.kanpla.io network request. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_today_menuA | Returns the available Kanpla menu items for today. |
| get_menu_for_dateB | Returns the available Kanpla menu items for a specific date. |
| list_modulesA | Lists the canteens/modules available to your account, so you can find your moduleId. |
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 3 tools
The tools get_menu_for_date and get_today_menu have overlapping purposes, as both return menu items. The descriptions distinguish them by date specificity, but an agent could still be confused about which to use. list_modules is distinct.
Tool names follow a verb_noun pattern with snake_case (get_menu_for_date, get_today_menu, list_modules). The mix of 'get' and 'list' verbs is minor, and overall the naming is predictable.
With only 3 tools, the server feels under-scoped for a menu system. While it covers basic retrieval, additional tools for date ranges or module-specific menus would justify the count.
The tool surface lacks critical operations beyond retrieval, such as searching, filtering by module, or updating menu items. An agent cannot perform common tasks like getting menus for a week, which leaves significant gaps.