Log inSubmit server
Openrouteservice logo

Openrouteservice

MCP tools for Openrouteservice directions, matrices, isochrones, elevation, snapping, and geocoding.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Openrouteservice

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "openrouteservice": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-openrouteservice"
      ],
      "env": {
        "PLATFORM_ORS_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The Openrouteservice MCP server exposes Openrouteservice routing and location APIs through MCP tools. It supports directions, distance and duration matrices, isochrones, snap-to-road, elevation, and Pelias geocoding, using either the Pipeworx gateway or a local stdio process. Reach for it when an agent needs route calculations, accessibility areas, road matching, elevation data, or place search. An Openrouteservice API key is required.

Use cases

  • Calculate driving, cycling, walking, hiking, or wheelchair routes
  • Build distance and duration matrices between locations
  • Find reachable areas within a travel range
  • Snap coordinates to nearby roads
  • Search places and retrieve elevation data

Key features

  • Directions with multiple travel profiles
  • Distance and duration matrices
  • Drive and walk isochrones
  • Snap-to-road matching
  • Point and line elevation
  • Pelias geocoding search

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

6/6 checks healthy over the last 40d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @pipeworx/mcp-openrouteservice (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads452Package downloads in the last 30 days.
Last commit27d agoMost recent push to the default branch.

How Openrouteservice works

What the Openrouteservice MCP server does

The Openrouteservice MCP server connects MCP-compatible agents to the Openrouteservice API at https://api.openrouteservice.org/v2/. It provides location and mobility operations without requiring the agent to construct the underlying HTTP requests. Supported use cases include route planning, travel-time analysis, reachable-area calculations, road matching, elevation lookup, and geocoding.

The package is available through the Pipeworx gateway or as a standalone local MCP process. The gateway endpoint also exposes shared Pipeworx tools, while the local process lists only the Openrouteservice tools.

How it works

An MCP client can connect to the hosted endpoint at https://gateway.pipeworx.io/openrouteservice/mcp. The gateway connection lists the pack's tools along with shared Pipeworx meta-tools. Its ask_pipeworx tool can route natural-language questions to tools across the wider catalog, including this pack.

The Openrouteservice MCP server can also run over standard input and output with npx -y @pipeworx/mcp-openrouteservice. In standalone mode, it responds to MCP initialization, tool-listing, and tool-call requests directly, without a Pipeworx account or gateway round trip. The same functions are also available through Pipeworx HTTP tool endpoints for clients that do not use MCP.

Setup and configuration

For the hosted connection, add the gateway URL as an MCP server in a compatible client. For local use, configure the client to run the package with npx and the -y flag.

The upstream service has a stated free allowance of 2,000 requests per day. The gateway and standalone modes use the same Openrouteservice-backed tool set, but their available surrounding tools differ.

Tools and capabilities

The Openrouteservice MCP server includes:

  • directions for routes, with selectable profiles, output format, and instructions.
  • matrix for distance and duration values between source and destination locations.
  • isochrones for driveable or walkable areas based on a range and range type.
  • snap for matching coordinates to nearby roads, with an optional search radius.
  • elevation_line for elevation values along a line.
  • elevation_point for elevation at a point.
  • geocode_search for Pelias text search, with optional source, layer, result-count, and geographic-focus parameters.

Supported profiles include driving, heavy-goods vehicles, several cycling modes, walking, hiking, and wheelchair travel. The default profile is driving-car.

Limitations and notes

The Openrouteservice MCP server requires an API key for Openrouteservice access. A gateway pack endpoint does not contain only these seven tools: shared Pipeworx meta-tools are included, and the exact tool set may change. Use the connection's initialize response as the authoritative scope for a particular session.

Connecting to the full Pipeworx gateway exposes all catalog packs directly, whereas the scoped endpoint lists this pack directly. In standalone mode, shared gateway tools such as cross-catalog routing are not available. The documented service allowance is 2,000 requests per day, so applications should account for that limit when issuing repeated requests.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Openrouteservice

Openrouteservice is an MCP server that connects AI agents to the Openrouteservice API for directions, distance and duration matrices, isochrones, snap-to-road matching, elevation queries, and Pelias geocoding. It can run through the Pipeworx gateway or locally over stdio, and requires an Openrouteservice API key.

Run it locally with `npx -y @pipeworx/mcp-openrouteservice` and configure your MCP client to start that command. You can instead add the hosted Pipeworx endpoint at `https://gateway.pipeworx.io/openrouteservice/mcp` as an MCP server.

It needs an Openrouteservice API key, configured through `PLATFORM_ORS_KEY` for the platform setup.

Yes. Cursor is listed as a supported MCP client in the setup documentation. You can connect it to the hosted gateway URL or configure it to launch the standalone package through `npx`.

It supports `driving-car`, `driving-hgv`, `cycling-regular`, `cycling-road`, `cycling-mountain`, `foot-walking`, `foot-hiking`, and `wheelchair`. `driving-car` is the default profile.

Related MCP servers

All in Location Services All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOpenrouteservice AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/openrouteservice?style=directory)](https://allmcps.com/mcp/openrouteservice)
HTML Embed
<a href="https://allmcps.com/mcp/openrouteservice"><img src="https://allmcps.com/api/badge/openrouteservice?style=directory" alt="Openrouteservice on AllMCPs" /></a>