# JustRouting MCP Server [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/justrouting/mcp  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/justrouting-mcp-server

## Description
Road routing, travel-time matrices, geocoding, and fleet optimization for Southeast Asia.

## Tools
Capabilities this server exposes over MCP:

- **geocode** — Place or address → coordinates
- **route** — Calculate one route
- **table** — Compare travel times or distances between multiple locations
- **optimize** — Assign jobs to vehicles and order their stops

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "justrouting-mcp-server": {
    "url": "https://raw.githubusercontent.com/justrouting/mcp/main/install.sh"
  }
}
```

## Documentation

## What JustRouting MCP Server MCP server does

JustRouting MCP Server MCP server exposes four separate tools for location and fleet workflows focused on Southeast Asia. `geocode` converts a place, landmark, business, or address into coordinates. Returned results include formatted location details, identifiers, country codes, result types, and a longitude-latitude coordinate string that can be passed to the other tools.

`route` calculates one driving route between two locations. Its response can include distance, estimated duration, snapped endpoints, simplified encoded geometry, main roads, toll information, and ferry information. The tool also supports an explicit motorcycle profile and road exclusions for toll roads, motorways, and ferries when a suitable alternative exists.

`table` produces distance and travel-time matrices for multiple coordinates. It can compare all supplied locations or restrict calculations to selected source and destination indexes. `optimize` assigns jobs to vehicles and orders their stops for multi-vehicle routing workflows.

## How it works

The server uses MCP tool calls to send requests to JustRouting. Coordinates use `longitude,latitude` order. If a user supplies names or addresses, an agent should call `geocode` first, check the selected result, and then pass its coordinates to `route`, `table`, or `optimize`.

Use `route` for one origin-destination calculation, not for matrix comparisons. Use `table` when comparing several destinations, finding a nearby driver or facility, or constructing origin-destination travel data. Matrix rows represent sources and columns represent destinations, while returned indexes identify the original coordinate positions. Matrix annotations can request durations, distances, or both.

The JustRouting MCP Server MCP server is intended for MCP-compatible assistants, including Claude and Cursor. It communicates through standard input and output rather than a network listener.

## Setup and configuration

On macOS or Linux, the provided installer downloads a prebuilt binary and installs `justrouting-mcp`; Go is not required for that method. The repository also supports installation from source with `go install github.com/justrouting/mcp/cmd/justrouting-mcp@latest`. The executable must be available in `PATH`.

A JustRouting API key is required. Set it as `JUSTROUTING_API_KEY`, or provide it in the MCP client's environment configuration. A stdio configuration uses `justrouting-mcp` as the command and passes the key through the server's `env` block.

## Tools and capabilities

- `geocode`: Search place and address details, with optional result limits and filters.
- `route`: Calculate a driving route, estimated duration, distance, geometry, and route-road details.
- `table`: Compare travel times or distances across multiple locations, with optional source and destination subsets.
- `optimize`: Assign jobs to vehicles and arrange their stops.
- Road preferences: Request motorcycle routing or exclude toll, motorway, or ferry road types for a route.

## Limitations and notes

The service is designed for Southeast Asia, so suitability for locations outside that focus is not established by the provided material. Road exclusions are preferences rather than guarantees. A route may still use an excluded road type when no reasonable alternative exists.

Geocoding returns a best match by default, and multiple results can be requested up to 10. Agents should not invent missing address fields and should verify ambiguous results before routing. Coordinates must be supplied in longitude-latitude order.

The `table` response can contain null matrix values when a source-destination route is unavailable. The tool should not replace `route` for a single pair of locations. The JustRouting MCP Server MCP server also requires a JustRouting API key and an MCP client that supports stdio.

_Full upstream README: https://allmcps.com/mcp/justrouting-mcp-server/readme_