๐ ๐ ๐ - Omnimodal AIGC framework that turns ComfyUI workflows into MCP tools without code, for text, image,โฆ
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP ๆๅก. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
first catalogued 2026-10-09๏ผlast seen 2026-10-16ใThere is no official certification or quality rating here โ we record sources and dates only.
๐จ Pixelle MCP - Omnimodal Agent Framework
ไปฅไธๆๅฝ่ช่ฏฅไปๅบ็ README๏ผ็ๆฎต๏ผ ยท ๅจ GitHub ่ฏปๅฎๆด README โ
English | ไธญๆ
โจ An AIGC solution based on the MCP protocol, supporting both local ComfyUI and cloud ComfyUI (RunningHub) modes, seamlessly converting workflows into MCP tools with zero code.
https://github.com/user-attachments/assets/65422cef-96f9-44fe-a82b-6a124674c417
๐ Recent Updates
- โ
**2025-09-29**: Added RunningHub cloud ComfyUI support, enabling workflow execution without local GPU and ComfyUI environment
- โ
**2025-09-03**: Architecture refactoring from three services to unified application; added CLI tool support; published to PyPI
- โ
**2025-08-12**: Integrated the LiteLLM framework, adding multi-model support for Gemini, DeepSeek, Claude, Qwen, and more
๐ Features
- โ
๐ **Full-modal Support**: Supports TISV (Text, Image, Sound/Speech, Video) full-modal conversion and generation
- โ
๐ **Dual Execution Modes**: Local ComfyUI self-hosted environment + RunningHub cloud ComfyUI service, users can flexibly choose based on their needs
- โ
๐งฉ **ComfyUI Ecosystem**: Built on ComfyUI, inheriting all capabilities from the open ComfyUI ecosystem
- โ
๐ง **Zero-code Development**: Defines and implements the Workflow-as-MCP Tool solution, enabling zero-code development and dynamic addition of new MCP Tools
- โ
๐๏ธ **MCP Server**: Based on the MCP protocol, supporting integration with any MCP client (including but not limited to Cursor, Claude Desktop, etc.)
- โ
๐ **Web Interface**: Developed based on the Chainlit framework, inheriting Chainlit's UI controls and supporting integration with more MCP Servers
- โ
๐ฆ **One-click Deployment**: Supports PyPI installation, CLI commands, Docker and other deployment methods, ready to use out of the box
- โ
โ๏ธ **Simplified Configuration**: Uses environment variable configuration scheme, simple and intuitive configuration
- โ
๐ค **Multi-LLM Support**: Supports multiple mainstream LLMs, including OpenAI, Ollama, Gemini, DeepSeek, Claude, Qwen, and more
๐ Project Architecture
Pixelle MCP adopts a **unified architecture design**, integrating MCP server, web interface, and file services into one application, providing:
- ๐ **Web Interface**: Chainlit-based chat interface supporting multimodal interaction
- ๐ **MCP Endpoint**: For external MCP clients (such as Cursor, Claude Desktop) to connect
- ๐ **File Service**: Handles file upload, download, and storage
- ๐ ๏ธ **Workflow Engine**: Supports both local ComfyUI and cloud ComfyUI (RunningHub) workflows, automatically converts workflows into MCP tools
๐โโ๏ธ Quick Start
Choose the deployment method that best suits your needs, from simple to complex:
๐ฏ Method 1: One-click Experience
> ๐ก **Zero configuration startup, perfect for quick experience and testing**
๐ Temporary Run
๐ **View uvx CLI Reference โ**
๐ฆ Persistent Installation
๐ **View pip CLI Reference โ**
After startup, it will automatically enter the **configuration wizard** to guide you through execution engine selection (ComfyUI/RunningHub) and LLM configuration.
๐ ๏ธ Method 2: Local Development Deployment
> ๐ก **Supports custom workflows and secondary development**
๐ฅ 1. Get Source Code
๐ 2. Start Service
๐ **View Complete CLI Reference โ**
๐ง 3. Add Custom Workflows (Optional)
**โ ๏ธ Important**: Make sure to test workflows in ComfyUI first to ensure they run properly, otherwise execution will fail.
๐ณ Method 3: Docker Deployment
> ๐ก **Suitable for production environments and containerized deployment**
๐ 1. Prepare Configuration
๐ 2. Start Container
๐ Access Services
Regardless of which method you use, after startup you can access via:
- **๐ Web Interface**: http://localhost:9004
*Default username and password are both dev, can be modified after startup*
- **๐ MCP Endpoint**: http://localhost:9004/pixelle/mcp
*For MCP clients like Cursor, Claude Desktop to connect*
**๐ก Port Configuration**: Default port is 9004, can be customized via environment variable PORT=your_port.