Maps & transport · Local MCP server
GeoEDGE MCP
Geospatial analysis: vector and raster GIS operations, cartographic maps, spatial data access.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.GeoEDGE-git/geoedge-mcp- Version
- 1.0.9
- Status
- Active
- Category
- maps & transport
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-09-14
- Updated
- 2026-09-14
- Publisher
- GeoEDGE-git (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/GeoEDGE-git) · how
- Listed under
- Maps MCP servers
- Website
- mcp.geoedge.com.au
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | geoedge-mcp | 1.0.9 | stdio |
How to connect GeoEDGE MCP
GeoEDGE MCP runs locally from a Python package published to PyPI: geoedge-mcp version 1.0.9. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx geoedge-mcp. It reads these environment variables: GEOEDGE_MCP_LICENSE_KEY (required, secret) and GEOEDGE_MCP_STORAGE_PATH; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"geoedge-mcp": {
"command": "uvx",
"args": [
"geoedge-mcp"
],
"env": {
"GEOEDGE_MCP_LICENSE_KEY": "<secret>",
"GEOEDGE_MCP_STORAGE_PATH": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, mcp.geoedge.com.au, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | No real file found |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More maps & transport servers
| Server | Runs |
|---|---|
| Futuristic Risk IntelligenceGeopolitical conflict risk, political events, and maritime traffic data for AI agents. | Local · stdio |
| GeoGeocoding, routing, isochrones, traffic, weather, and place search for AI agents. 19 MCP tools. | Remote · HTTPLive check: sign-in required |
| GeoapifyGeocode, reverse-geocode, autocomplete, route and search places. | Remote · HTTPLive check: ✓ handshake |
| GeocodingForward and reverse geocoding, place search, and distance via OpenStreetMap Nominatim. No key. | Local · stdio |
| GeojpMCP server for Japan geodata: cadastral lot numbers (chiban) and reverse geocoding, for AI agents. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Geojs MCPIP geolocation from GeoJS. No key required. | Local · stdio |
| GeoLabelTurn GPS coordinates into place name, category, and live opening hours via OpenStreetMap. | Local · stdio |
| Geolocate MeGive any AI assistant real-time access to your phone's GPS and location history. | Remote · HTTPLive check: sign-in required |