inkscape-mcp

Overview Schema Source Related Servers Discussions Admin

export_png

Export an SVG document to PNG via Inkscape with validated, allowlisted options for area, DPI, size, color mode, and output path.

Instructions

Exports an SVG document to PNG through Inkscape using only bounded, allowlisted options.

Input Schema

Name	Required	Default
`dpi`	No
`area`	No	page
`path`	Yes
`width`	No
`height`	No
`pageId`	No
`antialias`	No
`colorMode`	No
`dithering`	No
`background`	No	document
`customArea`	No
`outputPath`	Yes
`compression`	No
`selectionId`	No
`workspaceId`	Yes
`allowDistortion`	No
`backgroundColor`	No
`expectedRevision`	Yes
`snapAreaToPixels`	No
`backgroundOpacity`	No
`expectedOutputRevision`	No

Output Schema

Name	Required	Description	Default
`area`	Yes
`dpiX`	No
`dpiY`	No
`hash`	Yes
`width`	Yes
`height`	Yes
`pageId`	No
`bitDepth`	Yes
`revision`	Yes
`colorType`	Yes
`background`	Yes
`byteLength`	Yes
`selectionId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedv0.1.0Oct 14, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / allowDistortion

Added value: +{
+  "default": false,
+  "type": "boolean"
+}

addedInput schema / properties / antialias

Added value: +{
+  "maximum": 3,
+  "minimum": 0,
+  "type": "integer"
+}

changedInput schema / properties / area / enum

Previous value: -[
-  "drawing",
-  "page"
-]New value: +[
+  "custom",
+  "drawing",
+  "page",
+  "selection"
+]

addedInput schema / properties / colorMode

Added value: +{
+  "enum": [
+    "Gray_1",
+    "Gray_2",
+    "Gray_4",
+    "Gray_8",
+    "Gray_16",
+    "RGB_8",
+    "RGB_16",
+    "GrayAlpha_8",
+    "GrayAlpha_16",
+    "RGBA_8",
+    "RGBA_16"
+  ],
+  "type": "string"
+}

addedInput schema / properties / compression

Added value: +{
+  "maximum": 9,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / customArea

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "height": {
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "width": {
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "x": {
+      "type": "number"
+    },
+    "y": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "height",
+    "width",
+    "x",
+    "y"
+  ],
+  "type": "object"
+}

addedInput schema / properties / dithering
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / pageId

Added value: +{
+  "pattern": "^[A-Za-z_][A-Za-z0-9_.-]{0,127}$",
+  "type": "string"
+}

addedInput schema / properties / selectionId

Added value: +{
+  "pattern": "^[A-Za-z_][A-Za-z0-9_.-]{0,127}$",
+  "type": "string"
+}

addedInput schema / properties / snapAreaToPixels
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / properties / area / enum

Previous value: -[
-  "drawing",
-  "page"
-]New value: +[
+  "custom",
+  "drawing",
+  "page",
+  "selection"
+]

addedOutput schema / properties / bitDepth

Added value: +{
+  "anyOf": [
+    {
+      "const": 1,
+      "type": "number"
+    },
+    {
+      "const": 2,
+      "type": "number"
+    },
+    {
+      "const": 4,
+      "type": "number"
+    },
+    {
+      "const": 8,
+      "type": "number"
+    },
+    {
+      "const": 16,
+      "type": "number"
+    }
+  ]
+}

addedOutput schema / properties / byteLength

Added value: +{
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}

addedOutput schema / properties / colorType

Added value: +{
+  "anyOf": [
+    {
+      "const": 0,
+      "type": "number"
+    },
+    {
+      "const": 2,
+      "type": "number"
+    },
+    {
+      "const": 3,
+      "type": "number"
+    },
+    {
+      "const": 4,
+      "type": "number"
+    },
+    {
+      "const": 6,
+      "type": "number"
+    }
+  ]
+}

addedOutput schema / properties / hash

Added value: +{
+  "pattern": "^[a-f0-9]{64}$",
+  "type": "string"
+}

addedOutput schema / properties / pageId

Added value: +{
+  "pattern": "^[A-Za-z_][A-Za-z0-9_.-]{0,127}$",
+  "type": "string"
+}

addedOutput schema / properties / selectionId

Added value: +{
+  "pattern": "^[A-Za-z_][A-Za-z0-9_.-]{0,127}$",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "area",
-  "background",
-  "height",
-  "revision",
-  "width"
-]New value: +[
+  "area",
+  "background",
+  "bitDepth",
+  "byteLength",
+  "colorType",
+  "height",
+  "hash",
+  "revision",
+  "width"
+]

First observedv0.0.0Aug 26, 2026

TDQS

C2.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only carry destructiveHint=false, so the description must shoulder most of the behavioral burden. It usefully discloses that conversion runs through Inkscape with 'bounded, allowlisted options', which is real context beyond the annotation. However, it omits overwrite behavior for outputPath, the meaning of the expectedRevision/expectedOutputRevision preconditions, and that this is a file-writing operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, stating the transformation and the execution constraint immediately. It earns its place but is arguably under-sized for a 21-parameter mutation tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, but the description is too thin for a 21-parameter, 4-required export operation: no revision-precondition guidance, no overwrite/error semantics, and no routing to sibling export tools. Given the tool's complexity, more was needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 21 parameters, including a nested customArea object and three enums, and the description explains none of them. The vague 'bounded, allowlisted options' phrase hints at constrained values but names no parameter, so it does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (exports), source resource (SVG document) and target format (PNG), so an agent can distinguish it from export_svg and export_pdf without opening a schema. It stops short of explicitly naming which sibling export to prefer, so it is not a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no mention of alternatives (export_svg, export_pdf, document_export_batch), and no prerequisites or preconditions for the required revision/workspace parameters. The 'through Inkscape' clause explains mechanism, not when to select this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server