OpenCage Geocoder MCP for AI. Convert any location to lat/lon or vice versa.

Q: What is the difference between forwardgeocode and reversegeocode?

forwardgeocode takes text (like an address) and gives you coordinates. reversegeocode does the opposite: it takes coordinates and figures out the best matching street address.

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

How this MCP server connects to your AI agent

OpenCage Geocoder converts addresses to latitude/longitude coordinates and coordinates back to formatted street addresses worldwide. This server gives your AI client high-precision global geocoding and reverse geocoding using one reliable API.

It handles city names, landmarks, ZIP codes, and specific international formats across the globe.

What AI agents can do with OpenCage Geocoder Automation

Forward geocode

Converts a physical address or place name string into precise geographic latitude and longitude coordinates.

Reverse geocode

Takes known latitude and longitude coordinates and returns the full, formatted street address details for that point on Earth.

Convert Address Text to Coordinates

You pass a physical address or place name, and the server returns precise latitude and longitude values.

Convert Coordinates back to Address

The agent takes coordinates (lat/lon) and converts them into a structured, readable street address format.

Handle Multiple Languages

You request the results in specific languages or formats for your application's needs.

Retrieve Road Details

The server can optionally pull extra road info, like which nearest road matches a location.

Ask an AI about this

Included with Plan

Waiting for input…

AI Agent

What AI agents can do with OpenCage Geocoder: 2 Tools for Location Data

These tools allow your agent to convert between human-readable addresses and precise geographic coordinates globally.

Make your AI actually useful.

Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.

Start using OpenCage Geocoder on Vinkius

Forward Geocode

Converts a physical address or place name string into precise geographic latitude and longitude coordinates.

Reverse Geocode

Takes known latitude and longitude coordinates and returns the full, formatted...

Security and governance baked right in.

Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.

Claude AI

Open Claude Settings

Go to claude.ai, click your profile icon, then navigate to Customize → Connectors.

Add Custom Connector

Click the "+" button and select Add custom connector. Paste your Vinkius endpoint URL:

https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. For OAuth-protected servers, expand Advanced settings to add credentials.

Start a conversation

Open a new chat. The OpenCage Geocoder integration is available immediately — no restart needed.

Antigravity

Configure Agent Environment

Open your Antigravity agent's workspace configuration or mcp-servers.json file.

Bind the Endpoint

Add the Vinkius endpoint URL to your agent's MCP connections list:

"mcp_servers": {
  "opencage-geocoder": {
    "serverUrl": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
  }
}

Provide your secure token in place of [YOUR_TOKEN_HERE] to ensure your agent requests are authenticated.

Execute

Start your Antigravity session. The agent will autonomously discover and utilize the OpenCage Geocoder tools with full Vinkius guardrails applied.

VS Code Copilot

⚡

One-Click Install (Recommended)

In your Vinkius Dashboard, simply click the Add to VS Code button for this server. We'll automatically configure your local workspace.

Or configure manually

Open MCP Settings

Open VS Code, press Ctrl/Cmd + Shift + P, and search for GitHub Copilot: MCP Servers.

Add Server Config

Add the Vinkius endpoint configuration to your mcp-servers.json file:

