ArcGIS Online MCP integration for AI agents.
Connect AI agents to ArcGIS Online through 3 structured actions, including find address candidates, reverse geocode, and suggest. Review authentication, inpu…
- ACTION CONTRACTS
- 3
- 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 ArcGIS Online integration exposes
The ArcGIS Online Agent App exposes 3 provider-backed actions for location and data work. Its current contract lets an authorized agent convert an address or place query into arcgis geocoding candidates, convert longitude and latitude into an arcgis address result, and return arcgis address and place autocomplete suggestions. 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 ArcGIS Online account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real ArcGIS Online capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
find_address_candidatesREADConvert an address or place query into ArcGIS geocoding candidates.
INPUTS: singleLine / location / searchExtent / category / sourceCountry
reverse_geocodeREVIEWConvert longitude and latitude into an ArcGIS address result.
INPUTS: longitude / latitude / outSr / langCode / forStorage
suggestREVIEWReturn ArcGIS address and place autocomplete suggestions.
INPUTS: text / location / searchExtent / category / sourceCountry
INPUT CONTRACTS
Know what the action needs before it runs.
find_address_candidates
singleLineREQUIRED- Street address, place name, postal code, or POI query.
locationOPTIONAL- A WGS84 coordinate used by ArcGIS geocoding.
searchExtentOPTIONAL- Bounding box that limits search results, formatted as xmin,ymin,xmax,ymax.
categoryOPTIONAL- Place or address category filter supported by ArcGIS.
sourceCountryOPTIONAL- Country code or comma-separated country codes used to restrict results.
reverse_geocode
longitudeREQUIRED- Longitude in decimal degrees.
latitudeREQUIRED- Latitude in decimal degrees.
outSrOPTIONAL- Spatial reference WKID for returned coordinates.
langCodeOPTIONAL- Language code for returned addresses.
forStorageOPTIONAL- Whether the reverse geocoding result will be stored persistently.
suggest
textREQUIRED- Input text to autocomplete.
locationOPTIONAL- A WGS84 coordinate used by ArcGIS geocoding.
searchExtentOPTIONAL- Bounding box that limits search results, formatted as xmin,ymin,xmax,ymax.
categoryOPTIONAL- Place or address category filter supported by ArcGIS.
sourceCountryOPTIONAL- Country code or comma-separated country codes used to restrict results.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Find Address Candidates
Convert an address or place query into ArcGIS geocoding candidates. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
find_address_candidatesVerify with Reverse Geocode
Convert longitude and latitude into an ArcGIS address result. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
reverse_geocodeSAFETY BOUNDARY
Operate ArcGIS Online with explicit limits
- Authorize ArcGIS Online with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned ArcGIS Online 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 ArcGIS Online rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the ArcGIS Online task completed successfully.
CONNECTION MODEL
API key
ArcGIS API key used as an access token for ArcGIS Location Services. Create API key credentials in your ArcGIS portal: https://developers.arcgis.com/documentation/security-and-authentication/api-key-authentication/tutorials/create-an-api-key/location-platform/.
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
- 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 ArcGIS Online.