repo-b-mcp-comfy-bridge

Name: repo-b-mcp-comfy-bridge
Availability: InStock
Author: grtninja

Validate MCP bridge status and apply safe configuration changes for Comfy environments.

2|1|Updated Feb 9, 2026

Search Tags:#validation #mcp #bridge #rest-api #config-management #comfy #fail-closed

Ready to run

npx skills add https://github.com/grtninja/skill-arbiter --skill repo-b-mcp-comfy-bridge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repo-b-mcp-comfy-bridge
Source: https://github.com/grtninja/skill-arbiter/tree/main/skill-candidates/repo-b-mcp-comfy-bridge
Command: npx skills add https://github.com/grtninja/skill-arbiter --skill repo-b-mcp-comfy-bridge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The MCP bridge coordination and safe Comfy integration require strict checks to prevent unsafe changes and ensure reliable governance.

Core Features & Use Cases

Enforce loopback MCP defaults and fail-closed behavior to prevent drift.
Validate MCP runtime via /api/mcp/status and controlled config updates via /api/mcp/config.
Validate required Comfy resources (shim.comfy.*) and fail closed on anomalies to protect systems.
Scope boundaries and governance flows for repo B deployments.

Quick Start

Run the MCP Comfy Bridge workflow to validate status, enforce defaults, and apply safe configurations against the target repository.

Frequently Asked Questions about repo-b-mcp-comfy-bridge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I validate MCP bridge status and enforce fail-closed behavior in Comfy environments?▼

Validate MCP bridge status by checking the /api/mcp/status endpoint and enforce fail-closed behavior by applying loopback defaults. This prevents configuration drift and ensures safe Comfy integration by halting operations on detected anomalies.

What does fail-closed validation mean for MCP adapter configuration updates?▼

Fail-closed validation for MCP adapter configuration updates means the system automatically blocks unsafe changes and halts operations if Comfy resource contracts or runtime checks fail. This strict governance prevents unreliable configurations from being applied to the environment.

Do I need PowerShell and specific environment variables to run MCP Comfy bridge diagnostics?▼

Yes, you need PowerShell and specific required environment variables configured to run MCP Comfy bridge diagnostics. These environment prerequisites are strictly validated before runtime checks can execute against the /api/mcp/status and /api/mcp/config endpoints.

How can I prevent configuration drift when managing MCP governance workflows?▼

Prevent configuration drift in MCP governance workflows by enforcing loopback MCP defaults and validating Comfy resource contracts. The bridge automatically scopes boundaries for repo B deployments and fails closed on any detected anomalies during status checks.

Why does my MCP bridge configuration fail closed when updating Comfy resources?▼

Your MCP bridge configuration fails closed when updating Comfy resources because the system detects anomalies during shim.comfy.* contract checks. This strict validation protects systems by blocking any configuration changes that violate the Comfy resource contracts.