Import images with the ConvertSite MCP

The ConvertSite MCP brings images into your workspace two ways: the Upload an image from a URL tool downloads an image from an https:// link and stores it as a workspace asset, and table writes through the MCP automatically convert external image URLs into workspace assets before saving. You ask your connected assistant in plain language; it calls the MCP tools for you.

What you need

Connect Claude or Codex to ConvertSite first. The upload tool is a write operation, so the connection needs write access: the convert:apps.write scope granted during the standard connection. Table conversion runs inside the same write operations, so the same connection covers both.

The upload also needs an active app session context, meaning the assistant is working inside a ConvertSite app when it calls the tool.

New to the connection? See Connect ConvertSite MCP to Claude or Connect ConvertSite MCP to Codex.

Upload an image from a URL

The Upload an image from a URL tool takes one input, a URL, and stores the image at that address as a real workspace asset. The asset belongs to your workspace, not to the conversation, so it stays available to your apps.

Paste the image URL into your conversation and ask your assistant to upload it to ConvertSite.
The assistant calls Upload an image from a URL with the URL you provided.
The tool downloads the image, stores it as a workspace asset, and returns an asset value containing the stored workspace asset key.

When you ask the built-in ConvertSite assistant to search for images, it recommends passing a selected Pexels image URL to the upload tool so the image becomes a permanent workspace asset instead of staying tied to its source URL.

Use the asset key in your app

Use the returned asset key with the existing src-asset property syntax when authoring app content. The image then loads from workspace storage instead of the original website, so it keeps working even if the original URL changes or the page disappears.

The same asset works anywhere an Image element can point at an asset. See Image for how the element sources its picture.

Supported image types and limits

The upload tool enforces these rules before it stores an image:

Only https:// URLs are accepted. The check runs on ConvertSite's servers, so a plain http:// link fails even if the image is reachable.
Supported image types: JPEG, PNG, WebP, GIF, AVIF, and SVG. The server hosting the image must declare one of these image content types in its response.
Maximum image size: 5 MiB. Larger images fail with an error instead of being truncated.
SVG files are sanitized before storage: scripts and external references are stripped, so an SVG cannot run code in your app.

When an upload fails

The tool reports one of these errors. Match the message to the cause below and fix the URL or the file, then ask your assistant to try again.

Error message	Cause
`invalid or unsafe url`	The URL is malformed, is not `https`, has no host, or does not resolve to a public address.
`could not fetch url`	ConvertSite could not download the image: the request failed, the server returned a non-success status, or it sent a redirect that was not followed.
`file too large`	The image is larger than 5 MiB.
`invalid content type`	The server's response is not one of the supported image types.
`could not sanitize svg`	An SVG file could not be safely cleaned before storage.

Image URLs in table writes

When your assistant writes or edits a table through the MCP, every external URL found in an Image column cell is downloaded and replaced with a workspace asset reference before the table is saved. You do not need to call the upload tool separately for table data: supplying ordinary image URLs in the rows is enough.

Values that are already asset references rather than URLs are left unchanged. The converted images are served from ConvertSite as workspace assets, so a row no longer depends on the original external URL staying alive.

This conversion applies to rows supplied through the MCP connection. The visual table editor is unaffected: images you add there yourself work as before.

Was this helpful?