A route that ignores a 4m height limit or an ADR restriction is not a slightly worse route, it is an unusable one — and that is what separates this from asking a general mapping API. Getting the cost breakdown, the blackspots and the parking off the same planned route means the follow-up questions don't need the route recomputed.
A Python server that puts six TRANSCEND logistics services behind one interface: Route, Tolls, Weather, POI, Traffic and Stations. It exists because truck route planning is fragmented — general mapping doesn't know about height restrictions, toll calculators are per country, and fuel prices live somewhere else again.
- 12 tools across the six modules
- Route: `calculate_route` plans with ADR dangerous-goods class, height, width and weight constraints
- Tolls: `calculate_route_costs` returns fuel, tolls, maintenance and CO₂ for a route
- Weather: `get_current_weather`, `get_weather_forecast` for a date range, `get_weather_alerts` for active warnings
- Parking: `find_parking_by_location` by coordinates and radius, plus `find_parking_by_zipcode` and `find_parking_by_province`
- Traffic: `get_blackspots_path` returns dangerous zones along a planned route
- Fuel: `find_stations_nearby`, `search_stations` filtered by fuel type or text, `get_station_best_prices`
- Inputs and outputs are validated with pydantic
A TRANSCEND account — register at `transcend.cargoffer.com` and take the API key from your profile settings, then set `TRANSCEND_API_KEY`. Python 3.10 or newer. Clone the repository and `pip install -e .`, then run `python -m transcend_mcp`, which defaults to stdio; set `MCP_HOST` and `MCP_PORT` to run HTTP/SSE instead, with the SSE endpoint on port 8100 by default. `TRANSCEND_ENV` selects production or release-dev, and `LOG_LEVEL` sets verbosity.
One command plus a key — ..., then supply credentials