Skip to main content
Glama
sandraschi

comfyops-mcp

by sandraschi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

comfy_workflows

List, search, register, validate, and retrieve curated ComfyUI workflow definitions to reuse and manage image/video generation pipelines without the node editor.

Instructions

Manage curated ComfyUI workflow definitions.

Return Format

{"success": bool, "workflows": [...], "workflow": {...}, "sources": [...], "message": str}

Examples

comfy_workflows(operation="list")
comfy_workflows(operation="search", query="flux", tags="video")
comfy_workflows(operation="discover")
comfy_workflows(operation="register", workflow_id="my-wf",
                workflow_json='{"3":{"class_type":"KSampler",...}}',
                tags="t2i,portrait", source_url="https://civitai.com/...")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoDisplay name for register.
tagsNoComma-separated tags for search/register.
queryNoSearch text for search operation.
operationYesOperation to perform.
source_urlNoOriginal source URL for register.
descriptionNoDescription for register.
workflow_idNoWorkflow ID for get/validate/register.
workflow_jsonNoJSON string for register.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

There are no annotations, so the description carries the full behavioral burden. It provides a return-format sketch and examples, but it does not disclose side effects (e.g., whether register persists data, whether discover pulls remote sources) or any safety, auth, or rate-limit behavior.

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?

The description is compact and well-organized with a one-line purpose, a Return Format block, and a few representative examples. The 'Manage' verb is generic, but the structure earns its place without redundancy.

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

Completeness3/5

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

Given six operations and eight parameters, the description omits explicit guidance for get and validate, and it does not state which parameters are relevant per operation beyond examples and schema hints. The presence of an output schema reduces the need to document return values, but behavior and operation selection remain under-specified.

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

Parameters3/5

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

The input schema already documents all eight parameters with 100% coverage, so the description need not repeat them. The examples do illustrate sensible combinations like operation='search' with query and tags, but no new parameter meaning is added beyond the schema.

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?

The phrase 'Manage curated ComfyUI workflow definitions' names a clear resource and general action, and the examples show concrete operations such as list, search, discover, and register. It does not explicitly contrast with sibling tools like comfy_library or comfy_generate, so it stops short of 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 Guidelines3/5

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

Usage is implied by the operation enum and examples, but the description never states when to prefer this tool over siblings or how to choose among list, search, discover, get, and validate. There are no explicit exclusions or alternative recommendations.

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

Deploy Server

Other Tools