Mapsmith
Enables AI agents to perform professional-grade geoprocessing tasks such as buffers, overlays, reprojections, and terrain analysis with deterministic tools and verifiable provenance.
README
MapSmith π¨πΊοΈ
Professional-grade geoprocessing for AI agents β with provenance you can verify.
MapSmith is an open-source MCP server that gives any AI agent (Claude, ChatGPT, Copilot, Cursor, or your own) real GIS analysis capabilities: not just "make me a map", but buffers, overlays, reprojections, zonal statistics, terrain and network analysis β executed by deterministic engines, never hallucinated by the model.
Ask for the result. The agent picks the tools. Every output carries its full lineage.
Why MapSmith
- Real geoprocessing, not map CRUD. Built on the proven open geospatial stack (GDAL, GeoPandas, Shapely, and more to come: WhiteboxTools, PDAL, DuckDB Spatial, QGIS Processing via sidecar).
- Provenance by design. Every layer MapSmith produces ships with a machine-readable lineage manifest: source datasets (with checksums), every tool executed, exact parameters, CRS decisions, software versions, timestamps. Re-run it bit-identical, without the LLM. No AI slop.
- The LLM orchestrates, tools compute. Geometry and numbers only ever come from deterministic tool executions β never from model output.
- Semantic tools, not a tool dump. A curated set of goal-level tools plus a searchable operation catalog (progressive discovery), because agent accuracy collapses when you expose hundreds of raw tools.
Quickstart
# Docker (the supported path)
docker run -i --rm -v $(pwd)/data:/data ghcr.io/mapsmith-ai/mapsmith
# or from PyPI
uvx mapsmith
Add to Claude Desktop / any MCP client (stdio):
{
"mcpServers": {
"mapsmith": {
"command": "uvx",
"args": ["mapsmith"]
}
}
}
Then ask your agent things like:
"Take parcels.gpkg, keep only the parcels within 300 m of the river in rivers.gpkg, and give me the result with the analysis lineage."
Tools
| Tool | What it does |
|---|---|
describe_dataset |
CRS, geometry types, schema, extent, feature count of any vector dataset |
buffer_layer |
Metric buffer with automatic UTM estimation for geographic CRS |
clip_layer |
Clip a layer with a mask layer |
reproject_layer |
Reproject to any CRS (EPSG code or WKT) |
spatial_join |
Join by spatial predicate, auto-routed to the fastest engine (SedonaDB > DuckDB > GeoPandas) |
run_sql |
Spatial SQL (DuckDB dialect) over GeoParquet and GDAL formats |
zonal_statistics |
Raster statistics per vector zone with exact fractional pixel coverage ([raster] extra) |
hillshade |
Shaded relief from a DEM, in-memory Whitebox engine ([whitebox] extra) |
flow_accumulation |
D8 flow accumulation with automatic depression filling ([whitebox] extra) |
watershed |
Watershed delineation from a DEM and pour points ([whitebox] extra) |
get_provenance |
Return the full lineage manifest of any MapSmith output |
list_operations |
BM25-ranked catalog search; detail=true returns parameters and worked examples |
server_info |
Version, license, available engines |
Every tool that writes an output also writes <output>.provenance.json next to it β
and runs deterministic verification (CRS, dimensions, value invariants) whose results
are recorded in the manifest before any failure is raised.
The Docker image ships with the [raster] and [whitebox] extras included. With
uvx, pick your extras: uvx --from "mapsmith[raster,whitebox]" mapsmith.
Provenance example
{
"mapsmith_version": "0.1.0",
"operation": "buffer_layer",
"parameters": {"distance_meters": 300.0},
"inputs": [{"path": "rivers.gpkg", "sha256": "9f2cβ¦", "crs": "EPSG:4326"}],
"crs_decisions": {"analysis_crs": "EPSG:32632", "reason": "estimated UTM zone for metric buffering"},
"engine": {"name": "geopandas", "version": "1.0.1"},
"started_at": "2026-08-18T10:15:03Z",
"finished_at": "2026-08-18T10:15:04Z"
}
Architecture
AI agent (Claude / ChatGPT / Copilot / your app)
β MCP (stdio local Β· Streamable HTTP remote)
βΌ
βββββββββββββββββββββββββββββββββββββββββββββββ
β MapSmith server β
β Β· semantic tools + operation catalog β
β Β· parameter validation, CRS discipline β
β Β· provenance recorder (lineage manifests) β
βββββββββββββββββββββββββββββββββββββββββββββββ€
β Engines β
β Β· vector: GeoPandas/Shapely (built-in) β
β Β· SQL/analytics: DuckDB Spatial (built-in) β
β Β· heavy joins: SedonaDB ([sedona] extra) β
β Β· zonal stats: exactextract ([raster]) β
β Β· terrain/hydro: Whitebox NG ([whitebox]) β
β Β· qgis_process / GRASS sidecar (roadmap, β
β GPL-isolated via subprocess) β
βββββββββββββββββββββββββββββββββββββββββββββββ
Roadmap
- [x] Zonal statistics (exactextract, exact fractional coverage)
- [x] Whitebox Next Gen adapter: hillshade, flow accumulation, watershed (in-memory, open tier)
- [ ] More terrain & hydrology: slope/aspect, stream network extraction
- [ ] Typed analysis plans: the agent proposes a DAG, MapSmith validates it before running
- [ ] QGIS Processing sidecar (subprocess-isolated): ~900 algorithms
- [ ] Sandboxed code-execution tool for the long tail
- [ ] Remote server (Streamable HTTP + OAuth), long-job progress via MCP Tasks
- [ ] Map rendering: shareable MapLibre viewer URLs, MCP Apps
Install support policy
Docker (or uvx on a machine with working wheels) is the only supported installation path. Geospatial native dependencies across three OSes are a support black hole; issues about broken local environments will be redirected here.
License
- MapSmith server and engines: AGPL-3.0-or-later (see
LICENSE) - Client SDK and tool-schema definitions (future
sdk/): Apache-2.0
You can self-host MapSmith freely, forever. If you modify it and offer it as a service, the AGPL asks you to share your changes β or talk to us about a commercial license.
"MapSmith" is a trademark of the MapSmith project β see TRADEMARKS.md.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.