Google Routes MCP integration for AI agents.
Connect AI agents to Google Routes through 2 structured actions, including compute route matrix and compute routes. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 2
- 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 Google Routes integration exposes
The Google Routes Agent App exposes 2 provider-backed actions for location and developer tools work. Its current contract lets an authorized agent compute route matrix elements for origin and destination waypoint combinations with google routes and compute one or more routes between an origin and destination with google routes. 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 Google Routes account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Google Routes capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
compute_route_matrixREVIEWCompute route matrix elements for origin and destination waypoint combinations with Google Routes.
INPUTS: fieldMask / origins / destinations
compute_routesREVIEWCompute one or more routes between an origin and destination with Google Routes.
INPUTS: fieldMask / origin / destination
INPUT CONTRACTS
Know what the action needs before it runs.
compute_route_matrix
fieldMaskREQUIRED- The response field mask sent as the `X-Goog-FieldMask` header.
originsREQUIRED- The route matrix origin route matrix waypoints.
destinationsREQUIRED- The route matrix destination route matrix waypoints.
compute_routes
fieldMaskREQUIRED- The response field mask sent as the `X-Goog-FieldMask` header.
originREQUIRED- The route origin waypoint.
destinationREQUIRED- The route destination waypoint.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Compute Route Matrix
Compute route matrix elements for origin and destination waypoint combinations with Google Routes. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
compute_route_matrixVerify with Compute Routes
Compute one or more routes between an origin and destination with Google Routes. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
compute_routesSAFETY BOUNDARY
Operate Google Routes with explicit limits
- Authorize Google Routes with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Google Routes 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 Google Routes rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Google Routes task completed successfully.
CONNECTION MODEL
API key
Google Maps Platform API key sent with the X-Goog-Api-Key header. Create or manage it in the Google Cloud Console: https://developers.google.com/maps/documentation/routes/get-api-key
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
- 0
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 2
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 Google Routes.