Nominatim MCP. Map Coordinates and Addresses from OpenStreetMap Data
Nominatim lets your AI client search the world’s open-source map data (OpenStreetMap) without needing an API key. You can find places, translate GPS coordinates into street addresses, and pull detailed geographical information simply by talking to your agent.
Give Claude and any AI agent real-world access
Your agent can find specific points of interest anywhere in the world, whether you know the street address or just the kind of place (like a hospital).
If you get GPS numbers, this MCP translates them into clear, human-readable city and state addresses.
You can query the system using a specific OpenStreetMap ID to pull all known details about that geographical feature.
The MCP returns defined bounding boxes for large areas, like whole countries or city districts.
Ask an AI about this
Waiting for input…
What AI agents can do with Nominatim MCP - 5 Tools
These tools allow your agent to search for places by name, convert raw coordinates to human addresses, and pull deep details about any object found on OpenStreetMap.
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 Nominatim MCPGet Details
Pulls comprehensive information about a specific OpenStreetMap feature using its unique ID.
Lookup Osm
Retrieves general data, coordinates, and properties for multiple OpenStreetMap...
Reverse Geocode
Converts a set of geographic coordinates into the nearest official address details...
Search
Finds places by name or partial address, returning structured results with bounding...
Get Status
Checks the current operational status of the Nominatim service to confirm it's ready...
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.
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 each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Nominatim, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
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.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Manually cross-referencing location data slows down every project.
Today, if you need to validate an address list or find out what a set of GPS coordinates mean, you're stuck copy-pasting into multiple paid mapping websites. You hit rate limits, pay per thousand lookups, and spend hours stitching together disparate pieces of information just to get a clean dataset.
With this MCP, your agent handles the complexity automatically. You simply ask for the location data, and it uses powerful tools like `search` to pull structured results—giving you everything from city names down to the correct postal code in one go.
Nominatim gives you reliable context with Nominatim MCP.
Instead of opening five different tabs, navigating through paid account dashboards, and waiting for API keys to refresh, your agent executes the entire workflow in a single conversation. It can use `reverse_geocode` to confirm an address instantly.
The result is immediate, reliable location context powered by open data. Your work moves from manual lookups to automated discovery.
What Nominatim MCP does for your AI
Need to understand a location but don't want to pay for mapping services? This MCP connects you directly to OpenStreetMap’s massive, community-driven database. Forget the hassle of managing API keys or dealing with service limits. You just talk to your AI client and it handles the complex lookup process.
It lets your agent find physical locations by name—whether it's a school, a restaurant, or a specific street corner. If you only have GPS coordinates, the MCP converts them back into full, readable addresses, giving you context immediately. You can also drill down into geographic details: look up complex object IDs or determine the exact boundaries of a city block.
This service is critical for anyone dealing with location data who needs reliable results without proprietary restrictions. Connect it via Vinkius and your agent accesses this entire catalog of global spatial data instantly.
019d8460-9633-73ee-92d5-07599495f483 How to set up Nominatim MCP
The bottom line is that once connected, your AI client treats OpenStreetMap data like a built-in tool you can call with natural language instructions.
Subscribe to this MCP on Vinkius.
Connect your preferred AI client (like Claude or Cursor) to the catalog.
Tell your agent what you need—for example, 'What address is at 40.7128, -74.0060?' and it handles the rest.
Who uses Nominatim MCP
This MCP is for the data analyst who needs to batch process thousands of addresses without paying per query. It’s for the field researcher mapping out routes based on open-source maps, and the developer building systems that need reliable location context everywhere.
Running scripts to geocode large lists of addresses or extract structured data components (like zip codes) from raw text.
Determining the exact administrative boundaries and types of places at random GPS coordinates during an investigation.
Building prototypes that require location context, like routing or validating address formats, without relying on paid commercial APIs.
Benefits of connecting Nominatim MCP
Eliminate API costs. You get access to the entire OpenStreetMap database for free, meaning you never have to worry about paid usage limits when running search or reverse_geocode.
Get structured data components instantly. When your agent runs a search, it doesn't just give you a name; it provides detailed address parts like street, postal code, and country, which is perfect for databases.
Work with raw IDs. Need to know everything about a specific object? Use get_details or lookup_osm to pull deep context from the map data that simple searches miss.
Understand boundaries. If you need to scope an area—say, all locations within a given city limit—the MCP returns precise geographic bounding boxes for reliable filtering.
Handle global scale. The service supports multi-language naming conventions and robust searching across diverse global regions, making it ideal for international projects.
Nominatim MCP use cases
Validating a mailing list
A marketing team has a spreadsheet of old addresses. Instead of manually checking each one, they prompt their agent to 'validate these 50 locations.' The agent uses the search tool to verify if the address exists and pull standardized components like zip codes.
Mapping archaeological sites
A researcher finds a collection of historical GPS coordinates. They ask their agent to 'translate these points into formal addresses.' The agent uses reverse_geocode to give the coordinates immediate, usable context for reporting.
Building a localized content app
A developer needs to list all local amenities (hospitals, schools) near a central point. They prompt their agent to 'find all type=hospital within 1km of X coordinates.' The agent uses search with structured filters.
Analyzing regional market reach
A business wants to know the exact boundaries of a state or metropolitan area for sales planning. They ask their agent to 'give me the bounding box for Ohio.' The MCP uses this information to define the precise operational region.
Nominatim MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Assuming all mapping data is uniform
Trying to use a generic API call that only returns latitude/longitude and a single, vague address line.
Always use reverse_geocode or the search tool. These tools guarantee you get structured components—the city, state, and country separated out—which is necessary for data cleaning.
Relying on a single search result
Only using simple text searches that might return the most popular or visible location, ignoring other nearby points of interest.
Use lookup_osm and feed it multiple IDs to pull comprehensive data for several related features at once. This gives you a holistic view of the area.
Stopping when an address is found
Getting an address but not knowing if that location has administrative boundaries or parent hierarchies.
After finding a place, ask your agent to use get_details on the object ID. This reveals its full parent hierarchy and links to other data sources.
When to use Nominatim MCP
Use this MCP if your primary need is open-source geographic context—you are mapping, validating addresses, or building location logic based on OpenStreetMap’s global community data. You must use it when you cannot afford paid API calls, or when the specific nature of the location requires detailed, non-commercial object metadata.
Don't use this if your core requirement is accessing highly proprietary or restricted business data (like internal corporate records) that hasn't been mapped to OpenStreetMap. If you only need simple 'point A to point B' routing without needing component validation, a dedicated route planning tool might suffice. However, for any task involving address components, boundaries, or identifying what a set of coordinates represents, this Nominatim MCP is the right choice.
Frequently asked questions about Nominatim MCP
Does Nominatim MCP require me to pay for API access? +
No. This MCP connects directly to OpenStreetMap and does not require you to manage or provide any paid API keys. It's completely free, powered by community data.
How do I use the Nominatim MCP in my agent workflow? +
You simply connect your AI client through Vinkius and ask it to perform an action—like 'find a restaurant near 40.7128, -74.0060.' The agent figures out which tool to call.
Can Nominatim MCP find addresses in countries without good mapping coverage? +
Yes, because it uses OpenStreetMap data, its coverage is vast and community-driven, making it useful for regions where commercial map services might fail or charge exorbitant rates.
Which tool should I use to verify an address component? +
The search tool is best. It returns results with structured components (street, city, state) and coordinates, allowing you to validate specific parts of the address.
Can Nominatim MCP get me the boundaries for a region? +
Yes, use get_details or other lookup tools. They provide bounding boxes, which define the exact minimum and maximum coordinates for a given area.
Do I need an API key? +
No! Nominatim is completely free and requires no authentication. It's powered by the OpenStreetMap community. Just subscribe and start searching. Rate limit is 1 request per second.
How accurate is the geocoding? +
Nominatim uses OpenStreetMap data, which is crowd-sourced and varies by region. Urban areas typically have very accurate results. Use addressdetails=1 to get structured address components and namedetails=1 for multi-language names.
Can I convert coordinates to an address? +
Yes! Use reverse_geocode with latitude and longitude. Returns the nearest address with street name, house number, city, state, postal code and country. Supports different zoom levels for varying detail granularity.
What is an OSM ID and how do I use it? +
OSM IDs are unique identifiers for OpenStreetMap objects: N for nodes (points), W for ways (lines/areas), R for relations (groups). Use lookup_osm with IDs like 'W123456' or 'N987654'. Use get_details for comprehensive info on a single object.