Skip to main content
Glama
Sign In
GeoAgent

GeoAgent

by AbishekFRK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to GeoAgent

No user-submitted related servers found.

    Related Servers

    • OpenStreetMap MCP Server v2

      ogSINGH
      A
      license
      A
      quality
      C
      maintenance
      Enables LLMs to geocode and reverse geocode places, find nearby points of interest, search categories within an area, get turn-by-turn routing, suggest meeting points, and analyze neighborhoods, commutes, schools, EV charging, and parking through OpenStreetMap data services. It also serves place and map tile resources over stdio, SSE, or Streamable HTTP transports.
      12
      MIT

    • GIS MCP Server

      briannag1692
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to perform geospatial analysis, spatial data processing, vector and raster operations, coordinate transformations, spatial statistics, mapping, and access to climate, satellite, and other geospatial data through MCP-compatible clients.
      MIT

    • gfm-mcp

      yuyi1008688
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes geospatial foundation model inference as MCP tools for LLM agents, enabling building extraction, water segmentation, object detection, change detection, zero-shot scene classification, and embeddings on CPU.
      3
      GPL 3.0
    • Magic Lane MCP Server

      Magic Lane MCP Serverofficial

      magiclane
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to become geospatially intelligent assistants with tools for location search, smart routing, round trip planning, reverse geocoding, isochrone analysis, route visualization, geofence management, and interactive map display.
      8
      17 npm
      8
      Apache 2.0
    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

    A3.8/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool maps to a distinct geo operation, and the descriptions explicitly route agents (e.g. 'call distance_bearing next', 'get the point from geocode first'). The only mild overlap is features_within versus nearest_features, since a small radius query can approximate an n-nearest query, but the descriptions ('within X km' vs 'closest/nearest') resolve this adequately.

    Naming Consistency3/5

    All names are snake_case and readable, but the grammatical conventions are mixed: geocode is a bare verb, distance_bearing and point_in_polygon are noun phrases, and features_within/nearest_features use noun+preposition forms. There is no single predictable verb_noun pattern to extrapolate from.

    Tool Count5/5

    Five tools is a tight, well-scoped surface for a geo lookup/measurement agent, and each tool covers a genuinely different question type (geocode, measure, radius search, nearest-n, containment). Nothing feels redundant or missing from the count perspective.

    Completeness4/5

    The core lifecycle of place resolution, measurement, proximity search, and polygon containment is covered with no obvious dead ends in the stated workflow. The main gap is reverse geocoding (coordinates back to a place name), which agents would have to work around by scanning features_within results.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources