Geoapify MCP integration for AI agents.
Connect AI agents to Geoapify through 5 structured actions, including get route, address autocomplete, and forward geocode. Review authentication, inputs, wo…
- 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 Geoapify integration exposes
The Geoapify Agent App exposes 5 provider-backed actions for location and developer tools work. Its current contract lets an authorized agent calculate a route between waypoints with the geoapify routing api, return address autocomplete suggestions from geoapify, and convert free-form text into geocoding results with geoapify. 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 Geoapify account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Geoapify capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_routeREADCalculate a route between waypoints with the Geoapify Routing API.
INPUTS: waypoints / mode / type / units / lang
address_autocompleteREVIEWReturn address autocomplete suggestions from Geoapify.
INPUTS: text / lang / limit / type / filter
forward_geocodeREVIEWConvert free-form text into geocoding results with Geoapify.
INPUTS: text / lang / limit / type / filter
get_route_matrixREADCalculate a travel matrix between sources and targets with Geoapify.
INPUTS: sources / targets / mode / type / units
reverse_geocodeREVIEWConvert latitude and longitude into place results with Geoapify.
INPUTS: lat / lon / lang / limit / type
INPUT CONTRACTS
Know what the action needs before it runs.
get_route
waypointsREQUIRED- The ordered route waypoints as `[longitude, latitude]` pairs.
modeOPTIONAL- The Geoapify routing mode.
typeOPTIONAL- The Geoapify route preference.
unitsOPTIONAL- The distance unit system.
langOPTIONAL- The language for route instructions.
address_autocomplete
textREQUIRED- The free-form text query sent to Geoapify.
langOPTIONAL- The result language code in ISO 639-1 format.
limitOPTIONAL- The maximum number of results to return.
typeOPTIONAL- The Geoapify place type filter.
filterOPTIONAL- The Geoapify boundary or country filter expression.
forward_geocode
textREQUIRED- The free-form text query sent to Geoapify.
langOPTIONAL- The result language code in ISO 639-1 format.
limitOPTIONAL- The maximum number of results to return.
typeOPTIONAL- The Geoapify place type filter.
filterOPTIONAL- The Geoapify boundary or country filter expression.
get_route_matrix
sourcesREQUIRED- The source waypoints used for the route matrix.
targetsREQUIRED- The target waypoints used for the route matrix.
modeOPTIONAL- The Geoapify routing mode.
typeOPTIONAL- The Geoapify route preference.
unitsOPTIONAL- The distance unit system.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Route
Calculate a route between waypoints with the Geoapify Routing API. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_routeVerify with Get Route Matrix
Calculate a travel matrix between sources and targets with Geoapify. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_route_matrixSAFETY BOUNDARY
Operate Geoapify with explicit limits
- Authorize Geoapify with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Geoapify 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 Geoapify rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Geoapify task completed successfully.
CONNECTION MODEL
API key
Geoapify API key sent as the apiKey query parameter. Create it on the Geoapify MyProjects page: https://myprojects.geoapify.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
- 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 Geoapify.