Skip to main content
Glama
geolens-io

geolens-mcp

Official
by geolens-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to geolens-mcp

No user-submitted related servers found.

    Related Servers

    • osm-mcp

      a-tsitanov
      F
      license
      B
      quality
      B
      maintenance
      Provides read-only query tools over OpenStreetMap data in PostGIS, enabling natural language queries for features, categories, and spatial analysis.
      7
      -

    • FastAPI Database MCP Server

      amararun
      F
      license
      Not graded
      quality
      F
      maintenance
      Provides read-only SQL query access to Postgres and DuckDB databases via MCP tools, with extensive security hardening for public endpoints.
      1
      -

    • PostgreSQL MCP Server

      jplwunder
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides read-only access to PostgreSQL databases with schema inspection, query execution in multiple formats (JSON, CSV, Markdown), and query history tracking with built-in security features.
      -

    • postgres-mcp

      pleware
      A
      license
      A
      quality
      B
      maintenance
      Enables read-only PostgreSQL interaction with enforced SQL security policies, including query validation, row limits, and timeouts.
      4
      MIT

    • mcp-arcgis-salem

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides access to City of Salem GIS open geospatial data (ArcGIS), enabling search, query, and schema retrieval of datasets such as parcels, zoning, and public works.
      3 npm
      MIT

    • Vizru MCP server

      abhijithvs680
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides read-only SQL query access to PostgreSQL mirrors of Vizru spreadsheets on Neon, exposing REST endpoints and MCP tools for relational filtering and schema discovery.
      -
    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

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clear, distinct target: dataset discovery, schema/trust metadata, feature retrieval, SQL querying, and map metadata. There is potential overlap between get_features and query for reading data, but the descriptions frame them as different access modes (GeoJSON features vs. read-only SQL) so an agent can choose intentionally.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (search_datasets, get_features, get_dataset_schema, list_maps, get_map). The bare `query` tool is the only deviation, but it is a recognizable verb and does not clash with the others.

    Tool Count5/5

    Six tools is well-scoped for a geospatial catalog and map metadata server: three for dataset introspection/access, two for saved maps, and one for SQL. Each tool fills a distinct role without redundancy or sprawl.

    Completeness4/5

    The read-only dataset workflow is well covered: discover, inspect schema, fetch features, or run SQL. Minor gaps exist, such as no explicit list-all-datasets or per-feature lookup endpoint, but agents can work around them with search and query.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources