
Openrouteservice Mcp
io.github.mrfentmenv1.0.0Updated Oct 1, 2026
Query OpenRouteService: geocode, reverse geocode, driving directions.
Overview
AI-generated overview
Lets an assistant geocode places, reverse geocode coordinates, and get driving directions through OpenRouteService.
- What it does
- This local MCP server exposes OpenRouteService capabilities to an assistant. Based on its description, it supports geocoding (turning place names into coordinates), reverse geocoding (turning coordinates into addresses), and driving directions between locations. It runs as a local process over stdio.
- When to use it
- Useful when an assistant needs to resolve place names to coordinates, look up an address from a location, or plan a driving route as part of a task. It fits location-aware workflows that need geocoding or routing data.
- Requirements
- Runs as a local process on the user's machine, installed from the npm package openrouteservice-mcp, so Node.js is required. The manifest declares no authentication, environment variables, or headers, but OpenRouteService typically requires an API key; confirm how credentials are supplied before installing.
Before you install
The manifest declares no authentication or environment variables, yet OpenRouteService normally needs an API key, so verify how the key is provided and where it is stored. Queries such as addresses and coordinates are sent to OpenRouteService, a third-party service, so consider the privacy of the locations you submit.
Installation
In SourceWeft
- Open Openrouteservice Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestOct 1, 2026

