QGIS MCP Server
Related Servers
Alternatives to QGIS MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceConnects QGIS to any MCP-speaking AI agent, exposing 125 tools that let the agent manage layers, edit features, run processing algorithms, render and style maps, author layouts and atlases, query across layers with SQL, and administer the QGIS session. Works with any MCP client and QGIS 3.28–4.x.GPL 2.0
- AlicenseNot gradedqualityBmaintenanceEnables any MCP-speaking AI agent to drive QGIS directly by managing layers, editing features, running processing algorithms, rendering maps, and authoring layouts through 125 tools. It bridges agents to a running QGIS instance over a plugin socket connection, supporting QGIS 3.28-4.x and virtually any MCP client.1GPL 2.0
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants (Claude, Cursor, etc.) to QGIS 4.x via MCP, enabling natural language-driven GIS workflows through 37+ tools, including data loading, processing, and spatial analysis.GPL 2.0
- AlicenseBqualityAmaintenanceAn MCP server that enables AI assistants to directly control QGIS for tasks like layer management, feature editing, and map rendering. It provides a suite of 50 tools to execute processing algorithms and manage GIS projects through natural language commands.125429GPL 2.0
- AlicenseBqualityCmaintenanceEnables MCP clients to control QGIS by executing PyQGIS commands, managing layers and projects, exporting maps, and running Processing algorithms through either a GUI plugin or a headless Python process.13MIT
- AlicenseAqualityDmaintenanceConnect QGIS to Claude AI through the Model Context Protocol (MCP), enabling Claude to directly control QGIS — manage layers, edit features, run processing algorithms, render maps, and more.1001MIT
TDQS
Scored across 125 tools
Most tools target distinct QGIS resources and actions, and the descriptions explicitly distinguish close pairs such as execute_sql vs execute_connection_sql and execute_processing vs start_processing_job. However, with 125 tools there are many overlapping subdomains (styling, processing, layer inspection, expression evaluation, editing), so an agent can still hesitate between several plausible tools.
The set is consistently snake_case, and most tools follow a verb_noun or action_resource pattern such as get_layer_features, add_vector_layer, or set_layer_style. There are minor deviations with noun-first tools like raster_calculator, spatial_join, batch_commands, and ping, plus some add/create and remove/delete variation.
125 tools is an extreme mismatch for a single MCP server surface, far beyond the typical well-scoped range. Even though QGIS is a large domain, the set should be grouped or narrowed; the current count creates substantial selection and context burden.
The surface is very broad, covering layers, features, editing, styling, processing, layouts, CRS, bookmarks, themes, connections, and diagnostics. Some lifecycle operations are still missing or partial, such as deleting layer groups or updating/removing individual layout items, but these are minor gaps given the overall coverage.