Mapsuke lets you work with your QGIS project through a chat with Claude Code or Codex.
Mapsuke running in QGIS. Map data © OpenStreetMap contributors (ODbL). Contains modified Copernicus Sentinel data 2026.
- No MCP setup: Connect your agent to QGIS directly.
- Your own agent: Use your Claude Code or Codex CLI login, or an API key.
- Python in QGIS: The agent runs Python with QGIS and Processing tools. This code has the same file and network permissions as QGIS; review it before running it.
- Processing tools as skills: The agent discovers the Processing tools available in QGIS and uses them like skills.
- Reusable workflows: Save routine operations as Processing scripts.
- Install QGIS 3.44 or later and Claude Code or the Codex CLI.
- Install and enable the Mapsuke plugin, then open it from the Plugins menu or toolbar.
- Select New session, choose Claude or Codex, and log in if prompted.
- Enter a request such as “Add a point in Sapporo.” In Ask mode, approve the generated Python before it runs.
If QGIS cannot find the CLI, set its path in Mapsuke's settings. At each session start or restore, Mapsuke first checks that the selected CLI executable is available and its user configuration directory exists. If either cannot be confirmed, or an existing skills path is not a directory, skill synchronization and its prompt are skipped; install/run the CLI or correct its configured path before starting another session. When these checks pass, Mapsuke offers to save any missing bundled mapsuke-* skills for the selected CLI. Existing same-named bundled skills are overwritten with the bundled versions on every session start or restore, including local edits. Declining skips creation of missing skills and the offer returns at the next session start while they are missing; existing copies are still updated. Unrelated skill folders are left alone. Review and remove legacy qgis-* copies and the retired mapsuke-create-report and mapsuke-save-processing-script skills from the CLI skills folders if no longer needed.