QGIS MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QGIS_MCP_HOST | No | Host address for the MCP bridge (default: 127.0.0.1). Set if you need a different host. | 127.0.0.1 |
| QGIS_MCP_PORT | No | Port for the MCP bridge (default: 9876). Set if you need a different port. | 9876 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_layer_summaryA | Summarize a layer in one call: feature count, geometry type, CRS, extent, and fields. Replaces the usual five round-trips (layer_info + list_fields + samples)
with a single response. For vector layers, each field comes with up to 3
example values pulled from the first features scanned - not a full
distinct-value enumeration. Raster layers get the shared metadata
(id/name/type/crs/extent) with |
| filter_layer_by_expressionA | Set a QGIS expression as the layer's subset filter (subset string). Only features matching |
| select_features_by_expressionB | Select features on a layer matching a QGIS expression, e.g. "pop" > 1000.
|
| get_layer_extent_wktA | Get a layer's extent as both a bbox and ready-to-use WKT polygon. Useful as an input to a following step, e.g. clip_layer_to_extent or a Processing algorithm that takes a geometry parameter. |
| reproject_layerA | Reproject a vector layer to a new CRS, saving the result as a new layer. The original layer is left untouched. The new in-memory layer is added
to the project and validated: |
| clip_layer_to_extentA | Clip a layer to a bounding-box extent, saving the result as a new layer. Provide exactly one of |
| merge_layersA | Merge multiple vector layers of the same geometry type into one new layer. Fails with GeometryTypeMismatch if the layers don't all share one
geometry type. |
| get_field_statisticsA | Get min/max/mean/sum and distinct-value count for a numeric field. Fails with UnsupportedFieldType if the field isn't numeric. Also includes a capped preview of distinct values seen on the field. |
| add_field_with_valuesB | Add a new field and populate every feature from a QGIS expression, in one step.
|
| export_layerA | Export a layer to GeoJSON, Shapefile, GPKG, or CSV.
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: summary, filtering, selection, extent retrieval, reprojection, clipping, merging, statistics, field addition, and export. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., get_layer_summary, filter_layer_by_expression, reproject_layer. No mixing of conventions.
10 tools is well-scoped for a GIS MCP server covering common operations: information, filtering, selection, manipulation, and export. Not too few or too many.
Covers core data manipulation but lacks a tool to list available layers, which is a notable gap. Missing delete field/update field operations, but add and export are present.