Skip to main content
Glama
jamesfiltness

geocoding-mcp

by jamesfiltness
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to geocoding-mcp

No user-submitted related servers found.

    Related Servers

    • geocode-mcp

      danishashko
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for geocoding, reverse geocoding, place/POI search, and distance calculation using OpenStreetMap Nominatim, with no API key required.
      43 npm
      1
      MIT

    • chuk-mcp-geocoder

      IBM
      A
      license
      A
      quality
      C
      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

    • mcp-photon

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      A geocoding MCP server that converts place names to coordinates and coordinates to place names using OpenStreetMap data.
      2 npm
      MIT

    • overpass-mcp

      Rusty0508
      A
      license
      A
      quality
      C
      maintenance
      MCP server providing structured access to OpenStreetMap data through Overpass and Nominatim APIs, enabling geocoding, nearby place searches, element queries, and tag counting without API keys.
      7
      MIT

    • geocodage-mcp

      cvagner
      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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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 issues

    Resources