QGISMCP connects [QGIS](https://qgis.org/) to [Claude AI](https://claude.ai/chat) through the [Model Context Protocol
If you want an AI assistant working directly with Qgis MCP, the qgis mcp mcp server is the bridge. QGISMCP connects QGIS to Claude AI through the Model Context Protocol (MCP), allowing Claude to directly interact with and control QGIS. This integration enables prompt assisted project.
QGISMCP connects QGIS to Claude AI through the Model Context Protocol (MCP), allowing Claude to directly interact with and control QGIS. This integration enables prompt assisted project creation, layer loading, code execution and more.
Once connected, the assistant can call these 14 tools directly:
ping — Simple ping command to check server connectivityget_qgis_info — Get QGIS information about the current installationload_project — Load a QGIS project from the specified pathcreate_new_project — Create a new project and save itget_project_info — Get current project informationadd_vector_layer — Add a vector layer to the projectadd_raster_layer — Add a raster layer to the projectget_layers — Retrieve all layers in the current projectremove_layer — Remove a layer from the project by its IDzoom_to_layer — Zoom to the extent of a specified layerget_layer_features — Retrieve features from a vector layer with an optional limitexecute_processing — Execute a processing algorithm with the given parameterssave_project — Save the current project to the given pathrender_map — Render the current map view to an image fileSetup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.
Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Qgis MCP sits in that group, and the shape of its toolset — ping, get_qgis_info, load_project among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| ping | Simple ping command to check server connectivity |
| get_qgis_info | Get QGIS information about the current installation |
| load_project | Load a QGIS project from the specified path |
| create_new_project | Create a new project and save it |
| get_project_info | Get current project information |
| add_vector_layer | Add a vector layer to the project |
| add_raster_layer | Add a raster layer to the project |
| get_layers | Retrieve all layers in the current project |
| remove_layer | Remove a layer from the project by its ID |
| zoom_to_layer | Zoom to the extent of a specified layer |
| get_layer_features | Retrieve features from a vector layer with an optional limit |
| execute_processing | Execute a processing algorithm with the given parameters |
| save_project | Save the current project to the given path |
| render_map | Render the current map view to an image file |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.