Most of what it does is ordinary GIS chores — load these layers, run that algorithm, render the view — carried out by describing them instead of clicking through them. The code-execution tool makes the range open-ended: anything PyQGIS can do, it can do, which is why this belongs on a desktop you control rather than a shared machine.
A QGIS plugin plus a local server: the plugin opens a socket server inside QGIS, the server speaks MCP to your client and relays commands to it. With both running, an assistant can create or load a project, add and remove layers, run Processing algorithms and render the map in the instance in front of you. The project is built on the approach of BlenderMCP.
- Projects created, loaded and saved at a path you name
- Vector and raster layers added, listed, removed and zoomed to
- Features read back out of a vector layer, with a limit you set
- Any algorithm in the Processing Toolbox run with your parameters
- The current map view rendered out to an image file
- Arbitrary PyQGIS code executed inside the application — the widest tool in the set, and the one to decide about deliberately
- A connectivity check and a report on the QGIS installation it is attached to
QGIS with the plugin folder copied into your QGIS profile and enabled from the plugin manager, Python with the uv package manager for the server side, and the socket server started from the plugin's own menu before your client connects. The author reports testing against a single QGIS release.