Skip to main content
Glama
geocoding-mcp

geocoding-mcp

geo-coding-mcp

An MCP server for forward geocoding via the Nominatim API (OpenStreetMap). No API key required.

Usage

Claude CLI

claude mcp add --scope user geocoding -- npx -y geo-coding-mcp

Manual configuration

Add to your MCP config (e.g. claude_desktop_config.json):

{
  "mcpServers": {
    "geocoding": {
      "command": "npx",
      "args": ["-y", "geo-coding-mcp"]
    }
  }
}

Related MCP server: geocodage-mcp

Tool

geocode

Forward geocodes a free-form location query and returns matching places with coordinates and address details.

Parameters:

Name

Type

Required

Description

q

string

yes

Free-form search query, e.g. "221B Baker Street, London"

limit

number

no

Max results to return (1–40, default 5)

countrycodes

string

no

Comma-separated ISO 3166-1 alpha-2 codes to filter by, e.g. "gb,us"

addressdetails

boolean

no

Include structured address breakdown (default true)

viewbox

string

no

Bounding box to boost results: "x1,y1,x2,y2" (min_lon,min_lat,max_lon,max_lat)

bounded

boolean

no

Restrict results to within the viewbox (requires viewbox)

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
...

Testing locally

npm run build
npx @modelcontextprotocol/inspector node ./build/index.js

License

MIT

Available Tools

1 tool
geocodeC

Forward geocode a location query using the Nominatim (OpenStreetMap) API. Returns latitude, longitude, and address details for matching places.

Inputs: q (required), limit, bounded, viewbox, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool there is no possibility of overlap or misselection; 'geocode' has one unmistakable purpose (forward geocoding a query string).

    Naming Consistency4/5

    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.

    Tool Count3/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      F
      maintenance
      An MCP server providing geocoding and place discovery services via Nominatim and OpenStreetMap. It enables users to perform forward and reverse geocoding, extract bounding boxes, and find nearby places or administrative hierarchies.
      10
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for geocoding French addresses, POIs, and cadastral parcels using the Géoplateforme API. Supports direct geocoding, reverse geocoding, and capability queries.
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for geocoding, reverse geocoding, place/POI search, and distance calculation using OpenStreetMap Nominatim, with no API key required.
      92 npm
      1
      MIT