openroute-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port to run the server on (default: 8888 if using HTTP transport) | |
| DATA_FOLDER | No | Folder to save generated routes | |
| OPENROUTE_API | No | OpenRouteService API URL (default: https://api.openrouteservice.org) | https://api.openrouteservice.org |
| OPENROUTESERVICE_API_KEY | Yes | API key for OpenRouteService, obtained from https://openrouteservice.org/ |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_location_coordinatesA | Search for possible coordinates of a location. Args: location: Location string (address or place name) Returns: List of location results with coordinates, address, and metadata. |
| get_coordinates_objectC | Returns the next enclosing objects with an address tag which surrounds the given coordinate. Args: lon: Longitude of the location lat: Latitude of the location Returns: List of objects results close to the given coordinates |
| create_route_from_toA | Create a route from a starting location coordinates to a destination, optionally with waypoints. Args: route_type: Type of route, e.g. "driving-car", "cycling-mountain", "cycling-regular", "foot-hiking" from_coordinates: Starting location as [longitude, latitude] to_coordinates: Destination location as [longitude, latitude] waypoints: optional list of waypoints coordinates as [[lon, lat], ...] Returns: GPX representation of the route |
| search_poisB | Search for points of interest (POIs) in an area. Args: bounding_box_coordinates: coordinates defining a bounding box as [[min_lon, min_lat], [max_lon, max_lat]] filters_name: optional explictly mentioned list of names to filter POIs, e.g. ["Gas station", "Restaurant"] Returns: Found POIs information |
| search_known_routesA | Search for known hiking/cycling routes close to a given start and end coordinates, this enables to suggest waypoints to go through known trails when creating a route. Currently only works for Switzerland using Swiss Geo API. Args: route_type: Type of route, e.g. "driving-car", "cycling-mountain", "cycling-regular", "foot-hiking" from_coordinates: Starting location as [longitude, latitude] to_coordinates: Destination location as [longitude, latitude] Returns: Description of known routes close to the given coordinates |
| get_reachable_areaA | Computes the area that can be reached within a given time or distance from one or more starting points. Args:
coordinates_list: 1 or more coordinates to compute reachable area from as [[lon, lat], ...]
route_type: Type of route, e.g. "cycling-mountain", "cycling-regular", "foot-hiking", "driving-car"
range_type: Type of range, either Returns: Reachable area information in GeoJSON format |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| scenic_hiking_route | Prompt to create a scenic hiking route. |
| scenic_biking_route | Prompt to create a scenic mountain biking route. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: route creation, reverse geocoding, isochrone analysis, known route discovery, forward geocoding, and POI search. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (create_route_from_to, get_coordinates_object, get_reachable_area, search_known_routes, search_location_coordinates, search_pois) using snake_case. The pattern is uniform and predictable.
With 6 tools, the server is well-scoped for a routing and location utility. Each tool addresses a fundamental need without unnecessary redundancy or excessive features.
The tool set covers core routing, geocoding, reverse geocoding, isochrones, and POI search. Minor gaps exist, such as lack of distance matrix or turn-by-turn directions, but overall it provides a solid base for location-based tasks.