On va où ? Routing API

app.onvaouPublished by onvaou.appv0.2.0Updated Oct 24, 2026

Address geocoding and bike, scooter, motorcycle, wheelchair and walking routes across Europe.

VerifiedSTDIODesktop onlyLocation & Lifestyle

Overview

AI-generated overview

Lets an assistant geocode European addresses and compute bike, scooter, motorcycle, wheelchair and walking routes with detailed surface and climb data.

What you can do
The server exposes two read-only tools. geocode_address turns an address, place name, station or point of interest into longitude/latitude candidates, ranked best first, each with a label, type and confidence score, with optional bias by nearby point, country, result limit and language. compute_route takes an origin, a destination, up to eight waypoints, a travel mode, route variants and avoidance options, and returns up to three routes (safe, balanced, fast) with cycle-lane share, unpaved surfaces, main roads, motorways, climb and turn-by-turn steps. Both tools return a short readable summary followed by the same data as JSON, and report quota usage.
When to use it
Useful when an assistant needs European place lookup or non-car route planning: cycling, e-bike, kick scooter, motorcycle, wheelchair or walking itineraries, including comparisons of route variants and their surface and elevation characteristics. It is a fit for travel, mobility and accessibility questions where coordinates and route details matter rather than driving directions.
Requirements
Runs locally over stdio, typically started with npx from the npm package onvaou-itineraires-mcp, so Node.js is needed. A free API key is required in the environment variable OVO_API_KEY; an optional OVO_API_URL overrides the default production API base URL. Network access to the routing API is required. Coverage is limited to Europe.
Before you install
The API key OVO_API_KEY is a secret and must be supplied through the environment, not committed to configuration files that are shared. The free tier is limited to 10,000 requests per month, with a separate daily allowance for searches; the tools report usage but do not enforce it for you. Results come from third-party sources (Photon/OpenStreetMap and IGN Géoplateforme), and each answer carries an attribution string that must be displayed next to any route or result shown. Both tools are…

Installation

In SourceWeft

  1. Open On va où ? Routing API in the dashboard and add it to a workspace.
  2. 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

« On va où ? » Routing API: MCP server

Address geocoding, and bike, e-bike, kick scooter, motorcycle, wheelchair and walking routes across Europe, for AI assistants. One request turns a place name into coordinates; the next returns up to three routes (safe, balanced, fast) with what each one is worth: share of cycle lanes, unpaved surfaces, main roads and motorways, climb, and turn-by-turn steps.

Setup

  1. Create a free API key at https://console.onvaou.app (10,000 requests per month, no credit card).
  2. Add the server to your MCP client, for example Claude Desktop (claude_desktop_config.json):
json
{  "mcpServers": {    "onvaou-itineraires": {      "command": "npx",      "args": ["-y", "onvaou-itineraires-mcp"],      "env": { "OVO_API_KEY": "ovo_live_..." }    }  }}

Claude Code, same key, one line:

bash
claude mcp add -e OVO_API_KEY=ovo_live_... onvaou-itineraires -- npx -y onvaou-itineraires-mcp

Both tools come with the server: ask for "a safe bike route from Gare de Rennes to the Thabor park" and the assistant geocodes the two names, then routes between the coordinates it got back.

Tools

geocode_address: turns an address, a place name, a station or a point of interest (query, 2 to 200 characters) into longitude/latitude candidates, best first, each with a full label, its type and a confidence score. type is one of address (a house number), street, locality (town, district), region, country, venue (a named place: station, hotel, monument) or other, and nothing else. Narrow the search with near (bias the ranking around a point, which must itself be inside the European coverage), country (ISO 3166-1 alpha-2), limit (1 to 5) and language (en, fr, de, it; en by default, any other value refused). it is accepted, but the geocoder does not label in Italian: the labels then come back in the local language of each place (Milano, München). Results come from Photon (OpenStreetMap) across Europe, and from the IGN Géoplateforme in France, which hands over to Photon when it is unavailable, returns nothing, or its best confidence is below 0.4; source says which one answered. Its coordinates go straight into compute_route. Searches have their own daily allowance and never count towards the monthly routing quota, so a lookup before a route is free.

compute_route: origin and destination ({ "lon": 2.3522, "lat": 48.8566 }), up to 8 waypoints, mode (bike, ebike, scooter, moto, wheelchair, foot), variants, avoid (ferries, steps, tolls, highways, unpaved, steep), instruction language (en, fr, de, es, it, nl, pt), and whether to include steps, the encoded polyline and the elevation profile. Give it coordinates: when you only have a place name, call geocode_address first.

Both tools are read-only, answer with a short readable summary first, then the same data as JSON, and report what the call cost: searches used today for the geocoder, requests used this month for the router. Coverage: Europe. Each answer carries its own attribution string, and the search also says which source served it: display that attribution next to any route or result you show.

Documentation: https://onvaou.app/developers/routing-api.html Code examples: https://github.com/onvaou-app/routing-api-examples

Development

bash
npm installnpm test   # 11 tests, including a real MCP client over stdio against a mock API

License: MIT, © 2026 OVO SAS. Terms of the API: https://onvaou.app/cgv-api

Source: README.md at commit 3238016

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

3
  1. v0.2.0LatestSep 23, 2026
  2. v0.1.1Sep 22, 2026
  3. v0.1.0Sep 21, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts