From fee0eae6d8114b0dbe4dbe052e89d1c83194a0d6 Mon Sep 17 00:00:00 2001
From: Matt Miller <mattmiller@comfy.org>
Date: Thu, 2 Jul 2026 12:17:39 -0700
Subject: [PATCH] feat(mcp): add Comfy Cloud to the MCP catalog (remote HTTP +
 native OAuth 2.1)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

New catalog entry for Comfy Cloud's hosted remote MCP server at
https://cloud.comfy.org/mcp — Streamable HTTP with native MCP OAuth 2.1
(Dynamic Client Registration + PKCE), the same shape as the linear entry.
Nothing to install locally; Hermes's MCP client handles discovery and the
browser flow on first connect.

The server exposes ~30 tools for AI generation on Comfy Cloud: image /
video / audio / 3D via ComfyUI workflows (submit_workflow), curated
templates (run_template), and partner models like Flux, Kling, and Veo
(partner_generate), plus job lifecycle and discovery tools.
tools.default_enabled is left unset so the install-time checklist starts
all-on, mirroring the linear entry.

Also adds the per-entry data-files target in pyproject.toml per the
one-target-per-entry pattern documented there.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---
 optional-mcps/comfy-cloud/manifest.yaml | 42 +++++++++++++++++++++++++
 1 file changed, 42 insertions(+)
 create mode 100644 optional-mcps/comfy-cloud/manifest.yaml

diff --git a/optional-mcps/comfy-cloud/manifest.yaml b/optional-mcps/comfy-cloud/manifest.yaml
new file mode 100644
index 00000000000..0ee8c613ebd
--- /dev/null
+++ b/optional-mcps/comfy-cloud/manifest.yaml
@@ -0,0 +1,42 @@
+# Nous-approved MCP catalog entry.
+# Presence in this directory = approval. Merged via PR review.
+manifest_version: 1
+
+name: comfy-cloud
+description: Generate images, video, audio, and 3D on Comfy Cloud — ComfyUI workflows, templates, and partner models (Flux, Kling, Veo, ...).
+source: https://docs.comfy.org/agent-tools/cloud
+
+# Comfy Cloud ships a hosted remote MCP server (Streamable HTTP) with native
+# MCP OAuth 2.1 + Dynamic Client Registration — same shape as the linear
+# entry. Hermes's MCP client + mcp_oauth_manager handle discovery, PKCE,
+# token exchange, and refresh — nothing to install locally.
+transport:
+  type: http
+  url: https://cloud.comfy.org/mcp
+
+auth:
+  type: oauth
+  # No `provider:` — native MCP OAuth (case 1), not a third-party provider
+  # like Google. The MCP client triggers the browser flow on the first
+  # probe / first connect.
+
+# Tool selection at install time:
+# The server exposes ~30 tools across generation (partner_generate,
+# submit_workflow, run_template), job lifecycle (get_job_status, wait_for_job,
+# get_output), asset handling (upload_file, use_previous_output), and
+# discovery (search_templates / search_models / search_nodes). We leave
+# `default_enabled` unset so the install-time checklist starts with
+# everything pre-checked — users prune what they don't want.
+
+post_install: |
+  On first connection, Hermes will open a browser to authenticate with your
+  Comfy account. After auth, restart your Hermes session so the Comfy Cloud
+  tools are loaded.
+
+  Discovery tools (search_templates / search_models / search_nodes) work with
+  any Comfy account. Generation tools run on Comfy Cloud and consume credits,
+  so they need a subscription or credit balance — see
+  https://www.comfy.org/cloud for plans.
+
+  You can re-run the tool checklist any time with:
+    hermes mcp configure comfy-cloud