GeoEDGE MCP

io.github.GeoEDGE-gitPublished by GitHub account GeoEDGE-gitv1.0.9Updated Oct 24, 2026

Geospatial analysis: vector and raster GIS operations, cartographic maps, spatial data access

The publisher's own server: Edge Network

VerifiedSTDIODesktop onlyLocation & LifestyleData & Analytics

Overview

AI-generated overview

A local MCP server that gives an assistant geospatial analysis tools for vector and raster GIS operations, cartographic maps and spatial data access.

What you can do
Run vector and raster GIS operations on spatial data through the assistant, such as processing and analysis tasks described as geospatial analysis capabilities. Produce cartographic maps from the data. Access and work with spatial data files stored locally. GIS tools stay disabled unless a valid subscription licence key is supplied.
When to use it
Useful when you want an assistant to carry out GIS analysis, map production or spatial data handling on your own machine without leaving the chat, and you already have a GeoEDGE subscription.
Requirements
Runs locally as a stdio process, installed from the PyPI package geoedge-mcp and launched with uvx, so a Python/uv environment is needed. A GeoEDGE subscription licence key must be provided in the GEOEDGE_MCP_LICENSE_KEY environment variable. Optionally set GEOEDGE_MCP_STORAGE_PATH to choose the folder for GIS data files; otherwise a per-user folder is used. Desktop only.
Before you install
The licence key is a secret passed via GEOEDGE_MCP_LICENSE_KEY and is required for the GIS tools to work. The server reads and writes GIS data files in the configured storage folder, so point it at a directory you are comfortable having modified.

Installation

In SourceWeft

  1. Open GeoEDGE MCP 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.

Tools

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

Version history

1
  1. v1.0.9LatestSep 16, 2026

Score

25% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Edge integrations