create_route_from_toLABSCO SUMMARY
Planning a trail becomes a conversation instead of a map session.
Naming the start and the finish is enough — it resolves both to coordinates, threads in whatever waypoints you add along the way, and hands back a GPX file that opens straight into a map or a GPS device.
What it is
A route planner in front of the OpenRouteService API, aimed at hiking and mountain biking. You give it place names or coordinates; it returns the route as a GPX file you can open on a map.
What you get
- Ten candidate coordinate pairs for a place name, each with enough description to tell which one you meant
- The addresses and landmarks nearest a longitude and latitude, when you have numbers rather than a name
- A route from a start to a destination, with optional waypoints in between
- Four ways to travel: foot-hiking, cycling-mountain, cycling-regular and driving-car
- The route itself as a GPX resource, loadable in a map viewer such as gpx.studio
Requirements
Python, and network access — every answer is a live call to OpenRouteService. The author's own caution travels with the output: check any generated route against official maps and current conditions before you set out.
Setup effort
One command plus a key — uvx openroute-mcp, then supply credentials
USE CASES
Planning a day's hike between two places you can only name
Say where you are starting and where you want to end up. The place names are resolved to coordinates first — with candidates offered when the name is ambiguous — and the foot-hiking route comes back as a GPX file.
Building a ride that goes past somewhere in particular
Add the waypoints you actually care about — a col, a café, a viewpoint — and route between them on the mountain-biking or road-cycling profile rather than accepting whatever the shortest line does.
Working out where a set of coordinates actually is
Hand over a longitude and latitude from a photo, a GPS log or a shared pin, and read back the addresses and features closest to it.
Getting a planned route onto a device
The route comes back as a GPX resource rather than as directions in prose, so it goes to a watch, a bike computer or a map viewer without being retyped.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- uvx on PATH
- OPENROUTESERVICE_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
uvx openroute-mcpMCP Clients
VS Code
{
"servers": {
"openroute-mcp": {
"command": "uvx",
"args": [
"openroute-mcp"
],
"env": {
"OPENROUTESERVICE_API_KEY": "<YOUR_OPENROUTESERVICE_API_KEY>"
}
}
}
}