HERE MCP integration for AI agents.
Connect AI agents to HERE through 6 structured actions, including lookup, autocomplete, and autosuggest. Review authentication, inputs, workflows, and safety…
- ACTION CONTRACTS
- 6
- 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 HERE integration exposes
The HERE Agent App exposes 6 provider-backed actions for location and data work. Its current contract lets an authorized agent look up a here place or location object by an identifier returned from another here search result, get here address and administrative-area completions for entered text, and get here query and entity suggestions for incomplete or misspelled address and place text with required spatial context. 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 HERE account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real HERE capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
lookupREADLook up a HERE place or location object by an identifier returned from another HERE search result.
INPUTS: id / lang / show
autocompleteREVIEWGet HERE address and administrative-area completions for entered text.
INPUTS: q / at / in / lang / limit
autosuggestREVIEWGet HERE query and entity suggestions for incomplete or misspelled address and place text with required spatial context.
INPUTS: q / at / in / lang / limit
discoverREVIEWSearch HERE places or addresses with a free-form Discover query and required spatial context.
INPUTS: q / at / in / lang / limit
geocodeREVIEWGeocode a free-form address, place, locality, or administrative-area query with HERE Geocoding and Search API v7.
INPUTS: q / lang / limit / in / at
reverse_geocodeREVIEWFind the nearest HERE address or place result for a latitude,longitude location.
INPUTS: at / lang / limit / types / politicalView
INPUT CONTRACTS
Know what the action needs before it runs.
lookup
idREQUIRED- The HERE result identifier returned by geocode, reverse geocode, discover, or autocomplete.
langOPTIONAL- The optional BCP 47 language tag for the response.
showOPTIONAL- The optional comma-separated HERE response enrichment selector.
autocomplete
qREQUIRED- The partial address or administrative-area text to complete.
atOPTIONAL- The optional HERE location context formatted as latitude,longitude.
inOPTIONAL- The optional HERE spatial or country filter, such as countryCode:USA.
langOPTIONAL- The optional BCP 47 language tag for the response.
limitOPTIONAL- The maximum number of autocomplete result items to return.
autosuggest
qREQUIRED- The partial HERE Autosuggest query.
atOPTIONAL- The optional HERE location context formatted as latitude,longitude.
inOPTIONAL- The optional HERE filter. Use circle:... or bbox:... as spatial context, or countryCode:... together with at.
langOPTIONAL- The optional BCP 47 language tag for the response.
limitOPTIONAL- The maximum number of result items to return.
discover
qREQUIRED- The free-form HERE Discover query.
atOPTIONAL- The optional HERE location context formatted as latitude,longitude.
inOPTIONAL- The optional HERE filter. Use circle:... or bbox:... as spatial context, or countryCode:... together with at.
langOPTIONAL- The optional BCP 47 language tag for the response.
limitOPTIONAL- The maximum number of result items to return.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Lookup
Look up a HERE place or location object by an identifier returned from another HERE search result. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
lookupVerify with Autocomplete
Get HERE address and administrative-area completions for entered text. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
autocompleteSAFETY BOUNDARY
Operate HERE with explicit limits
- Authorize HERE with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned HERE 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 HERE rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the HERE task completed successfully.
CONNECTION MODEL
API key
HERE API key sent as the apiKey query parameter. Create it in HERE Platform Access Manager on an app's Credentials tab: https://platform.here.com/.
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
- 5
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 HERE.