local-comfyui-mcp

Overview Schema Source Related Servers Score Discussions Admin

reload_workspace

Reload the ComfyUI browser tab to apply changed extension JavaScript, then wait for it to reconnect before continuing. Use force to bypass the browser's unsaved-changes confirmation.

Instructions

Reload the ComfyUI browser tab, and wait for it to come back.

This is the fix for exactly one thing: changed extension JavaScript. The bridge's own JS, and every node pack's, is served from disk on each page load and never re-read otherwise, so editing it takes a reload and nothing else - restarting ComfyUI would cost minutes and achieve the same thing by accident. Installing or upgrading a node is the opposite case and needs restart_comfy, because Python packs are imported once at startup.

It waits for the tab to register again rather than firing and returning, for the reason open_workspace does: a page part-way through loading fails exactly like no page at all.

The browser can refuse. ComfyUI asks "Leave site?" when a workflow has unsaved edits, and that dialog waits for a human - nothing here can dismiss it. So a tab with edits is refused by default; force reloads anyway, having first written the canvas to the export directory so nothing can be lost. Opening a second tab is the other way round the problem: a new tab loads the current JavaScript without disturbing this one.

Args: wait: seconds to wait for the tab to reconnect. 0 returns immediately. force: reload even though the browser may put a confirmation on screen. client_id: which tab, when several are open. Defaults to the focused one.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`wait`	No
`force`	No
`client_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 13, 2026

TDQS

A5/5.0

Behavior5/5

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

With no annotations provided, the description fully carries the behavioral disclosure burden. It discloses that the tool waits for tab registration, may be refused by the browser's 'Leave site?' dialog on unsaved edits, and that force writes the canvas to the export directory before reloading.

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?

The description is appropriately sized and well-structured, with each paragraph serving a distinct purpose: the core action, the waiting rationale, the browser refusal edge case, and parameter details. It avoids redundancy and is front-loaded with the primary verb and resource.

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

Completeness5/5

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

The description covers all necessary context: the exact purpose, the failure mode when a page is half-loaded, the browser confirmation issue, the force fallback, and the client_id default behavior. Given the output schema exists, no return value explanation is required. The description is complete for this tool's complexity.

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

Parameters5/5

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

The description's Args section provides complete semantic meaning for all three parameters: wait seconds, force bypass confirmation, and client_id to select a tab. This fully compensates for the 0% schema description coverage.

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?

The description clearly states the tool reloads the ComfyUI browser tab and waits for it to return. It explicitly defines the specific fix scenario (changed extension JavaScript) and distinguishes itself from restart_comfy by contrasting with node installation upgrades.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool (changed extension JavaScript) and when not to (node installation/upgrades requiring restart_comfy). It also provides an alternative (opening a second tab) and explains the force option for dealing with unsaved edits.

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

Install Server