Skip to main content
Glama

upload_image

Upload an image to ComfyUI for use in img2img, ControlNet, or IP-Adapter workflows. Accepts a source URL or base64-encoded data, returns the stored filename for LoadImage nodes.

Instructions

Upload a reference image to ComfyUI for use in img2img, ControlNet, or IP-Adapter workflows. Accepts either a source URL (will be fetched) or base64-encoded image data. Returns the stored filename for use as 'image' in workflow nodes like LoadImage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_urlNoURL to fetch the image from. One of source_url or image_base64 is required.
image_base64NoBase64-encoded image data (without the data:image/... prefix). One of source_url or image_base64 is required.
filenameNoFilename to save as on the ComfyUI side. Defaults to a timestamped name.
overwriteNoReplace an existing file with the same name

Implementation Reference

  • The tool handler function for "upload_image". It accepts source_url or image_base64, delegates to client.fetchAndUploadImage or client.uploadImage, and returns the uploaded filename/subfolder/type.
    async (args) => {
      if (!args.source_url && !args.image_base64) {
        throw new Error("Must provide either source_url or image_base64");
      }
    
      const result = args.source_url
        ? await client.fetchAndUploadImage(args.source_url, args.filename)
        : await client.uploadImage(
            Buffer.from(args.image_base64!, "base64"),
            args.filename ?? `upload-${Date.now()}.png`,
            { overwrite: args.overwrite },
          );
    
      return {
        content: [
          {
            type: "text" as const,
            text: `Uploaded: ${result.name} (subfolder: ${result.subfolder || "(root)"}, type: ${result.type})`,
          },
        ],
      };
    },
  • Zod schema for upload_image tool parameters: source_url, image_base64, filename, and overwrite.
    const uploadImageSchema = {
      source_url: z
        .string()
        .url()
        .optional()
        .describe("URL to fetch the image from. One of source_url or image_base64 is required."),
      image_base64: z
        .string()
        .optional()
        .describe(
          "Base64-encoded image data (without the data:image/... prefix). One of source_url or image_base64 is required.",
        ),
      filename: z
        .string()
        .optional()
        .describe("Filename to save as on the ComfyUI side. Defaults to a timestamped name."),
      overwrite: z
        .boolean()
        .default(false)
        .describe("Replace an existing file with the same name"),
    };
  • The registerImageTools function that calls server.tool('upload_image', ...) to register the tool.
    export function registerImageTools(
      server: McpServer,
      client: ComfyUIClient,
    ): void {
      server.tool(
        "upload_image",
        "Upload a reference image to ComfyUI for use in img2img, ControlNet, or IP-Adapter workflows. Accepts either a source URL (will be fetched) or base64-encoded image data. Returns the stored filename for use as 'image' in workflow nodes like LoadImage.",
        uploadImageSchema,
        async (args) => {
          if (!args.source_url && !args.image_base64) {
            throw new Error("Must provide either source_url or image_base64");
          }
    
          const result = args.source_url
            ? await client.fetchAndUploadImage(args.source_url, args.filename)
            : await client.uploadImage(
                Buffer.from(args.image_base64!, "base64"),
                args.filename ?? `upload-${Date.now()}.png`,
                { overwrite: args.overwrite },
              );
    
          return {
            content: [
              {
                type: "text" as const,
                text: `Uploaded: ${result.name} (subfolder: ${result.subfolder || "(root)"}, type: ${result.type})`,
              },
            ],
          };
        },
      );
  • src/server.ts:11-11 (registration)
    Import of registerImageTools from ./tools/images.js.
    import { registerImageTools } from "./tools/images.js";
  • src/server.ts:46-46 (registration)
    Invocation of registerImageTools(s, client) to register the tool on the MCP server.
    registerImageTools(s, client);
  • ComfyUIClient.uploadImage — sends image data as multipart/form-data to ComfyUI's /upload/image endpoint.
    async uploadImage(
      data: Buffer | Uint8Array,
      filename: string,
      options: { overwrite?: boolean; subfolder?: string } = {},
    ): Promise<UploadResult> {
      const form = new FormData();
      const blob = new Blob([new Uint8Array(data)], { type: "image/png" });
      form.append("image", blob, filename);
      form.append("overwrite", options.overwrite ? "true" : "false");
      if (options.subfolder) form.append("subfolder", options.subfolder);
    
      const res = await fetch(`${this.baseUrl}/upload/image`, {
        method: "POST",
        body: form,
      });
      if (!res.ok) {
        throw new Error(
          `ComfyUI image upload failed: ${res.status} ${await res.text()}`,
        );
      }
      return (await res.json()) as UploadResult;
    }
  • ComfyUIClient.fetchAndUploadImage — fetches an image from a URL first, then calls uploadImage.
    async fetchAndUploadImage(
      sourceUrl: string,
      filename?: string,
    ): Promise<UploadResult> {
      const res = await fetch(sourceUrl);
      if (!res.ok) {
        throw new Error(
          `Failed to fetch source image ${sourceUrl}: ${res.status}`,
        );
      }
      const buffer = Buffer.from(await res.arrayBuffer());
      const name = filename ?? deriveFilename(sourceUrl);
      return this.uploadImage(buffer, name);
    }
  • deriveFilename — extracts a filename from a URL or falls back to a timestamped name.
    function deriveFilename(sourceUrl: string): string {
      try {
        const url = new URL(sourceUrl);
        const last = url.pathname.split("/").pop() ?? "";
        if (last && /\.(png|jpg|jpeg|webp)$/i.test(last)) return last;
      } catch {
        // fall through
      }
      return `upload-${Date.now()}.png`;
    }
  • UploadResult interface: name, subfolder, type fields returned by the upload.
    export interface UploadResult {
      name: string;
      subfolder: string;
      type: string;
    }
Behavior3/5

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

No annotations; description adds that URL is fetched and output filename is for workflow nodes. Lacks details on limits, supported formats, or side effects beyond overwrite param.

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

Conciseness5/5

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

Two sentences, efficient, no redundancy, front-loaded with purpose.

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

Completeness4/5

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

With no output schema or annotations, description adequately covers purpose, input options, and output use. Missing error cases or format constraints, but still sufficient.

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

Parameters4/5

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

Schema coverage 100%; description adds mutual exclusivity of source_url and image_base64, fetch behavior, and output usage context beyond schema basics.

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

Purpose5/5

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

Clear verb 'upload' with specific resource 'reference image to ComfyUI' and explicit use cases (img2img, ControlNet, IP-Adapter). Distinguishes from sibling generation tools.

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

Usage Guidelines4/5

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

Specifies two input methods and purpose, but no explicit when-to-use vs alternatives. Context is clear enough for an upload tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/miller-joe/comfyui-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server