Log inSubmit server
Geolens logo

Geolens

by geolens-io

Read-only MCP access to GeoLens datasets, schemas, GeoJSON features, saved maps, and PostGIS SQL.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Geolens

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "geolens-io-geolens": {
      "command": "uvx",
      "args": [
        "geolens-mcp"
      ],
      "env": {
        "GEOLENS_INSTANCE": "YOUR_VALUE_HERE",
        "GEOLENS_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings ā†’ Developer ā†’ Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-testedā€” we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

geolens-io/geolens connects MCP-compatible coding agents to a self-hosted GeoLens instance. It supports dataset discovery, schema inspection, GeoJSON feature retrieval, saved-map access, and sandboxed read-only SQL against PostGIS. Use it when an agent needs to investigate geospatial catalog data without write, ingest, or administrative access. Public data can use the instance setting alone, while non-public data requires an API key.

Use cases

  • Search a GeoLens catalog for datasets relevant to a development task
  • Inspect spatial dataset schemas before writing application code
  • Retrieve GeoJSON features for analysis or debugging
  • Run read-only PostGIS queries from an agent session

Key features

  • Dataset discovery and search
  • Schema inspection
  • GeoJSON feature retrieval
  • Saved-map access
  • Sandboxed read-only PostGIS SQL
  • Caller-scoped access control

Security & health

What it can reach and how reliably it runs ā€” from our own checks, not the maintainerā€™s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

10/10 checks healthy over the last 49d

Supply-chain signal

2 high-severity advisories on record for this package. Most advisories affect transitive dependencies and may not be exploitable in this server's actual usage ā€” this is a directional signal, not a security audit.

Critical 0High 2Medium 0Low 1

Scanned 11d ago via OSV.dev Ā· geolens-mcp (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks ā€” not a rating.

GitHub stars282Stargazers on the source repository.
Last commit1d agoMost recent push to the default branch.
Directory activity7 viewsConfig copies, upvotes, and views on AllMCPs.

How Geolens works

What geolens-io/geolens does

geolens-io/geolens exposes a self-hosted GeoLens geospatial catalog through the Model Context Protocol. An MCP-compatible coding agent can search the catalog, examine dataset schemas, retrieve GeoJSON features, inspect saved maps, and query the underlying PostGIS data with read-only SQL.

The server is intended for investigation and development workflows rather than catalog management. It provides no write, ingestion, or administrative operations. Calls are limited by the requesting userā€™s access, so an agent cannot use the connection to bypass the permissions applied by the GeoLens instance.

How it works

The MCP client starts or connects to the server and directs requests to the configured GeoLens instance. The server reads the instance address from GEOLENS_INSTANCE. When the requested resources are private, it also uses GEOLENS_API_KEY for authentication.

Each operation remains read-only. SQL access is sandboxed and targets PostGIS data, making it suitable for examining spatial records, checking available fields, or producing query results during a development session. The same connection can also be used to locate datasets and move from catalog metadata to feature or map content.

Because access follows the callerā€™s permissions, the useful scope of a session depends on the identity and credentials supplied to GeoLens. A public instance or public datasets can be accessed without the private-data credential described by the project.

Setup and configuration

Install the package from PyPI with:

Terminal
pip install geolens-mcp

Alternatively, run it through uvx without installing it into the active environment:

bash
uvx geolens-mcp

Set GEOLENS_INSTANCE to identify the GeoLens deployment the agent should use. Set GEOLENS_API_KEY when the agent must access non-public data. Client-specific connection instructions and credential rules are maintained in the GeoLens MCP guide, so the client configuration should be matched to the MCP client being used.

The repository also includes a development test command using uv:

bash
cd mcp
uv run --extra dev python -m pytest -v

Tools and capabilities

  • Search and discover datasets in a GeoLens catalog.
  • Inspect the schemas associated with available datasets.
  • Read GeoJSON features from accessible geospatial data.
  • Retrieve saved maps.
  • Run sandboxed, read-only SQL over PostGIS.
  • Enforce the callerā€™s existing GeoLens access scope.

The capability set is deliberately read-only. It is a fit for agents that need to answer questions about spatial data or inspect a catalog from a coding workflow, but not for automating edits, ingestion pipelines, or administration.

Read the full README View source on GitHub

Reviews

No reviews yet ā€” be the first to share how it worked for you.

Frequently Asked Questions about Geolens

geolens-io/geolens is an MCP server that connects an AI coding agent to a self-hosted GeoLens instance. It provides read-only tools for finding datasets, inspecting schemas, retrieving GeoJSON features and saved maps, and executing sandboxed SQL against PostGIS. Access follows the callerā€™s permissions, with an API key used for non-public data.

Install it with `pip install geolens-mcp`, or run it with `uvx geolens-mcp`. Configure the MCP client to use the installed server, then set `GEOLENS_INSTANCE`; add `GEOLENS_API_KEY` when accessing non-public data.

Yes, Cursor is one of the coding agents named for use with geolens-io/geolens. Add the server through Cursorā€™s MCP configuration and provide the GeoLens instance and any required API key according to the client setup guidance.

No, geolens-io/geolens is read-only. Its capabilities cover dataset discovery, schema inspection, GeoJSON features, saved maps, and sandboxed SQL; it has no write, ingest, or administrative tools.

Related MCP servers

All in Location Services All alternatives
Add a badge to your READMEShow itā€™s listed ā€” live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGeolens AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/geolens-io-geolens?style=directory)](https://allmcps.com/mcp/geolens-io-geolens)
HTML Embed
<a href="https://allmcps.com/mcp/geolens-io-geolens"><img src="https://allmcps.com/api/badge/geolens-io-geolens?style=directory" alt="Geolens on AllMCPs" /></a>