Skip to main content
Glama
onvaou-app

onvaou-itineraires-mcp

Official
README.md
# « On va où ? » Routing API: MCP server

Bike, e-bike, kick scooter, motorcycle, wheelchair and walking routes across
Europe, for AI assistants. One request 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_..." }
    }
  }
}
```

## Tool

`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.

Coverage: Europe. Map data © OpenStreetMap contributors: display the returned
attribution next to any route you show.

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

## Development

```bash
npm install
npm test   # 4 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

TDQS

A3.9/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no ambiguity; the tool's purpose is clearly defined and distinct from any potential peers.

Naming Consistency5/5

The single tool name 'compute_route' follows a clear verb_noun pattern and is descriptive, though there are no other tools to compare against.

Tool Count2/5

A single tool feels insufficient for a routing service, especially since the description references geocoding as a prerequisite, which is not provided. A typical server would include at least geocoding and route management tools.

Completeness2/5

The server only covers route computation, but the workflow implies a need for geocoding (to get coordinates) and possibly route saving or sharing, which are absent. This creates a significant dead-end for agents.