Mapbox MCP integration for AI agents.
Connect AI agents to Mapbox through 5 structured actions, including get directions, batch geocode, and forward geocode. Review authentication, inputs, workfl…
- 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 Mapbox integration exposes
The Mapbox Agent App exposes 5 provider-backed actions for location and developer tools work. Its current contract lets an authorized agent compute a route between multiple coordinates with the mapbox directions api, submit multiple forward or reverse geocoding queries in one mapbox batch request, and convert free-form text into geographic features with mapbox geocoding v6. 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 Mapbox account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Mapbox capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_directionsREADCompute a route between multiple coordinates with the Mapbox Directions API.
INPUTS: profile / coordinates / alternatives / annotations / continue_straight
batch_geocodeREVIEWSubmit multiple forward or reverse geocoding queries in one Mapbox batch request.
INPUTS: queries
forward_geocodeREVIEWConvert free-form text into geographic features with Mapbox Geocoding v6.
INPUTS: q / autocomplete / limit / language / country
get_matrixREADCompute a travel time or distance matrix with the Mapbox Matrix API.
INPUTS: profile / coordinates / annotations / approaches / bearings
reverse_geocodeREVIEWConvert a coordinate pair into place features with Mapbox Geocoding v6.
INPUTS: longitude / latitude / limit / language / types
INPUT CONTRACTS
Know what the action needs before it runs.
get_directions
profileREQUIRED- Routing profile used by the request.
coordinatesREQUIRED- Route coordinates in travel order.
alternativesOPTIONAL- Whether to request alternative routes.
annotationsOPTIONAL- Route annotations to include in the response.
continue_straightOPTIONAL- Whether the router should prefer continuing straight at waypoints.
batch_geocode
queriesOPTIONAL- Batch geocoding queries submitted to Mapbox.
forward_geocode
qREQUIRED- The free-form text query to geocode.
autocompleteOPTIONAL- Whether Mapbox should return autocomplete-style results.
limitOPTIONAL- The maximum number of features to return.
languageOPTIONAL- The IETF language tag used for localized feature names.
countryOPTIONAL- Country filters applied to the geocoding request.
get_matrix
profileREQUIRED- Routing profile used by the request.
coordinatesREQUIRED- Coordinates included in the matrix calculation.
annotationsOPTIONAL- Matrix annotations to include in the response.
approachesOPTIONAL- Curb approach constraints for the coordinates.
bearingsOPTIONAL- Bearing filters applied to the coordinates.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Directions
Compute a route between multiple coordinates with the Mapbox Directions API. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_directionsVerify with Get Matrix
Compute a travel time or distance matrix with the Mapbox Matrix API. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_matrixSAFETY BOUNDARY
Operate Mapbox with explicit limits
- Authorize Mapbox with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Mapbox 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 Mapbox rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Mapbox task completed successfully.
CONNECTION MODEL
API key
Mapbox access token used with the access_token query parameter. Create or copy it from your Mapbox Access Tokens page: https://console.mapbox.com/account/access-tokens/.
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
- 2
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 3
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 Mapbox.