Provides forward geocoding using the OpenStreetMap Nominatim API, converting location queries into coordinates and address details.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@geocoding-mcp geocode the Eiffel Tower"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP server for forward geocoding via the Nominatim API (OpenStreetMap). No API key required.
claude mcp add --scope user geocoding -- npx -y geo-coding-mcpAdd to your MCP config (e.g. claude_desktop_config.json):
{
"mcpServers": {
"geocoding": {
"command": "npx",
"args": ["-y", "geo-coding-mcp"]
}
}
}Related MCP server: geocodage-mcp
geocodeForward geocodes a free-form location query and returns matching places with coordinates and address details.
Parameters:
Name | Type | Required | Description |
| string | yes | Free-form search query, e.g. |
| number | no | Max results to return (1–40, default |
| string | no | Comma-separated ISO 3166-1 alpha-2 codes to filter by, e.g. |
| boolean | no | Include structured address breakdown (default |
| string | no | Bounding box to boost results: |
| boolean | no | Restrict results to within the viewbox (requires |
Example response:
Geocoding results for: Big Ben, London
Found 3 result(s)
==================================================
[1] Big Ben, Westminster Bridge Road, Lambeth, London, Greater London, England, SE1 7PB, United Kingdom
Lat: 51.5007325 Lon: -0.1246254
Type: tourism/attraction (importance: 0.7654)
Address: tourism: Big Ben, road: Westminster Bridge Road, city: London, postcode: SE1 7PB, country: United Kingdom
...npm run build
npx @modelcontextprotocol/inspector node ./build/index.jsMIT
Forward geocode a location query using the Nominatim (OpenStreetMap) API. Returns latitude, longitude, and address details for matching places.
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Free-form search query, e.g. '221B Baker Street, London' | |
| limit | No | Maximum number of results to return (1-40, default 5) | |
| bounded | No | Restrict results to within the viewbox (requires viewbox) | |
| viewbox | No | Bounding box to boost results: 'x1,y1,x2,y2' (min_lon,min_lat,max_lon,max_lat) | |
| countrycodes | No | Comma-separated ISO 3166-1 alpha-2 country codes to filter results, e.g. 'gb,us' | |
| addressdetails | No | Include structured address breakdown in results (default true) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided so the description bears the full load. It discloses the upstream API, which is useful, but says nothing about rate-limit policy, attribution requirements, ambiguity of free-form queries, or how multiple matches are returned.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences with no waste. It is front-loaded with the operation and follows with the return shape.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 6-parameter external-API tool with no annotations and no output schema, the description gives the agent the operation and return fields but omits operational concerns (rate limits, error/zero-result behavior) that an agent would benefit from knowing before calling.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents every parameter including defaults and ranges. The description adds no parameter-level meaning beyond what the schema states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (forward geocode) and resource (location query) with the underlying API named (Nominatim/OpenStreetMap). With no siblings to differentiate from, this is clear but stops short of the crispness of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no mention of rate limits, no suggestion of alternatives for the reverse-geocoding case. The description is purely definitional.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0geocodeScored across 1 tool
With only a single tool there is no possibility of overlap or misselection; 'geocode' has one unmistakable purpose (forward geocoding a query string).
The lone tool name 'geocode' is clear, lowercase, and well-chosen, but with just one tool there is no verb_noun pattern to demonstrate consistency across the set.
One tool is thin for a service whose domain (Nominatim) naturally includes forward and reverse geocoding plus lookup variants; the surface feels under-built rather than well-scoped.
Forward geocoding is covered, but obvious companion operations such as reverse geocoding (coordinates to address) and batch/multi-result lookup are absent, leaving notable gaps in the geocoding lifecycle.
Nominatim MCP — wraps OpenStreetMap Nominatim geocoding API (free, no auth)
Geo MCP — geographic utilities from free public APIs
Geospatial MCP server for earthquake, tsunami, volcano, disaster, and FX data queries.