Integration

Geokeo integration

Geokeo is a geocoding API: turn a place name or address into coordinates and a structured address (forward geocoding), or turn latitude and longitude into the nearest places and their addresses (reverse geocoding). Results carry address components, a formatted postal-style address, the centroid and bounding box in WGS 84, and an OpenStreetMap link. Requests that fail still answer with a status value (INVALID_REQUEST, ACCESS_DENIED, OVER_QUERY_LIMIT, ZERO_RESULTS) instead of ok, so check it. The XML output format is not exposed. Authentication is an API key from the Geokeo dashboard, sent as the api query parameter; the free plan allows 2,500 requests per day, reset at midnight UTC, and a query with zero results is not charged.

Connect Geokeo How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Geokeo.Built from the 2 Geokeo tools below, on the connection you add once.

What you can do with Geokeo

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

forward_geocodeForward geocodeGETFinds places matching a text query (max 50 characters): returns results with address_components, formatted_address and geometry.location lat/lng (strings). Check status: ok, or ZERO_RESULTS, INVALID_REQUEST, OVER_QUERY_LIMIT.
reverse_geocodeReverse geocodeGETFinds the places at a latitude/longitude: returns results with address_components, formatted_address, geometry and distance from the point. Check status: ok, or ZERO_RESULTS, INVALID_REQUEST, OVER_QUERY_LIMIT.

Use Geokeo from Claude Code, Cursor or Codex

Connect Geokeo in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Geokeo operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Geokeo

Create your workspace
Sign up free. Nothing to install.
Connect Geokeo once
Add your Geokeo connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.