A community MCP server offers structured SVG inspection, editing and export, with optional control of a running Inkscape instance. For Codex, 2 routes are explicitly documented by the integration maintainer.
Uses MCP; agent-specific setup instructions are not included in the linked documentation.
Requirements and limitations
Python 3.12+, uv or pipx, a permitted SVG workspace, and Inkscape 1.4.x on PATH for rendering, export and geometry operations.
Headless-first does not mean every desktop operation is available. Optional live mode and advanced actions have distinct requirements; review the maintainer documentation.
Linux, Inkscape, its extension and the documented Python dependencies.
Can Codex control all of Inkscape?
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.