Comfy Local MCP
Windows-native MCP server for a local ComfyUI portable package. It enables listing, validating, and running ComfyUI workflows via the loopback HTTP API.
README
Comfy Local MCP
Windows-native MCP server for a local ComfyUI portable package. It talks to
ComfyUI over its loopback HTTP API and runs with the portable package's own
python_embeded\python.exe; no virtual environment is required.
Portable layout
The MCP package is expected to be placed next to the portable package folders:
ComfyUI_windows_portable\
ComfyUI\
python_embeded\
comfy-local-mcp\
The installer also accepts an explicit -PortableRoot when the MCP package is
stored elsewhere.
Install
From PowerShell, run install.ps1 in the extracted package directory:
.\install.ps1 -PortableRoot "F:\ComfyUI_windows_portable" -RegisterCodex
The installer:
- uses
ComfyUI\..\python_embeded\python.exedirectly; - installs the pinned MCP dependency into this package's
vendordirectory; - copies bundled API-format workflows into
ComfyUI\user\default\workflows; - uses
ComfyUI\outputas the output directory; - optionally registers the MCP server with Codex.
No files are installed into ComfyUI's python_embeded\Lib\site-packages.
Runtime configuration
COMFYUI_URL: loopback ComfyUI URL, defaulthttp://127.0.0.1:8188.COMFY_PORTABLE_ROOT: portable root containing siblingComfyUIandpython_embededdirectories.COMFYUI_ROOT: optional explicit ComfyUI directory.COMFY_MCP_WORKFLOW_ROOT: defaults toComfyUI\user\default\workflows.COMFY_MCP_OUTPUT_ROOT: defaults toComfyUI\output.COMFY_MCP_ALLOWED_ROOTS: semicolon-separated workflow/output roots.
The MCP tools list_workflows and save_workflow operate in the configured
workflow directory. validate_workflow and run_workflow accept either an
absolute path inside that directory or a workflow filename.
Build a Release
From the repository root:
.\tools\comfy_local_mcp\build_release.ps1 -Version "0.1.0"
The generated archive is written to dist\comfy-local-mcp-0.1.0.zip.
Notes
ComfyUI must be running before calling server_info, validate_workflow, or
run_workflow. Models and custom nodes remain customer-local; the MCP package
does not download or share model weights.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.