GIS MCP Server
A Model Context Protocol (MCP) server providing geospatial tools for AI agents. Enables Claude, GPT, and other LLMs to perform geocoding, routing, spatial analysis, and file operations.
Features
- Geocoding: Convert addresses to coordinates and vice versa (via Nominatim/OSM or Pelias)
- Batch Geocoding: Geocode multiple addresses in a single request (up to 10)
- Elevation Data: Get altitude for points and elevation profiles along paths
- Routing: Calculate routes between points with distance, duration, and geometry (via OSRM)
- Spatial Analysis: Buffer, intersection, union, distance calculations
- File I/O: Read/write Shapefiles, GeoJSON, GeoPackage
- CRS Transformation: Convert between coordinate reference systems
Installation
# From PyPI (when published)
pip install gis-mcp-server
# From source
git clone https://github.com/matbel91765/gis-mcp-server.git
cd gis-mcp-server
pip install -e .
Quick Start
With Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"gis": {
"command": "uvx",
"args": ["gis-mcp-server"]
}
}
}
Direct Usage
# Run the server
gis-mcp-server
Available Tools
Geocoding
geocode
Convert an address to coordinates.
Input: "1600 Pennsylvania Avenue, Washington DC"
Output: {lat: 38.8977, lon: -77.0365, display_name: "White House..."}
reverse_geocode
Convert coordinates to an address.
Input: lat=48.8566, lon=2.3522
Output: {display_name: "Paris, Île-de-France, France", ...}
batch_geocode
Geocode multiple addresses at once (max 10).
Input: addresses=["Paris, France", "London, UK", "Berlin, Germany"]
Output: {results: [...], summary: {total: 3, successful: 3, failed: 0}}
Elevation
get_elevation
Get altitude for a point.
Input: lat=48.8566, lon=2.3522
Output: {elevation_m: 35, location: {lat: 48.8566, lon: 2.3522}}
get_elevation_profile
Get elevations along a path.
Input: coordinates=[[2.3522, 48.8566], [2.2945, 48.8584]]
Output: {profile: [...], stats: {min: 28, max: 42, gain: 14}}
Geometry
distance
Calculate distance between two points.
Input: lat1=48.8566, lon1=2.3522, lat2=51.5074, lon2=-0.1278
Output: {distance: {meters: 343556, kilometers: 343.56, miles: 213.47}}
buffer
Create a buffer zone around a geometry.
Input: geometry={type: "Point", coordinates: [2.3522, 48.8566]}, distance_meters=1000
Output: {geometry: {type: "Polygon", ...}, area_km2: 3.14}
spatial_query
Perform spatial operations (intersection, union, contains, within, etc.).
Input: geometry1={...}, geometry2={...}, operation="intersection"
Output: {geometry: {...}}
transform_crs
Transform coordinates between CRS.
Input: geometry={...}, source_crs="EPSG:4326", target_crs="EPSG:3857"
Output: {geometry: {...}}
Routing
route
Calculate route between two points.
Input: start_lat=48.8566, start_lon=2.3522, end_lat=48.8606, end_lon=2.3376
Output: {distance: {...}, duration: {...}, geometry: {...}, steps: [...]}
isochrone
Calculate area reachable within a time limit.
Input: lat=48.8566, lon=2.3522, time_minutes=15, profile="driving"
Output: {geometry: {type: "Polygon", ...}}
Files
read_file
Read geospatial files (Shapefile, GeoJSON, GeoPackage).
Input: file_path="data/cities.shp"
Output: {type: "FeatureCollection", features: [...]}
write_file
Write features to geospatial files.
Input: features={...}, file_path="output.geojson", driver="GeoJSON"
Output: {file_path: "...", feature_count: 10}
Configuration
Environment variables:
| Variable | Default | Description |
|---|---|---|
NOMINATIM_URL |
https://nominatim.openstreetmap.org |
Nominatim API URL |
NOMINATIM_USER_AGENT |
gis-mcp-server/1.0.0 |
User agent for Nominatim |
OSRM_URL |
https://router.project-osrm.org |
OSRM API URL |
OSRM_PROFILE |
driving |
Default routing profile |
PELIAS_URL |
(empty) | Pelias geocoding API URL |
PELIAS_API_KEY |
(empty) | Pelias API key (optional) |
OPEN_ELEVATION_URL |
https://api.open-elevation.com |
Open-Elevation API URL |
GIS_DEFAULT_CRS |
EPSG:4326 |
Default CRS |
GIS_TEMP_DIR |
/tmp/gis-mcp |
Temporary directory |
Response Format
All tools return a consistent JSON structure:
{
"success": true,
"data": { ... },
"metadata": {
"source": "nominatim",
"confidence": 0.95
},
"error": null
}
Rate Limits
- Nominatim: 1 request/second (enforced automatically)
- OSRM Demo: Best effort, consider self-hosting for production
Development
# Install dev dependencies
pip install -e ".[dev]"
# Run tests
pytest
# Run with coverage
pytest --cov=src/gis_mcp --cov-report=html
# Type checking
mypy src/gis_mcp
# Linting
ruff check src/gis_mcp
Architecture
src/gis_mcp/
├── server.py # MCP server entry point
├── config.py # Configuration management
├── utils.py # Common utilities
└── tools/
├── geocoding.py # geocode, reverse_geocode, batch_geocode
├── elevation.py # get_elevation, get_elevation_profile
├── routing.py # route, isochrone
├── geometry.py # buffer, distance, spatial_query, transform_crs
└── files.py # read_file, write_file
License
MIT License - see LICENSE for details.
Contributing
Contributions welcome! Please read the contributing guidelines before submitting PRs.
Roadmap
- Pelias geocoding support (higher accuracy)
- Elevation/terrain data
- Batch geocoding
- Valhalla routing integration (native isochrones)
- PostGIS spatial queries
- Real-time traffic data
- ESRI FileGDB full support
Metadata
Release files for gis-mcp-server 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| gis_mcp_server-1.2.0.tar.gz | 50.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gis_mcp_server-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 94.0 kB
Release files / gis_mcp_server-1.2.0.tar.gz
| Download URL | gis_mcp_server-1.2.0.tar.gz |
|---|---|
| Size | 50.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e932b9ce58a52d1de0f4a99021e0ce011bcb7810598898dd4620c4f45813c8fa
|
|
BLAKE2b-256 checksum How to use checksums |
9790a1a4c6b4740683edcc5e2253caf7a7f0a077d7df1050a0446f1cd044fe6e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 4, 2025.
Transparency logRelease files / gis_mcp_server-1.2.0-py3-none-any.whl
| Download URL | gis_mcp_server-1.2.0-py3-none-any.whl |
|---|---|
| Size | 43.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c283cc65bfdde699548650f93cb14f746026130fe21fd314c910d2038d167947
|
|
BLAKE2b-256 checksum How to use checksums |
2bf5821220fe028326a036dfd3ef395809dca2a562b31d6eebe20040c49d5328
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 4, 2025.
Transparency logSecurity for gis-mcp-server 1.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for gis_mcp_server-1.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 4, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.