Bicycle routes generator MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MTB_ENGINE | No | Routing engine to use: brouter or ors. | brouter |
| MTB_CONTACT | Yes | Email or URL sent in the User-Agent. Recommended: required by Nominatim's policy. | |
| MTB_GPX_DIR | No | Folder where GPX files are saved. The app only writes here (and to its .mtb-routes/ subfolder with cache and index). On Windows the default is the system temp folder. | /tmp/mtb-routes |
| ORS_API_KEY | No | Free OpenRouteService key if MTB_ENGINE=ors. | |
| MTB_DATA_DIR | No | Where to keep the cache and index. Default: <GPX folder>/.mtb-routes. | |
| MTB_BROUTER_URL | No | BRouter server (public or local). | https://brouter.de |
| MTB_PROTECTED_AREAS | No | Check protected areas with the Overpass API. | 1 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_routeA | Generate an MTB or road cycling route on real trails/roads, save it as GPX and return the summary and warnings. Takes 10 to 60 seconds (it evaluates several candidates and picks the best one). |
| list_routesA | List the saved GPX routes (most recent first) with their summary. |
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
generate_route and list_routes have clearly distinct purposes: one creates and saves a route, the other lists already saved routes. There is no overlap or ambiguity between them.
Both tools follow a clean verb_noun snake_case pattern: generate_route and list_routes. The convention is consistent and predictable.
Two tools is thin for a route generator that also manages saved GPX files. The surface is borderline minimal, though not an extreme mismatch for a narrow purpose.
The server covers generation and listing but lacks obvious lifecycle operations such as getting a saved route's details or deleting a saved route. These are notable gaps that could limit agent workflows.