AppStrings.How it works
APPLICATION × AGENT

Codex QGIS integration

A QGIS plugin and MCP server connect map data, processing and layout workflows. For Codex, 2 routes are explicitly documented by the integration maintainer.

Connection options for Codex

MCP · Live app

QGIS MCP · processing & layouts

A QGIS plugin and MCP server connect map data, processing and layout workflows.

Platforms: Windows, macOS, Linux

Codex · Documented

The maintainer documents Codex setup for this connection.

Requirements and limitations

A supported QGIS 3.28–4.x installation, uv and the companion plugin and server.

The plugin must be enabled in QGIS. Algorithm availability depends on installed processing providers.

MCP · Live app

QGIS MCP · PyQGIS bridge

A QGIS plugin connects project and processing operations to a Python MCP server.

Platforms: See documentation

Codex · MCP compatible

MCP transport compatibility is inferred; this agent is not explicitly documented for this connection.

Requirements and limitations

QGIS 3.x, Python 3.10+, uv and the companion QGIS plugin.

Requires the plugin in QGIS; arbitrary PyQGIS execution depends on the running application environment.

API · Live & file workflows

PyQGIS

PyQGIS provides Python access through the console, plugins and standalone scripts.

Platforms: Windows, macOS, Linux

Codex · Not documented

The native interface is documented, but no setup for this coding agent is established by this source.

Requirements and limitations

QGIS Python bindings with the correct application paths and environment; live control needs an in-app script or plugin.

Standalone scripts and the QGIS console have different environments. An agent-facing bridge is not included.

MCP · Live app

AgenticGIS MCP

A QGIS plugin with an MCP bridge for map analysis and project editing.

Platforms: Windows, macOS, Linux

Codex · Documented

The integration documentation explicitly names this client.

Requirements and limitations

QGIS with the AgenticGIS plugin enabled; Python 3.9 or newer for the optional stdio proxy.

The local MCP server controls the open QGIS project; optional external services have separate requirements.

Compare the actual routes

IntegrationCodex compatibilityRequirements
QGIS MCP · processing & layoutsDocumented setup Setup guide A supported QGIS 3.28–4.x installation, uv and the companion plugin and server.
QGIS MCP · PyQGIS bridgeMCP compatibility (inferred) Setup guide QGIS 3.x, Python 3.10+, uv and the companion QGIS plugin.
PyQGISNot documented QGIS Python bindings with the correct application paths and environment; live control needs an in-app script or plugin.
AgenticGIS MCPDocumented setup Setup guide QGIS with the AgenticGIS plugin enabled; Python 3.9 or newer for the optional stdio proxy.

Can Codex control all of QGIS?

The sources establish the capabilities listed above, not complete application coverage. Check each bridge’s limitations and your application version before starting.

Which setup should I use?

Choose a route that explicitly documents Codex and matches your environment. Start with the maintainer’s setup guide and a disposable project copy. Shared MCP support alone is listed as an inference.

All QGIS integrations