Integration

OpenCage Geocoding integration

OpenCage turns addresses and place names into coordinates (forward geocoding) and coordinates into an address (reverse geocoding), worldwide, from open data such as OpenStreetMap. Each result carries a formatted address, its normalized components (road, postcode, city, state, country...), a confidence score, a bounding box and, unless turned off, annotations such as timezone, currency, calling code, sun rise and set times, geohash and OpenStreetMap links. Results come as plain JSON or as GeoJSON. The XML format and the keyless ping route are not exposed. Results may be stored without time limit; the underlying data (mainly OpenStreetMap, ODbL) requires attribution when results are published. Authentication is an OpenCage API key sent as the `key` query parameter; free trial accounts are limited to 2,500 requests a day and one request per second.

Connect OpenCage Geocoding How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with OpenCage Geocoding

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.

geocodeGeocodeGETGeocodes an address or place name to coordinates, or reverse geocodes latitude,longitude to an address; pass it in q. Answers results (formatted, components, geometry lat/lng, confidence, annotations) and total_results.
geocode_geojsonGeocode geojsonGETSame geocoding as geocode (address to coordinates, or latitude,longitude in q to an address) but answers a GeoJSON FeatureCollection: features with Point geometry [lng, lat] and properties (formatted, components, annotations).

Use OpenCage Geocoding from Claude Code, Cursor or Codex

Connect OpenCage Geocoding in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its OpenCage Geocoding 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 OpenCage Geocoding

Create your workspace
Sign up free. Nothing to install.
Connect OpenCage Geocoding once
Add your OpenCage Geocoding 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.