How to Use the Nominatim MCP in LangChain

Q: Can my LangChain agent use Nominatim to verify specific building details?

Yes, your LangChain agent can call getdetails with an OSM ID to fetch administrative hierarchies. The agent parses this structural JSON to confirm if a location matches your LangChain business rules.

Q: What happens if a Nominatim query fails during a LangChain run?

If search returns an empty list, your LangChain agent can catch the empty response and attempt a broader query. You can also monitor latency by having the agent run getstatus at the start of the MCP chain.

Q: How do I query multiple geographic objects at once in LangChain?

Use the lookuposm tool in your LangChain chain with a comma-separated list of formatted IDs like N123,W456,R789. This returns a list of display names and coordinates directly to your agent, reducing round-trips.

Run free OpenStreetMap geocoding and routing queries directly inside your LangChain reasoning loops.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Nominatim MCP to LangChain

Create your Vinkius account to connect Nominatim to LangChain and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Nominatim with LangChain

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Chain location lookups with LangChain agents

The `search` tool lets your LangChain agent resolve messy user address strings into structured geographic coordinates. Because LangChain chains these outputs, the resulting Nominatim coordinates feed directly into your next tool without manual parsing. If the initial address is too vague, the LangChain agent runs `get_details` to pull the parent place hierarchy and check the importance score. This lets your chain validate the accuracy of the location before executing downstream database writes.

Validate spatial data using this MCP Server

The `get_status` tool gives your LangChain agent a quick way to verify the Nominatim server is online before kicking off a long-running batch job. If the Nominatim latency spikes or the server goes offline, your LangChain run catches the error and switches to a cached fallback dataset. When processing bulk coordinates, the LangChain agent uses `reverse_geocode` to resolve raw GPS points into readable street addresses. LangChain tracks these MCP tool calls in LangSmith, giving you a clear view of how many spatial queries your pipeline makes.

Deep geographic inspection via OSM identifiers

The `lookup_osm` tool allows your LangChain agent to fetch metadata for specific OpenStreetMap nodes, ways, or relations. You pass the formatted IDs directly from previous search results to pull the exact boundaries of a commercial property or park. By feeding the returned Nominatim bounding box and place rank into the LLM, the LangChain agent generates hyper-local summaries tailored to the user's immediate vicinity.

Setup guide

Set up Nominatim MCP in LangChain

Prerequisites

Python 3.10+ installed
langchain-mcp-adapters + langgraph packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install langchain-mcp-adapters langgraph langchain-openai. The MCP adapters package converts MCP tools into native LangChain BaseTool objects.
2

Connect via HTTP transport
Use MultiServerMCPClient with "transport": "http" pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create a ReAct agent
Pass the discovered tools to create_react_agent() from LangGraph. The agent automatically routes Nominatim tool calls through the MCP protocol.
4

Run with any LLM
Swap ChatOpenAI for ChatAnthropic, ChatGoogleGenerativeAI, or any LangChain-compatible model. The MCP tools work identically across all providers.

agent.py

from langchain_mcp_adapters.client import MultiServerMCPClient
from langgraph.prebuilt import create_react_agent
from langchain_openai import ChatOpenAI

async with MultiServerMCPClient({
    "nominatim-mcp": {
        "transport": "http",
        "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    }
}) as client:
    tools = client.get_tools()

    agent = create_react_agent(
        ChatOpenAI(model="gpt-4o"),
        tools,
    )
    result = await agent.ainvoke({
        "messages": "List recent Nominatim transactions"
    })
    print(result["messages"][-1].content)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Nominatim. 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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Nominatim now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Nominatim MCP in LangChain

You must configure a delay in your LangChain run loop to respect the Nominatim 1 request per second limit. Use a custom callback handler or rate-limiting middleware in your LangGraph setup to space out calls to `search` and `reverse_geocode`.

Yes, your LangChain agent can call `get_details` with an OSM ID to fetch administrative hierarchies. The agent parses this structural JSON to confirm if a location matches your LangChain business rules.

If `search` returns an empty list, your LangChain agent can catch the empty response and attempt a broader query. You can also monitor latency by having the agent run `get_status` at the start of the MCP chain.

Use the `lookup_osm` tool in your LangChain chain with a comma-separated list of formatted IDs like N123,W456,R789. This returns a list of display names and coordinates directly to your agent, reducing round-trips.

Your coordinates and address strings processed by LangChain never touch third-party tracking networks. The MCP server processes spatial queries inside an isolated, ephemeral V8 sandbox, and the underlying OpenStreetMap database does not log your private location history.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript