mcp_geocoding_get_coordinatesLABSCO SUMMARY
Raise `limit` when the name is ambiguous.
Place names repeat, and a single result is a guess. Asking for several and reading type and importance is how you tell the city from the street or the village of the same name — that is the whole reason those fields come back. Everything else here is deliberately absent: one tool, no key, no configuration.
What it is
A geocoder built on OpenStreetMap's Nominatim service. Give it a city, an address or a place description and it returns latitude and longitude — plus the matched display name, place type, importance ranking and bounding box.
What you get
mcp_geocoding_get_coordinatestakes alocationstring — a city, a country-qualified name, or a street address- An optional
limitreturns several candidates instead of one; the default is 1 and the maximum is 10 - Each result carries
latitude,longitude,display_name,place_id,type,class,importanceand abounding_box - The
importanceandtypefields are what let you tell a city apart from a street of the same name - Global coverage, since it is querying OpenStreetMap data
Requirements
Nothing but a Python runner: uvx geocode-mcp is the documented install, and the client entry is uvx with geocode-mcp as its argument. Also installable with pip install geocode-mcp. Published as geocode-mcp version 0.2.0, built for Python 3.12+. No API key — Nominatim is free to use.
Setup effort
One command — uvx geocode-mcp
USE CASES
01
Getting coordinates for a place you mentioned in passing
Ask for the latitude and longitude of a city without opening a map service.
02
Resolving an ambiguous name
Return several candidates and pick by type and importance rather than accepting the first.
03
Feeding coordinates into another tool
Convert an address to a lat/lon pair so a routing or weather call can use it.
04
Getting a bounding box for a region
Take the returned box as a map extent instead of computing one.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
uvx on PATH
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx geocode-mcpMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"geocoding": {
"command": "uvx",
"args": [
"geocode-mcp"
]
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"geocoding": {
"command": "uvx",
"args": [
"geocode-mcp"
]
}
}
}Copy the configuration from config/vscode-mcp.json to your VS Code MCP settings.
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"geocoding": {
"command": "uvx",
"args": [
"geocode-mcp"
]
}
}
}Copy the configuration from config/claude-desktop.json to your Claude Desktop config file.
