On va où ? Routing API vs Openrouteservice
A side-by-side look at the On va où ? Routing API and Openrouteservice MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose On va où ? Routing API for location services work as a local process; choose Openrouteservice for location services as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose On va où ? Routing API when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OVO_API_KEY.
Choose Openrouteservice when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLATFORM_ORS_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Location Services | Location Services |
| Quality signal | 44/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | OVO_API_KEY | PLATFORM_ORS_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View On va où ? Routing API | View Openrouteservice |
Tools & capabilities
On va où ? Routing API tools
No tool names declared yet. Check the project README from the listing page.
Openrouteservice tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
On va où ? Routing API
{
"mcpServers": {
"on-va-o-routing-api-2": {
"command": "npx",
"args": [
"-y",
"onvaou-itineraires-mcp"
],
"env": {
"OVO_API_KEY": "YOUR_OVO_API_KEY_HERE"
}
}
}
}
Openrouteservice
{
"mcpServers": {
"openrouteservice": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-openrouteservice"
],
"env": {
"PLATFORM_ORS_KEY": "YOUR_PLATFORM_ORS_KEY_HERE"
}
}
}
}
Frequently asked questions
On va où ? Routing API is categorized under Location Services and uses a local stdio subprocess. Openrouteservice belongs to Location Services and uses a local stdio subprocess. Pick On va où ? Routing API for location services work and Openrouteservice for location services.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
On va où ? Routing API has no declared pricing — check the project's own site. Openrouteservice has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add on-va-o-routing-api-2 and openrouteservice as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, On va où ? Routing API has a quality signal of 44/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Openrouteservice has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.