Geokeo MCP integration for AI agents.
Connect AI agents to Geokeo through 2 structured actions, including geocode forward and geocode reverse. Review authentication, inputs, workflows, and safety…
- 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 Geokeo integration exposes
The Geokeo Agent App exposes 2 provider-backed actions for location and data work. Its current contract lets an authorized agent convert an address or place query into geokeo geocoding results and convert coordinates into geokeo reverse geocoding results. 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 Geokeo account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Geokeo capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
geocode_forwardREVIEWConvert an address or place query into Geokeo geocoding results.
INPUTS: q / country
geocode_reverseREVIEWConvert coordinates into Geokeo reverse geocoding results.
INPUTS: lat / lng
INPUT CONTRACTS
Know what the action needs before it runs.
geocode_forward
qREQUIRED- Address or place query string to geocode.
countryOPTIONAL- Optional ISO 3166-1 alpha-2 country code used to narrow the search.
geocode_reverse
latREQUIRED- Latitude to reverse geocode.
lngREQUIRED- Longitude to reverse geocode.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Geocode Forward
Convert an address or place query into Geokeo geocoding results. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
geocode_forwardVerify with Geocode Reverse
Convert coordinates into Geokeo reverse geocoding results. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
geocode_reverseSAFETY BOUNDARY
Operate Geokeo with explicit limits
- Authorize Geokeo with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Geokeo 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 Geokeo rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Geokeo task completed successfully.
CONNECTION MODEL
API key
Geokeo API key sent as the api query parameter. Sign in at https://geokeo.com/login.php, then open Dashboard -> API to copy the 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 Geokeo.