Model Context Protocol server that packages GDAL-style geospatial workflows through Python-native libraries (Rasterio, GeoPandas, PyProj, etc.) to give AI agents catalog discovery, metadata intelligence, and raster/vector processing with built-in reasoning guidance and reference resources.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"gdal-mcp": {
"env": {
"GDAL_MCP_WORKSPACES": "/path/to/your/geospatial/data"
},
"args": [
"--from",
"gdal-mcp",
"gdal",
"--transport",
"stdio"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
GDAL MCP is a Model Context Protocol (MCP) server that provides AI agents with geospatial analysis capabilities while requiring them to justify their methodological choices through a reflection middleware system.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in maps / data
Query and manage PostgreSQL databases directly from AI assistants
🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
Manage Supabase projects — databases, auth, storage, and edge functions
Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators
MCP Security Weekly
Get CVE alerts and security updates for Gdal Mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
MCP server exposing GDAL/Rasterio operations to AI agents, with a reflection middleware that requires structured justification before executing operations whose methodology matters (CRS choice, resampling method, query extent).
uvx --from gdal-mcp gdal --transport stdio
docker build -t gdal-mcp .
docker run -i gdal-mcp gdal --transport stdio
git clone https://github.com/Wayfinder-Foundry/gdal-mcp.git
cd gdal-mcp
uv sync
uv run gdal --transport stdio
Add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/,
Windows: %APPDATA%\Claude\, Linux: ~/.config/Claude/):
{
"mcpServers": {
"gdal-mcp": {
"command": "uvx",
"args": ["--from", "gdal-mcp", "gdal", "--transport", "stdio"],
"env": {
"GDAL_MCP_WORKSPACES": "/path/to/your/geospatial/data"
}
}
}
}
Restart Claude Desktop. The MCP server indicator should appear, and the
raster_* and vector_* tools become available.
GDAL_MCP_WORKSPACES is a colon-separated list of directories the server
is allowed to touch. If unset, all paths are allowed and a warning is logged.
Optional tool-surface flags: RASTER=true, VECTOR=true. See
docs/ENVIRONMENT_VARIABLES.md for the full set.
raster_info, raster_convert, raster_reproject, raster_stats, raster_queryvector_info, vector_convert, vector_reproject, vector_clip, vector_buffer, vector_simplify, vector_queryworkspace://...), metadata (metadata://...), reference (reference://...), query results (query://result/{id})justify_crs_selection, justify_resampling_method, justify_query_extent (and more under src/prompts/)See TOOLS.md for parameters, return shapes, and worked examples.
Tools whose methodology matters refuse to execute until the calling agent produces a structured justification. The flow is:
raster_reproject(dst_crs="EPSG:3857", resampling="cubic", ...)..preflight/justifications/{domain}/ for a matching hash.ToolError with a hint pointing at the
relevant prompt (e.g. justify_crs_selection).Justification schema (intent,
alternatives considered, choice, tradeoffs, confidence), and re-invokes
the tool with a __reflection payload.raster_reproject and vector_reproject
on subsequent calls.See docs/REFLECTION.md for the schema and cache layout, and docs/PHILOSOPHY.md for why this exists.