Issues single-use HTTPS upload endpoints for local image files. Requires a user who can upload files (`upload_files`). Never download or base64-encode the image yourself; run the returned curl command so bytes go directly to WordPress. Use this tool only if you can run a shell command (curl) or send an HTTP request yourself; otherwise use `elementor/upload-media` for images with a public HTTPS URL, or ask the user to upload in WP Admin → Media → Add New. The upload token is sent in a header, not in the URL. Requires explicit user consent: the `consent` flag is only a prompt-level hint, and real approval comes from the MCP client asking the user to confirm the tool call.

- One token is issued per file. Pass `count` (default 1, maximum 10) and use one entry of `uploads` per file; the top-level fields repeat the first entry. Each token works once and expires after 10 minutes. A token is used up as soon as an upload request reaches the server, so a failed upload (wrong file type, size over the limit, checksum mismatch, interrupted transfer) needs a new token. Up to 20 unused tokens can exist per user at a time.
- Replace `/path/to/your/image-file` in the curl command with the real file path. Any extension works because the file type is detected from the content: JPEG, PNG, GIF, WebP and AVIF are accepted, and SVG only for administrators (`manage_options`) on sites that turned on Elementor's unfiltered file uploads.
- Optional request headers: `X-Elementor-Mcp-Upload-Filename`, `X-Elementor-Mcp-Upload-Sha256` (hex checksum, verified on the server), `X-Elementor-Mcp-Upload-Title` and `X-Elementor-Mcp-Upload-Alt` (up to 255 characters each).