Developer · Remote MCP server
Runcomfy MCP
Remote MCP for RunComfy: ComfyUI deployments, hosted models, LoRA training. 31 tools.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.runcomfy-com/runcomfy-mcp- Version
- 1.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-07
- Updated
- 2026-09-07
- Publisher
- runcomfy-com (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/runcomfy-com) · how
- Website
- www.runcomfy.com
- Repository
- github.com/runcomfy-com/runcomfy-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.runcomfy.com/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Runcomfy MCP
Runcomfy MCP is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.runcomfy.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| RubrkitMCP-native AI evaluation: rubric audits, eval suites, and proof reports for AI/LLM output. | Remote · HTTPLive check: ✓ handshake |
| Rules MCPMCP for rules/skills/knowledge evaluation for Cursor, Claude, VS Code, and Antigravity. | Local · stdio |
| Run PythonRun Python code from natural language prompts, with optional PyPI package install. | Remote · HTTPLive check: ✗ no handshake |
| RunCabinPut websites online from chat - instant free HTTPS, real domains, zero DNS or API-key setup. | Remote · HTTPLive check: sign-in required |
| RuneEvidence-backed codebase understanding with file:line citations, for AI clients over MCP. | Local · stdio |
| RunewardGoverned execution cells for AI agents: Docker/K8s sandboxes with policy, audit, and approvals. | Local · stdio |
| RunlogVerified registry of third-party-system knowledge - the external-dependency layer for agent memory. | Remote · HTTPLive check: ✗ no handshake |
| RunpodLaunch, scale, and manage GPU pods and serverless endpoints across regions. | Local · stdio |