"opencage-geocoder": {
  "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}

Ensure you replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.

LangChain

Install Dependencies

Install the LangChain MCP adapters for your environment:

pip install langchain-mcp-adapters

Connect the Server

Use the SSEClient in LangChain to connect to the Vinkius managed endpoint:

from langchain_mcp_adapters.client import SSEClient

# Connect to Vinkius
client = SSEClient(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
tools = client.get_tools()

CrewAI

Define the Tool

Load the Vinkius MCP tools into your CrewAI agents:

from crewai import Agent
from mcp_crewai import MCPTool

# Connect securely to Vinkius
vinkius_tools = MCPTool(url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")

# Assign to Agent
researcher = Agent(
    role='Data Researcher',
    tools=vinkius_tools.get_all()
)

Execute Task

Run your CrewAI process. The agent will autonomously route tasks to the Vinkius managed server.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

Import from OpenAPI, Swagger, or YAML specs
Create Agent Skills with progressive disclosure
Deploy to edge with MCPFusion framework
Built in DLP, auth, and compliance on every call
Real time usage dashboard and cost metering
Publish to catalog or keep private

Start building

Make Your AI Do More

Start with OpenCage Geocoder, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.

Use this MCP plus 5,100+ others, all in one place
Add new capabilities to your AI anytime you want
Every connection is secured and compliant automatically
Track usage and costs across all your servers
Works with Claude, ChatGPT, Cursor, and more
New servers added to the catalog every week

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by OpenCage Geocoder. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

Your data is protected. See how we built it.

Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This connection provides 2 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.

Manually converting addresses into map data is a huge pain point., Solved with Vinkius AI Gateway

Today, if you get an address from a form or spreadsheet, you usually have to run it through a third-party mapping tool. You copy the street name; you paste it in; you wait for the map widget to load; then you manually grab the latitude and longitude numbers—and hope they are accurate.

With this MCP server, your AI client handles that whole process in one step. You just ask: "What are the coordinates for X?" It runs `forward_geocode` and gives you the clean coordinate pair instantly, no copying or pasting involved.

OpenCage Geocoder MCP Server: Get structured data from addresses.

Without this tool, if your agent finds coordinates (lat/lon) in a database, you can't easily tell the end-user what street or city it is without another system call. You're stuck with raw numbers that mean nothing to a person.

Now, when the agent runs `reverse_geocode`, those cold lat/lon points pop back out as '123 Main Street, Anytown, USA.' The data structure goes from meaningless numbers to actionable text.

Support 24/7 support@vinkius.com ↗

Security Vinkius Trust Center ↗

SLA Service Level Agreement ↗

Report Listing Send Report ↗

geocoding

reverse-geocoding

maps

location-data

coordinates

What your AI can actually do with this

When you're dealing with location data, you gotta convert between addresses and coordinates constantly. The OpenCage Geocoder handles that whole round trip for your agent. This server gives your AI client the high-precision tools it needs to map anything globally.

How It Works

Your agent uses two primary functions: forward_geocode and reverse_geocode. You don't need to worry about the underlying API calls; you just tell your client what location data you have, and it handles the rest.

Using forward_geocode (Address to Coordinates)

When you pass in a physical address, place name, or landmark string, this tool spits out precise latitude and longitude numbers. It's reliable for everything: just a street corner, an entire city block, or even a specific ZIP code area. You can feed it anything from 'Times Square, New York' to 'The Eiffel Tower' and get coordinates back instantly.

What’s really useful is that you don't have to pick one format—it handles different international address standards globally. If you need extra detail, the tool can also grab specific road info; for instance, it tells you which nearest major road matches the location you provided.

Using reverse_geocode (Coordinates to Address)

If your agent only has coordinates—say, lat 34.0522 and lon -118.2437—this tool flips it around. It takes those raw numbers and turns them into a full, structured, readable street address. This isn't just random text; the output is formatted exactly like an actual mailing address, complete with necessary location metadata you need for databases or reports.

Global Scope and Flexibility

The coverage here is huge. It doesn't pull data from one place; it aggregates multiple open sources—think OpenStreetMap and other reliable global datasets—meaning it covers nearly every geographic region on the planet. You can specify exactly what language you want the results in, or what format your application needs, ensuring the output integrates smoothly into whatever system you’re running.

For instance, if you're processing international data, you might run forward_geocode with an address written in French, and the server gives you coordinates. Then, later on, when validating that point, you use reverse_geocode to ensure the resulting street address is also formatted correctly for a different language. It’s seamless because the underlying mechanism handles the linguistic complexity.

Don't try building this yourself with multiple APIs; it'll be a nightmare of keys and formatting rules. This server consolidates all that complex geocoding logic into one reliable, straightforward toolset. You just call forward_geocode or reverse_geocode, and you get clean, structured data back every time.

Built · Hosted · Managed by Vinkius OpenCage Geocoder MCP Server - Convert Addresses & Coordinates

Server ID 019e5d40-135e-7379-bc8a-d9209fce50a0

Vinkius Inspector

Compliance Grade F

Score 3.6/100

Report View Report ↗

Here's how it actually works

The bottom line is that it lets your AI client talk to global mapping data without you having to manage a complex database yourself.

First, you subscribe to the OpenCage Geocoder and supply your personal API Key to the MCP.

Next, you ask your agent for a specific lookup—either an address-to-coordinate job or coordinates-to-address job.

The server runs the relevant function (like forward_geocode) and returns structured JSON containing the required latitude, longitude, and formatted text.

Who is this actually for?

This tool serves developers who deal with location-based services and data analysts cleaning messy datasets. It's for anyone whose core task involves connecting text inputs (like customer mailing addresses) to precise map coordinates, or vice versa. If your app needs reliable geo-data, this is it.

Data Analyst

Uses the server to clean and enrich large datasets by converting raw address strings into standardized latitude/longitude pairs.

Backend Developer

Integrates location lookups into core application logic, using forward_geocode to validate user-submitted addresses before running a delivery route.

Logistics Coordinator

Validates pickup points by giving the agent coordinates and asking for the nearest formatted street address to confirm location details.

What Changes When You Connect

You get accurate coordinates for anything. Use forward_geocode to take a street name and instantly get the precise lat/lon pair needed for mapping services.

Reverse lookups are simple. Give your agent coordinates, and it uses reverse_geocode to give you the full address details—no manual parsing required.

It handles international stuff. You don't have to write separate logic for different country formats; the API manages global coverage.

Better data cleaning means less time debugging. Feed messy addresses into a geocoding workflow, and get structured coordinates back every time.

You control the output format. The server lets you specify languages or fields, so the result matches exactly what your app expects.

See it in action

01 01

Validating Shipping Addresses

A user submits a shipping address via a web form. Instead of trusting it, your agent runs forward_geocode. If the coordinates return successfully and match the expected region, you know the address is valid for routing.

02 02

Finding a Point on a Map

You have GPS data (latitude/longitude) from a tracking device. You need to tell your user what street they are at. Your agent runs reverse_geocode and gets the formatted address: '123 Main Street, Anytown.'

03 03

Data Enrichment for CRM

Your data team has a spreadsheet of old records with just city names. To make them usable in a map viewer, your agent iterates through the list and runs forward_geocode on every single entry to pull coordinates.

04 04

Global Search Query Handling

A user asks for 'Main Street' but doesn't specify the country. Your agent uses forward_geocode, allowing you to pass filters (like Country: UK) to narrow down results and prevent ambiguity.

The honest tradeoffs

Assuming a simple text search is enough

Anti-pattern

Trying to calculate distance between two addresses by just using string matching or basic regex on the street name.

The Fix

You must use forward_geocode for both addresses. This converts them into precise coordinates, which you then feed into a proper distance calculation function.

Mixing up inputs and outputs

Anti-pattern

Getting coordinates from one source but trying to treat them like an address string later in the workflow.

The Fix

Remember the flow: Use forward_geocode (text $\to$ coords). Then, if you need text again, use reverse_geocode (coords $\to$ text).

Ignoring location ambiguity

Anti-pattern

Running a simple address lookup that returns only the city name, which could be hundreds of miles off.

The Fix

Pass as much detail into forward_geocode as possible (e.g., 'Main Street, London, England'). The more context you give it, the better the coordinates will be.

When It Fits, When It Doesn't

Use this server if your job requires translating between human language addresses and machine-readable lat/lon pairs—that's it. If you need to build a simple address validation layer or map location data for routing, this is perfect. Don't use it if your problem is purely internal (like checking user roles in a database) or if you only need to match ZIP codes without full coordinate resolution; those are better handled by dedicated database lookups. You must use the forward_geocode tool when starting with text, and the reverse_geocode tool when starting with coordinates.

Questions you might have

How does OpenCage Geocoder MCP Server handle addresses in different countries? +

It handles global coverage by pulling data from multiple sources like OpenStreetMap. You don't need to write separate logic for UK versus US address formats; the server manages that complexity.

What is the difference between `forward_geocode` and `reverse_geocode`? +

forward_geocode takes text (like an address) and gives you coordinates. reverse_geocode does the opposite: it takes coordinates and figures out the best matching street address.

Can I get road information using OpenCage Geocoder MCP Server? +

Yes, besides basic lat/lon, you can optionally retrieve specific road data. This helps verify nearest roads or pull attribute details for routing services.

What if the address I give to `forward_geocode` is wrong? +

The server will return null values or an error message, letting your agent know the lookup failed. It's built to handle ambiguous or invalid inputs gracefully.

How do I set up OpenCage Geocoder MCP Server with my API key? +

You must provide your specific OpenCage API key when connecting to the server. The agent uses this key for authorization, ensuring all calls remain within your account's usage limits.

What happens if I hit rate limits when calling `forward_geocode`? +

The server immediately returns an error status code indicating the limit breach. You must build backoff logic into your agent's workflow to wait and retry later.

If I use `forward_geocode` for a vague location, will it return one result or many? +

The server returns an array of potential matches if the input is ambiguous. Your AI client needs logic to process this list and select the best geographic fit.

Can I control the language of the address returned by `reverse_geocode`? +

Yes, you pass a locale parameter with the coordinates. This forces the API to return formatted address elements in your desired language for better user experience.

Can I limit the search results to a specific country? +

Yes! Use the countrycode parameter in the forward_geocode tool with ISO 3166-1 alpha-2 codes (e.g., 'us' for USA, 'br' for Brazil) to restrict results to that territory.

How do I get the address of a specific set of coordinates? +

Use the reverse_geocode tool by providing the lat (latitude) and lng (longitude). The agent will return the most accurate formatted address found for those coordinates.

Can I get information about the nearest road to a location? +

Yes. By setting the roadinfo parameter to true in either forward_geocode or reverse_geocode, the API will attempt to match the location to the nearest road and include road-specific data in the response.

How this MCP server connects to your AI agent

What AI agents can do with OpenCage Geocoder Automation

Forward geocode

Reverse geocode

What AI agents can do with OpenCage Geocoder: 2 Tools for Location Data

Forward Geocode

Converts a physical address or place name string into precise geographic latitude and longitude coordinates.

Reverse Geocode

Takes known latitude and longitude coordinates and returns the full, formatted...

Security and governance baked right in.

Claude AI

Open Claude Settings

Add Custom Connector

Start a conversation

Claude Code

Open your terminal

Add the MCP Server

Start coding

Cursor

One-Click Install (Recommended)

Open Cursor Settings

Add New Server

Use in Composer

Antigravity

Configure Agent Environment

Bind the Endpoint

Execute

VS Code Copilot

One-Click Install (Recommended)

Open MCP Settings

Add Server Config

Windsurf

One-Click Install (Recommended)

Open Windsurf Settings

Add Server Endpoint

LangChain

Install Dependencies

Connect the Server

CrewAI

Define the Tool

Execute Task

Choose How to Get Started

Build Your Own

Make Your AI Do More

Built on the Model Context Protocol (MCP) for Claude, ChatGPT, Cursor, and more

Manually converting addresses into map data is a huge pain point., Solved with Vinkius AI Gateway

OpenCage Geocoder MCP Server: Get structured data from addresses.

geocoding

reverse-geocoding

maps

location-data

coordinates

What your AI can actually do with this

How It Works

Global Scope and Flexibility

Here's how it actually works

Who is this actually for?

What Changes When You Connect

Validating Shipping Addresses

Finding a Point on a Map

Data Enrichment for CRM

Global Search Query Handling

The honest tradeoffs

Assuming a simple text search is enough

Mixing up inputs and outputs

Ignoring location ambiguity

When It Fits, When It Doesn't

Questions you might have