A
licenseNot graded
qualityD
maintenanceEnables AI agents to generate images and videos through natural language by exposing ComfyUI workflows as parameter-configurable MCP tools.
9
MIT
Lingie.Mcp
by MechaBabyAi
Related Servers
Alternatives to Lingie.Mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceExposes litmedia.ai text-to-image and image-to-video generation tools via MCP, enabling AI agents to generate images and videos directly from prompts.1MIT
- AlicenseNot gradedqualityBmaintenanceA lightweight MCP server that bridges AI agents with a local ComfyUI instance, enabling them to generate and iteratively refine images, audio, and video through conversational tool calls.22 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to generate and iteratively refine images, audio, and video through natural conversation using a local ComfyUI instance.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to generate and iteratively refine images, audio, and video through natural conversation using a local ComfyUI instance.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to generate and edit images using local Stable Diffusion models in ComfyUI, with tools for text-to-image, img2img, ControlNet, UI frames, upscaling, and background removal—no cloud API or API key required.MIT
TDQS
A4.2/5.0
Scored across 8 tools
Disambiguation4/5
Each tool has a clearly distinct role in the workflow lifecycle: health check, listing workflows, inspecting parameters, running, polling, downloading, canceling, and uploading. The only real overlap is between lingie_run_result and lingie_run_status, both of which query a run_id and report status/progress, but run_result additionally downloads outputs.
Naming Consistency3/5
All tools share the 'lingie_' prefix and use snake_case, which makes the set feel unified. However, the verb_noun pattern is not consistent: lingie_health and lingie_workflow_capabilities lack an action verb, and lingie_run_result reads more like a run command than a result-fetching operation.
Tool Count5/5
Eight tools is well-scoped for this domain. The set covers health checking, workflow discovery, parameter introspection, run submission, status/result retrieval, cancellation, and file upload without unnecessary duplication.
Completeness5/5
The tool surface covers the full generation lifecycle: check the service, discover workflows, inspect required parameters, upload input files, run the workflow, poll for progress, download results, and cancel if needed. There are no obvious dead ends for the intended use case.
Maintenance
ActivityMaintained
ResponsivenessNo issues