wolt-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WOLT_MCP_LOG | No | Python logging level | WARNING |
| WOLT_LANGUAGE | No | Language for Accept-Language header | en |
| WOLT_DEFAULT_LAT | No | Default latitude for location queries | 59.4370 |
| WOLT_DEFAULT_LON | No | Default longitude for location queries | 24.7536 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_nearbyA | List Wolt venues near a location. Defaults to Tallinn center. Returns compact dicts with slug, rating, ETA, online status, tags. Use |
| get_menuA | Fetch a venue's full menu by slug. Returns categories and items with prices in minor units (e.g. 2390 = 23.90 EUR in Estonia). Each item includes |
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 2 tools
The two tools have completely distinct purposes: list_nearby finds venues, get_menu retrieves menu details for a specific venue. No overlap.
Both tools follow a verb_noun pattern ('get_menu', 'list_nearby'), though 'list_nearby' uses an adjective which is a minor deviation.
Only 2 tools is on the low end for a food delivery service, but it may be acceptable for a simple discovery-focused server. However, it feels thin for broader use cases.
The server covers basic venue discovery and menu retrieval, but lacks essential operations like searching items, user authentication, order management, or venue details beyond menus.