MapSmith
OfficialMapsmith 🔨🗺️
Профессиональная геообработка для AI-агентов — с проверяемым происхождением.
Mapsmith — это открытый MCP-сервер, который предоставляет любому AI-агенту (Claude, ChatGPT, Copilot, Cursor или вашему собственному) реальные возможности GIS-анализа: не просто «сделай мне карту», а буферы, наложения, перепроецирования, зональную статистику, анализ рельефа и сетей — выполняемые детерминированными движками, никогда не галлюцинируемые моделью.
Спрашивайте результат. Агент выбирает инструменты. Каждый вывод несет свое полное происхождение.
Почему Mapsmith
Настоящая геообработка, а не CRUD для карт. Построен на проверенном открытом геопространственном стеке (GDAL, GeoPandas, Shapely и другие: WhiteboxTools, PDAL, DuckDB Spatial, QGIS Processing через sidecar).
Происхождение по замыслу. Каждый слой, который создает Mapsmith, поставляется с машиночитаемым манифестом происхождения: исходные наборы данных (с контрольными суммами), каждый выполненный инструмент, точные параметры, решения по CRS, версии ПО, временные метки. Перезапустите его побитово идентично, без LLM. Никакого AI-мусора.
LLM управляет, инструменты вычисляют. Геометрия и числа всегда поступают только из детерминированных выполнений инструментов — никогда из вывода модели.
Семантические инструменты, а не свалка инструментов. Подобранный набор инструментов уровня целей плюс доступный для поиска каталог операций (прогрессивное обнаружение), потому что точность агента падает, когда вы открываете сотни сырых инструментов.
Related MCP server: GIS MCP Server
Быстрый старт
# Docker (the supported path)
docker run -i --rm -v $(pwd)/data:/data ghcr.io/mapsmith-ai/mapsmith
# or from PyPI
uvx mapsmithДобавьте в Claude Desktop / любой MCP-клиент (stdio):
{
"mcpServers": {
"mapsmith": {
"command": "uvx",
"args": ["mapsmith"]
}
}
}Затем спрашивайте своего агента что-то вроде:
«Возьми parcels.gpkg, оставь только участки в пределах 300 м от реки в rivers.gpkg, и дай мне результат с происхождением анализа.»
Инструменты (v0.1)
Инструмент | Что делает |
| CRS, типы геометрии, схема, экстент, количество объектов любого векторного набора данных |
| Метрический буфер с автоматическим расчетом UTM для географической CRS |
| Обрезать слой с помощью маски |
| Перепроецировать в любую CRS (код EPSG или WKT) |
| Соединить атрибуты по пространственному предикату (intersects/within/contains) |
| Возвращает полный манифест происхождения любого вывода Mapsmith |
| Доступный для поиска каталог доступных операций (прогрессивное обнаружение) |
Каждый инструмент, который записывает вывод, также записывает <output>.provenance.json рядом с ним.
Пример происхождения
{
"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"
}Архитектура
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) │
│ · raster: Rasterio (roadmap) │
│ · terrain/hydro: WhiteboxTools (roadmap) │
│ · qgis_process / GRASS sidecar (roadmap, │
│ GPL-isolated via subprocess) │
└─────────────────────────────────────────────┘План развития
Растровый движок (Rasterio): зональная статистика, обрезка, отмывка рельефа, алгебра
Адаптер WhiteboxTools: рельеф и гидрология (500+ разрешительных инструментов)
Боковой процесс QGIS Processing (изолированный подпроцесс): ~900 алгоритмов
Инструмент выполнения кода в песочнице для длинного хвоста
Удаленный сервер (Streamable HTTP + OAuth), прогресс длительных задач через MCP Tasks
Отрисовка карт: доступные для публикации URL просмотрщика MapLibre, MCP Apps
Политика поддержки установки
Docker (или uvx на машине с работающими колесами) — единственный поддерживаемый путь установки. Нативные геопространственные зависимости на трех ОС — это черная дыра поддержки; вопросы о сломанных локальных окружениях будут перенаправлены сюда.
Лицензия
Сервер и движки Mapsmith: AGPL-3.0-or-later (см.
LICENSE)Клиентский SDK и определения схем инструментов (будущий
sdk/): Apache-2.0
Вы можете свободно размещать Mapsmith на своем сервере навсегда. Если вы изменяете его и предлагаете как услугу, AGPL просит вас делиться своими изменениями — или свяжитесь с нами по поводу коммерческой лицензии.
«Mapsmith» является товарным знаком проекта Mapsmith — см. TRADEMARKS.md.
Available Tools
29 toolsaspectAIdempotent
Aspect from a DEM: downslope azimuth in degrees, 0 = north. GeoTIFF in/out.
FLAT CELLS ARE -1, not nodata — mask them before averaging aspect over an area, or the average is plausibly wrong. DEMs in a geographic CRS are refused (see slope): reproject to a projected CRS first. Requires the [whitebox] extra.
Inputs: dem_path (required), output_path (required), z_factor. Returns: object
brief_planARead-onlyIdempotent
Render a project brief from a plan that has ALREADY passed validation.
Every statement carries its source: operation declaration, argument rule, validation finding, engine availability or install requirement. Invalid plans return only the validation report and no project text. Installation commands are printed for the person to run; MapSmith never installs an engine.
Inputs: plan (required). Returns: object
buffer_layerAIdempotent
Buffer all features by a distance in meters.
Geographic-CRS inputs are reprojected to an estimated UTM zone for the metric
operation and back; the decision is recorded in the provenance manifest.
A warnings key in the result flags a suspicious-but-valid outcome with a
hint — e.g. a negative distance that eroded every geometry away.
Inputs: input_path (required), output_path (required), distance_meters (required). Returns: object
centroid_layerAIdempotent
One point per feature: the geometric centroid, computed in a metric CRS.
Geographic-CRS inputs are measured in an estimated UTM zone (decision recorded in the manifest) and returned in the input CRS — a planar centroid of degree coordinates lands in the wrong place, quietly. The output is verified: same feature count, Point geometry, input CRS. Note the manifest's caveat: the centroid of a concave or multi-part feature can fall outside it. Inputs without a CRS are refused.
Inputs: input_path (required), output_path (required). Returns: object
clip_layerAIdempotent
Clip a layer to the area of a mask layer. CRS are aligned automatically.
A warnings key in the result means the analysis ran but something is worth
your attention (typically an empty result, or inputs whose extents do not
overlap); each entry carries a hint. Inputs without a CRS are refused.
Inputs: mask_path (required), input_path (required), output_path (required). Returns: object
convert_formatAIdempotent
Convert a vector dataset between formats; the target is chosen by the output extension (.parquet, .gpkg, .geojson).
The output is re-read and verified: same feature count, same CRS. Two conversions are refused with the reason: shapefile (field names truncated to 10 characters, silently) and GeoJSON for non-WGS84 layers (RFC 7946 is WGS84 by definition — reproject first). Invalid geometry carried through is repaired deterministically and reported in a 'repairs' key.
Inputs: input_path (required), output_path (required). Returns: object
describe_datasetARead-onlyIdempotent
Inspect a dataset, vector or raster, before analysing it.
Vector: CRS, geometry types, schema, extent, feature count. A MULTI-LAYER container (e.g. a GeoPackage holding several layers) is described per layer — name, feature count, geometry type, CRS — because operations refuse containers with no chosen layer: extract the layer you mean first (run_sql: SELECT * FROM ST_Read(path, layer='name') with an output_path). Raster (.tif): CRS, grid size, resolution, bands with dtype, nodata and masked statistics (nodata cells counted separately). Call this first on any dataset you have not inspected yet — most silent GIS errors start with wrong assumptions about CRS, units, nodata or which layer you are on. Raster inspection requires the [raster] extra.
Inputs: path (required). Returns: object
dissolve_layerAIdempotent
Merge features into one geometry per value of by (or one feature in all).
aggfunc — first (default), last, sum, mean, median, min, max or count — is
applied to the other columns and RECORDED in the manifest: a sum reported
where a mean was meant is a plausible wrong number nobody can see. Features
with a null by key are dropped by the grouping and the manifest counts
them. The output feature count is verified against the number of distinct
keys, so a wrong grouping fails loudly instead of shipping.
Inputs: input_path (required), output_path (required), by, aggfunc. Returns: object
execute_planAIdempotent
Validate, then execute a geoprocessing plan step by step.
The plan is re-validated first (an invalid plan runs nothing). Steps run in order; "$step_id" references resolve to the outputs of earlier steps. Every step writes its own provenance manifest, and a plan-level manifest (.plan.json, with the plan sha256 and per-step outcomes) ties them together. Execution stops at the first failing step; outputs already produced stay on disk with their manifests. Same plan format as validate_plan — validate first, then execute.
A step_warnings key in the response means the plan ran but some step
produced a suspicious result (an empty output, non-overlapping inputs):
read it before treating a completed plan as a correct one.
Verification failures include structured checks and a three-attempt repair budget. To retry, change the plan yourself, choose NEW output paths and pass the previous .plan.json as repair.previous_manifest. MapSmith never chooses or runs the repair for you; every attempt is linked in the manifests and a fourth is refused.
Inputs: plan (required), repair. Returns: object
explode_layerAIdempotent
Split multi-part geometries into one feature per part (attributes copied).
The output feature count is verified against the number of parts counted before the engine ran, so a lost part fails loudly instead of shipping. Inputs without a CRS are refused.
Inputs: input_path (required), output_path (required). Returns: object
flow_accumulationAIdempotent
D8 flow accumulation from a DEM (GeoTIFF in/out). Depressions are filled first.
out_type: 'cells' (upslope cell count, includes the cell itself) or 'sca' (specific catchment area). log_transform=True for visualization-friendly values. Requires the [whitebox] extra.
Inputs: dem_path (required), output_path (required), out_type, log_transform. Returns: object
get_provenanceARead-onlyIdempotent
Return the manifest of the ONE operation that wrote this dataset.
Its inputs with their digests, the exact parameters, the CRS decisions with
reasons, engine and version, and every deterministic check with its result.
One step, in full. For the whole chain that led here — the operations
behind the inputs, and the ones behind those — the catalogue operation
get_lineage walks it and returns each step summarised instead of one step
complete; run it through run_operation. It is not a tool of its own on
purpose: two exposed tools answering the same question about the same file
is the overlap that makes an agent pick wrong.
Inputs: output_path (required). Returns: object
hillshadeAIdempotent
Shaded relief from a DEM: GeoTIFF in, GeoTIFF out (values scaled 0-32767).
azimuth = sun direction in degrees (default 315, NW); altitude = sun angle above the horizon (default 30). DEMs without a CRS are rejected. Requires the [whitebox] extra.
Inputs: dem_path (required), output_path (required), azimuth, altitude, +1 more. Returns: object
list_operationsARead-onlyIdempotent
Find the operation you need. Say what you have and what you want — it matters more than the words you search with.
Ranking alone does not scale, and this is measured rather than assumed on independently written requests. Declaring what you already know makes ranking less important: when few enough operations survive, the whole set is handed over rather than a ranked shortlist. Delivery is not an accuracy figure: it depends on the surviving set staying small enough to return whole.
So fill these in whenever you know them, and you usually do:
input_kind — what you are holding: 'vector' (points, lines, polygons), 'raster' (a grid, a GeoTIFF), 'dataset' (either), 'plan', or 'none'.
produces — what you want back: 'dataset:vector', 'dataset:raster', 'answer' (a number, nothing written), 'description' (what something IS, rather than a computation over it), 'plan_result'.
category — the family, when you know it: vector, raster, terrain, hydrology, inspection, sql, network, planning, provenance, visualization, bridge. Unlike the others this one only ORDERS the results — a wrong guess about our families costs you positions, never the answer, so guessing is safe.
projected — pass False if your data is in a geographic CRS (degrees), and every operation that would refuse it disappears from the results.
dataset_inputs — how many datasets you are holding for this step: 1 if you have one layer, 2 if the operation combines two. This is the facet that makes a large catalog usable: on the current one it takes the surviving set from a median of 34 to 9, because "clip these parcels with that boundary" and "simplify these parcels" are different questions and you already know which one you have.
geometry — for a vector layer, what it holds: 'point', 'line' or 'polygon' (describe_dataset tells you), or a list for a mixed layer. Operations that cannot take that geometry drop out; operations that take any geometry always stay, so declaring it never hides one that fits. With two layers, list the geometry of both (points and polygons to count points in polygons). Unsure? Leave it out.
query is then plain words for what you are trying to do, and it breaks the
tie inside what is left. Describe the PROBLEM rather than the operation:
"the coastline has too many vertices and the browser dies" works as well as
the name of the tool, and better when you do not know the name.
If the answer comes back as a single entry with status: "choose", that is
the normal case and it is asking you to pick. It carries every operation
that survived, in relevance order, each with the sentence saying what it is
NOT for. The order is a hint and nothing else: our ranking puts the right
operation in the top three 75% of the time, while a model reading the same
candidates and choosing gets its first pick right 69% — and 75% is where the two
model labellers who wrote the ground truth agree with EACH OTHER, so there is
often no single right answer to rank toward. You have context no ranking has: which
file is open, what ran a minute ago, what the person actually asked for. Use
it. And if two candidates would both be defensible, ask them — that is a
better move than picking one silently, and it is what a GIS analyst would do.
A order_is_weak field means the two rankers shared nothing in their top
three, which usually means the request does not match this catalog well: read
the candidates instead of trusting the order, and say so if none of them fits.
If the answer comes back with status: "unsure", the two ranking engines
agreed on nothing and the set was too large to hand over — usually the
request was not understood rather than impossible. It carries both engines'
guesses and a question; answering the question with the facets above is the
fastest way through.
If the answer comes back with status: "none_apply", nothing you declared
can be true at once — no ranking ran. It lists each declaration and how many
operations would come back without it, smallest first, so the one that is
excluding everything is the first line. The common case is produces: several
operations compute the number you want and write it into a column instead of
returning it, so they declare dataset:vector. If nothing in relax helps,
MapSmith probably does not do this — say so rather than running a neighbour.
detail=True adds parameters and worked example calls: use it on the exact
operation name before calling an unfamiliar tool. An empty query lists
everything that survives the facets, planned operations included.
engine selects the ranker and every result says which one ran: 'auto' (the
default) prefers embeddings and falls back to BM25 where the model cannot
load; 'lexical' is BM25 alone, deterministic and network-free; 'vector'
forces embeddings. The default changed on measurement, not preference, and
the facets above matter far more than this choice.
Inputs: limit, query, detail, engine, +6 more. Returns: result
measure_areaAIdempotent
Area per feature in SQUARE METRES, written to a named column, with the total in the result.
method='geodesic' (default) measures ground area on the ellipsoid the layer's CRS names: no map plane, so no projection distortion. method= 'planar' measures in the layer's own CRS and converts with its declared linear unit — a layer in US survey feet is not assumed to be in metres — and is refused on a geographic CRS, where an area would be in square degrees.
Two things this tool does that a bare area call cannot: invalid geometry is
repaired BEFORE measuring (the planar area of a self-intersecting ring is
the signed shoelace, a number matching no region, returned without
complaint) and every repair is recorded; and a planar measurement is
compared against the ground area, so a plane that is not equal-area here
comes back with a warnings entry carrying the ratio — Web Mercator at 42°
reports 1.80× the land it covers.
Inputs: input_path (required), output_path (required), method, area_column. Returns: object
merge_layersAIdempotent
Append two or more layers into one (schema union, attributes aligned by name).
Layers are reprojected to the FIRST layer's CRS when they differ; the decision is recorded in the provenance manifest. Columns present in only some inputs are null-filled in the others and the manifest names them — data that looks measured and is actually absent is a silent error. The output feature count is verified against the sum of the input counts. Inputs without a CRS are refused. This is an append, not a geometric union: use dissolve_layer to merge geometries afterwards.
Inputs: input_paths (required), output_path (required). Returns: object
nearest_joinAIdempotent
Attach each feature's nearest neighbour from another layer, with the distance IN METERS in a named column.
Geographic-CRS inputs are measured in an estimated UTM zone (decision
recorded in the manifest) and returned in the input CRS — a nearest
distance in degrees is the classic silent error of this operation, and it
cannot happen here. max_distance_meters drops pairs farther than that; an
emptied result comes back with a warnings entry, never silently.
Inputs: left_path (required), right_path (required), output_path (required), distance_column, +1 more. Returns: object
overlay_layersAIdempotent
Set-theoretic overlay of two layers: intersection (default), union, identity, symmetric_difference or difference.
The overlay layer is reprojected to the input CRS when they differ; the
decision is recorded in the provenance manifest. Overlay pieces of lower
dimension than the inputs (shared edges, corner contacts) are dropped, and
the manifest says so. Inputs without a CRS are refused; an empty result
comes back with a warnings entry, never as a silent success.
Inputs: input_path (required), output_path (required), overlay_path (required), how. Returns: object
preview_mapARead-onlyIdempotent
Show datasets on the interactive in-chat map panel (MCP Apps).
Pass the paths of one or more MapSmith outputs or source datasets (vector or GeoTIFF). Layers are previewed in EPSG:4326 with simplified geometry and capped feature counts sized to fit client limits; each layer card shows its provenance summary and verification status. Read-only: the datasets of record stay on disk. On clients without MCP Apps support the same payload is returned as structured data.
Inputs: paths (required), max_features. Returns: object
reproject_layerAIdempotent
Reproject a layer to a target CRS, e.g. 'EPSG:32632' or a WKT string.
Inputs without a CRS are refused. Geometry passes through unchanged, so an
invalid input yields an invalid output: mechanically broken geometry is
repaired deterministically and reported in a repairs key — read it, the
geometry type may have changed.
Inputs: input_path (required), target_crs (required), output_path (required). Returns: object
run_operationAIdempotent
Run ANY catalog operation by name, including the ones with no tool of their own — which is most of them, and increasingly so.
The tools above are the handful an agent reaches for constantly. The catalog holds every operation MapSmith can perform, and it grows faster than the tool list on purpose: tool-selection accuracy degrades past a few dozen exposed tools, while capability count has no such ceiling. Discover with list_operations (use detail=true to get parameters and worked examples), then call it here.
Arguments are validated against the catalog BEFORE anything runs — unknown operation, missing or misnamed argument, wrong type, path outside the workspace — and the errors come back with stable codes, so a failed call tells the planner what to fix instead of what went wrong. Execution goes through the same path as execute_plan, so an operation cannot behave one way here and another way in a plan.
Inputs: arguments (required), operation (required). Returns: object
run_sqlADestructive
Run spatial SQL (DuckDB dialect, ST_* functions, read_parquet/ST_Read for files).
Without output_path: returns up to 50 preview rows. With output_path (.parquet): materializes the full result as GeoParquet with a provenance manifest. input_paths declares every dataset read; when omitted, the engine derives them from the query. Under MAPSMITH_WORKSPACE only SELECT runs, and coordinate systems (ST_Transform, ST_SetCRS) and dataset paths (ST_Read, read_parquet) must be string literals, so they can be checked before anything opens them; ST_Read takes there the formats whose coordinate system MapSmith reads first (GeoPackage, OGR SQLite and SpatiaLite with MapSmith-read SRS catalogues, shapefile, GeoParquet, GeoJSON, GML, FlatGeobuf, GeoTIFF, CSV...).
Inputs: query (required), input_paths, output_path. Returns: object
server_infoARead-onlyIdempotent
MapSmith version, licensing, and available engines.
Inputs: no named parameters. Returns: object
simplify_layerAIdempotent
Simplify geometries (Douglas-Peucker, topology preserved) with the drift measured: the manifest records total area and length before and after.
Geographic-CRS inputs are simplified in an estimated UTM zone (decision recorded) and returned in the input CRS — a tolerance in degrees is a different distance at every latitude. On projected CRS the tolerance is interpreted in the CRS units. The feature count is verified unchanged; vertex counts before/after are in the result. Inputs without a CRS are refused.
Inputs: input_path (required), output_path (required), tolerance_meters (required). Returns: object
slopeAIdempotent
Slope gradient from a DEM: GeoTIFF in, GeoTIFF out.
units: degrees (default), percent or radians. DEMs in a geographic CRS are refused — degree cells with meter elevations give plausible but wrong values everywhere; reproject to a projected CRS first. The CRS decision is recorded in the provenance manifest. Requires the [whitebox] extra.
Inputs: dem_path (required), output_path (required), units, z_factor. Returns: object
spatial_joinAIdempotent
Join by spatial predicate (intersects/within/contains).
engine='auto' routes to the fastest available engine for the inputs:
SedonaDB (heavy joins, 10-180x) > DuckDB (GeoParquet fast path) > GeoPandas.
A warnings key in the result flags an empty join or inputs whose extents
do not overlap, each with a hint. Inputs without a CRS are refused.
Inputs: left_path (required), right_path (required), output_path (required), engine, +1 more. Returns: object
validate_planARead-onlyIdempotent
Statically validate a multi-step geoprocessing plan BEFORE running anything.
Write the plan as steps in execution order; each step has a unique id, an operation name from list_operations, and its arguments. Use "$step_id" as an argument value to consume the output dataset of an earlier step. Checks: operations exist and are installed, arguments complete and well-typed, references resolve backwards (mis-ordered steps are rejected), input files exist, outputs don't collide, and CRS flow is simulated end-to-end from the real input files. Returns machine-actionable errors/warnings/notes plus the simulated output CRS per step. Nothing is executed and nothing is written.
Example plan: {"goal": "wells at risk", "steps": [ {"id": "buf", "operation": "buffer_layer", "arguments": {"input_path": "wells.gpkg", "distance_meters": 300, "output_path": "buf.parquet"}}, {"id": "cut", "operation": "clip_layer", "arguments": {"input_path": "$buf", "mask_path": "zone.gpkg", "output_path": "risk.parquet"}}]}
Inputs: plan (required). Returns: object
watershedAIdempotent
Watershed of each pour point: DEM + points in, basin raster out (GeoTIFF).
Basins get 1-based IDs following the pour-point feature order; cells not draining to any point stay nodata. Points are aligned to the DEM CRS automatically (decision recorded). Requires the [whitebox] extra.
Inputs: dem_path (required), output_path (required), pour_points_path (required). Returns: object
zonal_statisticsAIdempotent
Statistics of a raster within each vector zone (exact fractional pixel coverage).
stats: subset of count/sum/mean/median/min/max/stdev/variance/majority/minority/
variety (default: count, mean, min, max). Zones are aligned to the raster CRS
automatically; the decision is recorded in the provenance manifest.
weights_path: a single-band raster of weights on the SAME grid as the values
(same CRS, cells and registration; otherwise refused with how to align it),
for weighted_mean/weighted_sum/weighted_stdev/weighted_variance/weighted_frac --
e.g. mean heat per zone weighted by population (default stats then: count,
mean, weighted_mean). A cell with a value and no weight counts with weight 0,
and the record names the zones where that happened.
Zones without a CRS are refused; warnings and repairs keys in the result
flag a suspicious outcome or geometry MapSmith had to repair.
Requires the [raster] extra.
Inputs: zones_path (required), output_path (required), raster_path (required), stats, +1 more. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 29 tools
Each operation targets a distinct verb+resource (buffer vs clip vs overlay vs dissolve vs merge), and the descriptions actively pre-empt the classic confusions — merge_layers explicitly says 'this is an append, not a geometric union', and get_provenance explains why lineage is deliberately not a second tool. The one real overlap is structural: run_operation can execute any cataloged operation, so it competes with every exposed tool, though the description frames it as a fallback after list_operations. Terrain tools (slope, aspect, hillshade, flow_accumulation, watershed) share DEM inputs but produce clearly different outputs.
The dominant convention is snake_case verb_noun (buffer_layer, convert_format, validate_plan, describe_dataset, get_provenance), applied consistently across the vector, planning, and provenance families. The deviations are the terrain/hydrology tools, which are bare nouns (slope, aspect, hillshade, watershed, flow_accumulation) with no verb, plus server_info. Still highly readable and predictable, just not one uniform pattern.
29 tools is above the comfortable 3-15 band and the set is grouped into many families (terrain, vector, join, SQL, raster stats, planning, provenance, preview, discovery), which puts real load on selection. The design is self-aware — it caps exposure on purpose and routes the long tail through run_operation — and every tool does map to a distinct operation, so nothing is redundant. Still borderline heavy for what could be a smaller hot-path set.
Coverage of the stated geoprocessing domain is broad and lifecycle-aware: geometry ops, overlay, joins, reprojection, format conversion, terrain/hydrology, zonal raster statistics, SQL, inspection, plus a validate/brief/execute planning triad with provenance. Gaps exist at the tool layer — no raster clip/reproject/resample/calculator, no point-creation or network operations — but run_operation plus list_operations makes the full catalog reachable, so these are workarounds rather than dead ends.
Maintenance
Related MCP Connectors
Paid deterministic data-quality and execution-verification tools for AI agents.
Deterministic reasoning stack for AI agents: simulate, decide & compute, plus cross-domain tools.
Verifiable geospatial tools: distances, topology, isochrones, Overture Maps, with sources.
Geodata for any place, inside your agent: map data, terrain, routes, satellite images, GIS files.
Related MCP Servers
AlicenseBqualityCmaintenanceEnables AI agents to become geospatially intelligent assistants with tools for location search, smart routing, round trip planning, reverse geocoding, isochrone analysis, route visualization, geofence management, and interactive map display.812 npm8Apache 2.0- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform geospatial analysis, spatial data processing, vector and raster operations, coordinate transformations, spatial statistics, mapping, and access to climate, satellite, and other geospatial data through MCP-compatible clients.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to directly operate ArcGIS Pro through natural language, giving access to 2,500+ spatial analysis tools across 46 toolboxes via the Model Context Protocol.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to inspect geospatial vector and raster metadata and run bounded analysis on administrator-registered datasets, including planar buffering, clipping, spatial joins, and PNG map rendering delivered as checksummed artifacts. All data access is read-only and controlled through a curated dataset catalog.Apache 2.0