GeoLens

io.github.geolens-ioPublished by GitHub account geolens-iov1.29.2Updated Nov 3, 2026

Read-only access to a self-hosted GeoLens spatial catalog: datasets, features, maps, sandboxed SQL.

VerifiedSTDIODesktop onlyDatabasesData & Analytics

Overview

AI-generated overview

Read-only MCP server that lets an assistant explore a self-hosted GeoLens spatial catalog: datasets, schemas, features, maps and sandboxed SQL.

What you can do
  • Discover datasets and inspect their schemas
  • Read features and maps from the catalog
  • Run read-only, sandboxed SQL queries
  • No write, ingest or admin operations; every call is scoped to the caller's access
When to use it
Useful when a coding agent or dev session needs to look up spatial data held in a self-hosted GeoLens instance, check schemas, or query features and maps without leaving the session.
Requirements
Runs locally as a Python package (pip install geolens-mcp or uvx geolens-mcp) over stdio. Requires GEOLENS_INSTANCE, the base URL of the GeoLens instance; the API suffix is appended automatically. Non-public data needs GEOLENS_API_KEY (sent as X-Api-Key), or GEOLENS_TOKEN, a JWT bearer token used only when the API key is unset. Network access to the instance is required.
Before you install
Requires credentials for non-public data: GEOLENS_API_KEY or GEOLENS_TOKEN, which grant access scoped to the caller. The server is read-only with no write, ingest or admin tools, but SQL queries and feature reads still send requests to your GeoLens instance, so point it only at a trusted instance URL.

Installation

In SourceWeft

  1. Open GeoLens in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

geolens-mcp

Apache-2.0 read-only Model Context Protocol server for GeoLens.

Point a coding agent (Claude Code, Cursor, Codex, …) at a GeoLens instance so it can discover datasets, inspect schemas, read features and maps, and run read-only SQL from inside a dev session. It has no write, ingest or admin tools, and every call is scoped to the caller's access.

Install

bash
pip install geolens-mcp        # or: uvx geolens-mcp

The server reads GEOLENS_INSTANCE and, for non-public data, GEOLENS_API_KEY from the environment. Client setup, the tool list and the credential rules are in the MCP guide.

Develop

bash
cd mcpuv run --extra dev python -m pytest -v

Source: mcp/README.md at commit 3ae9f0a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

16
  1. v1.29.2LatestNov 3, 2026
  2. v1.29.1Oct 31, 2026
  3. v1.29.0Oct 31, 2026
  4. v1.28.0Oct 29, 2026
  5. v1.27.1Oct 25, 2026
  6. v1.27.0Oct 24, 2026
  7. v1.26.0Oct 18, 2026
  8. v1.25.1Oct 17, 2026
  9. v1.24.0Oct 11, 2026
  10. v1.23.1Oct 10, 2026
  11. v1.23.0Oct 9, 2026
  12. v1.22.0Oct 5, 2026
  13. v1.21.1Oct 2, 2026
  14. v1.21.0Sep 28, 2026
  15. v1.20.0Sep 18, 2026
  16. v1.19.1Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts