agent-tools/cloud

[giscus[bot]]

agent-tools/cloud

Use Comfy Cloud from Claude Code and Claude Desktop through the Comfy Cloud MCP server — generate images, video, audio, and 3D, search models and nodes, and run workflows.

https://docs.comfy.org/agent-tools/cloud

[mostafa1233211]

Hi, I'm getting an authorization error when trying to connect the Comfy Cloud MCP server to Claude Desktop. The error message says:
"Authorization with the MCP server failed. You can check your credentials and permissions. If this persists, share this reference with support: ofid_df2b0712ca4d2072"
I've tried re-adding the connector with the URL https://cloud.comfy.org/mcp but the OAuth sign-in flow doesn't seem to complete successfully. Could you please help me resolve this?

[jay76620]

Authorization with the MCP server failed. You can check your credentials and permissions. If this persists, share this reference with support: "ofid_d4084e3668673db5", same here

[vertstream]

Can u please explain codex setup also

[comfyui-wiki]

Will update soon

[febogallo]

Hello, Im having issues with the connection:

Bug: Claude Desktop custom connector fails at /oauth/authorize with 400 (dynamic client registration issue)
Environment:

Client: Claude Desktop
Connector setup: Custom connector, MCP server URL https://cloud.comfy.org/mcp

Steps to reproduce:

Add https://cloud.comfy.org/mcp as a custom connector in Claude Desktop (Customize → Connectors → Add custom connector), no OAuth Client ID/Secret entered (left blank for DCR).
Click Connect.
Browser opens to cloud.comfy.org/oauth/authorize and immediately shows:

{"jsonrpc":"2.0","error":{"code":-32001,"message":"Authentication required. Provide an X-API-Key header or Authorization: Bearer token."},"id":null}
Actually — the browser console shows a 400 Bad Request on the GET /oauth/authorize request itself, before any login page loads.
Captured request (client_id partially redacted):
https://cloud.comfy.org/oauth/authorize?response_type=code&client_id=comfy-dyn-027512c7-4013-44ef-96b9-75d11bbe1501&redirect_uri=https%3A%2F%2Fclaude.ai%2Fapi%2Fmcp%2Fauth_callback&code_challenge=TS0tG-OIElKi5e_RCG8-G4wPQVPBkfogF7gokdIJMyI&code_challenge_method=S256&state=eWAxTHThuxTeaMRYJw_zk0x9guj8tlvi4RtiVIvvSEs&scope=comfy-cloud%3Aworkflows%3Aread+comfy-cloud%3Aworkflows%3Awrite+comfy-cloud%3Ajobs%3Aread+comfy-cloud%3Ajobs%3Awrite+comfy-cloud%3Afiles%3Aread+comfy-cloud%3Afiles%3Awrite+comfy-cloud%3Aassets%3Aread+comfy-cloud%3Aassets%3Awrite+comfy-cloud%3Ahub%3Aread+comfy-cloud%3Ahub%3Awrite+comfy-cloud%3Auser%3Aread+comfy-cloud%3Asettings%3Aread+comfy-cloud%3Asettings%3Awrite+comfy-cloud%3Abilling%3Aread+comfy-mcp%3Atools%3Aread+comfy-mcp%3Atools%3Acall
The request itself looks spec-compliant (has redirect_uri, PKCE code_challenge + code_challenge_method=S256, state, and a full scope list), so this looks like the authorization server rejecting/not recognizing the dynamically-registered client_id at the /authorize step — possibly a timing/sync issue between DCR (/oauth/register) and /oauth/authorize.
What I've already ruled out:

Server is reachable: curl https://cloud.comfy.org/mcp returns 401 (expected, unauthenticated).
My Comfy Cloud account itself works fine — I can log in and use the dashboard normally at cloud.comfy.org.
Tried removing and re-adding the connector from scratch (fresh DCR client_id each time) — same 400.
Not a local network/firewall issue (confirmed server responds to direct requests).

Ask: Could someone check whether the /oauth/authorize endpoint is correctly persisting/looking up client_ids issued via dynamic client registration? Happy to provide more logs/HAR if useful.

[mo36924]

I can reproduce a similar OAuth/DCR issue with ChatGPT Developer Mode.

MCP server:
https://cloud.comfy.org/mcp

ChatGPT discovers the OAuth configuration successfully, but Dynamic Client Registration fails with:

Dynamic client registration failed: registration endpoint returned 400

invalid_client_metadata: oauth: client_name is reserved for first-party clients and may not be used by a dynamically-registered third-party client: "ChatGPT"