GraphHopper MCP integration for AI agents.
Connect AI agents to GraphHopper through 5 structured actions, including list profiles, calculate route, and compute isochrone. Review authentication, inputs…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the GraphHopper integration exposes
The GraphHopper Agent App exposes 5 provider-backed actions for location and developer tools work. Its current contract lets an authorized agent list custom routing profiles available to the graphhopper api key, calculate the best route connecting two or more coordinates with the graphhopper routing api, and compute geojson isochrone polygons around a coordinate with the graphhopper isochrone api. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected GraphHopper account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real GraphHopper capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
list_profilesREADList custom routing profiles available to the GraphHopper API key.
calculate_routeREVIEWCalculate the best route connecting two or more coordinates with the GraphHopper Routing API.
INPUTS: point / profile / locale / pointHint / snapPrevention
compute_isochroneREVIEWCompute GeoJSON isochrone polygons around a coordinate with the GraphHopper Isochrone API.
INPUTS: point / profile / timeLimit / distanceLimit / buckets
compute_matrixREVIEWCompute a synchronous travel time, distance, or weight matrix with the GraphHopper Matrix API.
INPUTS: point / fromPoint / toPoint / profile / pointHint
geocodeREVIEWConvert text to coordinates or coordinates to place candidates with the GraphHopper Geocoding API.
INPUTS: q / point / reverse / locale / limit
INPUT CONTRACTS
Know what the action needs before it runs.
calculate_route
pointREQUIRED- Route waypoints in `latitude,longitude` format.
profileOPTIONAL- The GraphHopper routing profile, such as `car`, `bike`, `foot`, or a custom profile id.
localeOPTIONAL- The locale for turn instructions, such as `en`, `de`, or `fr`.
pointHintOPTIONAL- Optional road name hints for snapping each route waypoint.
snapPreventionOPTIONAL- Road types that should be avoided while snapping input points.
compute_isochrone
pointREQUIRED- A coordinate string in `latitude,longitude` format.
profileOPTIONAL- The GraphHopper routing profile, such as `car`, `bike`, `foot`, or a custom profile id.
timeLimitOPTIONAL- The travel time limit in seconds.
distanceLimitOPTIONAL- The travel distance limit in meters.
bucketsOPTIONAL- The number of nested isochrone buckets to return.
compute_matrix
pointOPTIONAL- Points in `latitude,longitude` format used as both origins and destinations.
fromPointOPTIONAL- Origin points in `latitude,longitude` format.
toPointOPTIONAL- Destination points in `latitude,longitude` format.
profileOPTIONAL- The GraphHopper routing profile, such as `car`, `bike`, `foot`, or a custom profile id.
pointHintOPTIONAL- Hints for point entries.
geocode
qOPTIONAL- The textual address or place query for forward geocoding.
pointOPTIONAL- The `latitude,longitude` location bias for forward geocoding or target coordinate for reverse geocoding.
reverseOPTIONAL- Whether to perform reverse geocoding. When true, point is required and q must be omitted.
localeOPTIONAL- The locale used for localized geocoding results.
limitOPTIONAL- The maximum number of geocoding results to return.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect List Profiles
List custom routing profiles available to the GraphHopper API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
list_profilesVerify with Calculate Route
Calculate the best route connecting two or more coordinates with the GraphHopper Routing API. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
calculate_routeSAFETY BOUNDARY
Operate GraphHopper with explicit limits
- Authorize GraphHopper with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned GraphHopper data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in GraphHopper rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the GraphHopper task completed successfully.
CONNECTION MODEL
API key
GraphHopper API key sent as the key query parameter. Create or manage API keys in the GraphHopper dashboard: https://www.graphhopper.com/dashboard/.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 1
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 4
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by GraphHopper.