mcp-circuit-breaker

Solid

Detects MCP tool failure patterns and trips a circuit breaker to stop cascading retries. Proposes fallback alternatives and resets when the tool recovers. Triggers on "MCP failing", "tool keeps erroring", "circuit-breaker", repeated tool call failures.

AI & Automation 8 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 79/100

Stars 20%
32
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# mcp-circuit-breaker — MCP Tool Failure Guard MCP tools can fail silently or return partial results, leading to cascading retry loops that waste tokens and degrade session quality. This skill detects failure patterns, trips a circuit breaker to halt retries, proposes alternatives, and resets when the tool recovers. > **Scope distinction** > - Claude Code native retry: low-level transport retries (transparent, fast) > - mcp-circuit-breaker: **session-level guard** — detects repeated semantic failures, intervenes before token waste compounds --- ## Triggers - `/mcp-circuit-breaker` - "MCP failing", "MCP keeps erroring", "tool isn't working", "circuit-breaker" - "same error keeps happening", "tool call looping", "MCP timeout" - Automatic: when the same MCP tool name appears in 3+ consecutive failed calls within a session --- ## Circuit States ``` CLOSED → Normal operation (tool calls pass through) OPEN → Circuit tripped (calls blocked, alternatives proposed) HALF-OPEN → Recovery probe (1 test call allowed, resets if success) ``` Default thresholds: - **Trip threshold**: 3 consecutive failures of the same tool - **Half-open probe**: after 60s cooldown (or explicit user command) - **Reset**: 1 successful call in HALF-OPEN state → back to CLOSED --- ## Execution Steps ### Step 1. Detect Failure Pattern Identify the failing tool and failure mode: ```bash # Check MCP server config cat .claude/settings.json 2>/dev/null | grep -A5 '"mcpServers"' || echo "No MCP con...

Details

Author
chrono-meta
Repository
chrono-meta/forge-harness
Created
2 months ago
Last Updated
today
Language
Shell
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

mcp-driver

Runtime debugging and live project inspection via godot-mcp. Use when headless tools cannot diagnose the problem: code compiles but runtime behavior is wrong, tests pass but the game does not work as expected, or you need to inspect live state (node tree, console output, rendering). Escalation trigger: a task has failed 2+ times through the headless path (headless-build, gdunit-driver), or the issue is inherently runtime-only (visual glitches, input not responding, physics behaving unexpectedly at runtime). DO NOT use for: syntax/compile errors (use headless-build), unit test failures (use gdunit-driver), API lookups (use godot-api). Requires: godot-mcp MCP server registered as "godot" (@coding-solo/godot-mcp).

492 Updated today
RandallLiuXin
AI & Automation Solid

mcp-toolchain-manager

Detect frontend tool capabilities, report gaps, verify official setup sources, plan approval-gated MCP changes, or update project/mcp-profile.md. Prefer capabilities over provider names; never install or configure without approval.

5 Updated 1 weeks ago
ytvee-dev
AI & Automation Listed

mcp-migration-auditor

Use this skill when the user wants to audit my MCP setup, check MCP compatibility, asks will my MCP servers break, mentions MCP spec migration, wants an MCP 2026 spec check, or says scan mcp config — also on any readiness question about the MCP 2026-07-28 specification (stateless transport, removed Mcp-Session-Id, deprecated roots/sampling/logging, experimental Tasks migration, OAuth hardening). Locates MCP configs (.mcp.json, claude_desktop_config.json, mcp.json, settings files) or accepts a pasted one, checks each server against rules verified from the official MCP blog and spec changelog, and outputs a per-server BREAKS/DEGRADED/SAFE table naming the triggering rule and specific fix, plus a prioritized migration checklist against the 2026-07-28 final date. Stdio-only local setups get an honest all-clear. Do NOT use for context-window cost audits of MCP connectors (cli-over-mcp-auditor's job), for debugging a broken MCP connection, or for installing new servers.

2 Updated 5 days ago
Abhillashjadhav